Skip to main content
Every MuleRouter endpoint sits under a single host:
The path is what tells MuleRouter which provider and which model you want. See the API Reference for the exact URL of every endpoint.

​
Industry aliases

For the few endpoints that have become de-facto industry standards, we expose short aliases at the root so existing SDKs work with a single base_url swap.

​
Synchronous vs asynchronous endpoints

  • Synchronous / streaming. Chat completions and similar fast endpoints respond within a single HTTP request — switch the base URL and you’re done.
  • Asynchronous tasks. Image, video, speech, and music generation return a task_id immediately and finish out-of-band. Poll GET .../<task-id> (or use webhooks) to retrieve the result. See Asynchronous tasks for the full pattern.

​
Response headers worth knowing

​
Migrating from a direct provider integration

In most cases, all you need to change is the base_url. For example, moving from OpenAI direct to MuleRouter:
python
For providers that have their own request shape (Google, Kling, Wan, etc.), use the matching /vendors/<provider>/... path. The per-endpoint reference pages list the exact request and response schemas.