Skip to main content
MuleRouter is an all-in-one API service for developers. One API key gives you access to multimodal AI from many providers — chat, image, video, speech, music — through a single, unified interface. We negotiate higher-tier service levels with each provider through aggregated purchasing, so the same API tends to be more stable and faster than going direct. This site is the reference for the MuleRouter HTTP API, the official CLI, and the rest of the platform surface.

​
Where to start

Quickstart

Send your first request in under a minute — curl, an API key, done.

Authentication

Get an API key, secure it, and use it in production.

Asynchronous tasks

The async pattern shared by every long-running endpoint.

Webhooks

Receive signed callbacks instead of polling for status.

Error codes

HTTP status codes and MuleRouter error codes in one place.

API Reference

The full per-endpoint catalog — LLM, image, video, speech, music.

CLI

mulerouter — drive every endpoint from the terminal.

Console

Manage API keys, billing, and webhooks in the web console.

​
What you can build with MuleRouter

​
How the API is shaped

  • Providers under /vendors — /vendors/openai/..., /vendors/google/..., etc. The path mirrors the upstream provider’s own API surface as closely as possible, so most existing SDKs work with a base-URL swap. See Endpoint conventions.
  • Industry aliases — /v1/chat/completions and /v1/models are aliases for the corresponding /vendors/... paths so OpenAI-flavored SDKs work out of the box.
  • Asynchronous tasks — image and video generation use a POST → poll GET pattern. See Asynchronous tasks.
  • Webhooks — register an HTTPS endpoint to skip polling entirely. See Webhooks.

​
Help

  • Found a bug? Include the Traceparent response header when filing the issue — it lets us trace the exact request through our pipeline.
  • Discord — community channel linked in the sidebar.
  • Email — contact@mulerouter.ai