API keys
The whole catalog — models, hardware, providers, prices, benchmarks — is a public API and an MCP server. Without a key you can try it: 10 requests a minute, 100 a day. Afree key is for your own projects: 500 requests a day and5,000 a month. One key works for both REST and MCP.
What you get
One request is one API call or one MCP tool call. A question asked through an assistant uses two to five, so a busy day of your own questions fits with room to spare. Free, for your own projects.
The same counters cover /api/v1/* and the MCP server — one budget, either door.
One magic-link email delivers and activates the key. No password, no dashboard to forget.
Tiers & limits
| tier | how issued | sustained | burst | daily | monthly |
|---|---|---|---|---|---|
| no key | nothing to do — enough to try it | 10/min | 3/s | 100/day | — |
| free key | automatic, by email | 20/min | 5/s | 500/day | 5,000/month |
| partner | approved by hand | 300/min | 20/s | 20,000/day | 500,000/month |
Every response carries RateLimit-* headers so clients can pace themselves. The chat assistant keeps its own budget — keys don't change it.
Request a key
Using the key
Send it as Authorization: Bearer or X-API-Key — REST and MCP alike:
curl https://llmap.ai/api/v1/models?limit=3 \ -H 'Authorization: Bearer llmap_f…'
Lost the key? Just request a new one. Leaked it? POST /api/v1/keys/revoke with the key as the credential kills it instantly. Full endpoint list on the MCP & API page.