UniversalBench bakes authentication into the URL path. Every customer has a personal URL containing their API key in the path:Documentation Index
Fetch the complete documentation index at: https://docs.universalbench.dev/llms.txt
Use this file to discover all available pages before exploring further.
ubk_ prefix identifies a UniversalBench key. The 64 character hex string after is the secret.
Why URL embedded auth
Most MCP services use a shared endpoint plus anX-API-Key header configured separately in your client. Every MCP client handles custom headers differently. Some break silently when headers are present. Some force them through OAuth flows that do not apply here.
Embedding the key in the URL path solves all of that. One paste, works everywhere. The client never needs to know about headers.
Treat your URL like a password
Anyone with your URL can make calls billed to your account. To minimize blast radius:- Do not commit your URL to public repositories
- Do not paste it into screenshots or shared logs
- Rotate the URL immediately if you suspect exposure
Rotating your URL
If your URL is compromised or you want a fresh one for any reason, click “Rotate key” in your dashboard. The old URL is invalidated immediately. Any MCP client configured with the old URL will start returning auth errors and needs to be updated with the new URL.Alternative authentication methods
If for some reason you cannot use the URL embedded auth (rare), the API also accepts the key in a few other places:| Method | Example |
|---|---|
| Authorization header | Authorization: Bearer ubk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |
| Custom header | X-Api-Key: ubk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |
| Query parameter | ?key=ubk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |
https://universalbench-mcp.penantiaglobal.workers.dev/. The URL embedded form is preferred because it requires zero client configuration.