API keys
The whole catalog — models, hardware, providers, prices, benchmarks — is a public API and an MCP server. Anonymous access works forever; a free key lifts you from per-IP limits to 5 req/s and 20k requests/day. One key works for both REST and MCP.
What you get
300/min, 20k/day, 500k/month — enough for a production integration, free forever.
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 |
|---|---|---|---|---|---|
| anonymous | nothing to do | 60 req/min | 10 req/s | 2,000/day | — |
| free key | auto — magic-link email | 300 req/min (5 req/s) | 20 req/s | 20,000/day | 500k/mo |
| partner | manual approval | 1,200 req/min (20 req/s) | 60 req/s | 200,000/day | 5M/mo |
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 orX-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 theMCP & API page.