Features
What passes through unchanged, and what the gateway itself handles.
What does RouteMux change about my request?
Almost nothing. Request and response bodies are forwarded to the upstream provider
verbatim. The gateway reads only model, stream, and usage metadata — tool definitions,
system prompts, message shapes, and provider-specific parameters behave exactly as the
provider documents them.
Does tool / function calling work?
Yes, unchanged, because the body is passed through. Whether a given model supports it is a property of that model, not of the gateway.
Does streaming work?
Yes. SSE is forwarded without buffering the whole response, and billing settles on real usage after the upstream finishes. Disconnecting mid-stream aborts the upstream call.
Can I use one key for several providers?
That is the point. A single key and base URL reach every model your key has access to across providers, on one balance and one bill.
Are images and video supported?
Yes, with different billing shapes:
- Images — billed per call rather than per token. Requesting several images bills each one.
- Video — asynchronous. Submitting returns a job immediately; you poll for status and fetch the result. Billing happens when the job completes successfully; failed jobs cost nothing.
Is there an OpenAPI spec?
Yes — the full machine-readable contract is at /docs/openapi.json, and /llms.txt is an
index written for AI coding tools. Every documentation page is also available as raw
Markdown by appending .md to its URL.