Every MuleRouter endpoint requires an API key, passed in theDocumentation Index
Fetch the complete documentation index at: https://mulerouter.ai/docs/llms.txt
Use this file to discover all available pages before exploring further.
Authorization request header.
Get an API key
Open the API Keys tab
Sign in to the MuleRouter Console
and open the API Keys tab.
Generate a new key
Click Generate new key. The console shows the full key string
exactly once — copy it to a secret store immediately.
Send authenticated requests
Include the key as a Bearer token in theAuthorization header:
GET URLs.
SDK setup
Most OpenAI-compatible SDKs accept abase_url override. Point it at
MuleRouter and they “just work”:
Best practices
- Never commit keys to source control. Use environment variables,
.envfiles (gitignored), or a secret manager. - Rotate aggressively. Generate a new key when a teammate leaves, when you suspect a leak, or on a fixed cadence.
- One key per workload. Per-service keys make leaks easy to scope and revoke without disrupting unrelated traffic.
- Server-side only. Treat the key like a database password — never ship it in a browser bundle or mobile app.
Errors
| HTTP | Meaning | Likely cause |
|---|---|---|
401 Unauthorized | Missing, malformed, or revoked key | Check the Authorization header is Bearer <key> |
402 Payment Required | Insufficient balance | Top up in the Console |
429 Too Many Requests | Rate limit / quota / daily-spend cap | Slow down or raise the limit |

