osmAPI · Rate Limits

Osmapi Rate Limits

osmAPI applies per-API-key rate limits with separate ceilings for free and paid models. Free models share a 200 rpm budget; paid models default to 1000 rpm per key with Enterprise able to negotiate higher. Real throughput is also bounded by upstream provider capacity and account credit balance. Free model responses include rate-limit telemetry headers.

Osmapi Rate Limits is the machine-readable rate-limit profile for osmAPI on the APIs.io network, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring requests_per_minute.

Limit state is signalled in the limit, remaining, reset, and retryAfter response headers, and an exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled and quotaExceeded.

Tagged areas include Rate Limiting, AI, LLM, and Gateway.

3 Limits Exhausted: HTTP 429 Quota: 429 limitremainingresetretryAfter
Method: generated, dated 2026-05-05.
Written by API Evangelist on 2026-05-05 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Rate LimitingAILLMGateway

Limits

Free Models - Default api-key
requests_per_minute · minute
200
Applies to all users on free models. Window resets every 60 seconds.
Paid Models - Default api-key
requests_per_minute · minute
1000
Default for paid model access. Actual throughput also bounded by credit balance and upstream provider limits.
Enterprise - Negotiated account
requests_per_minute
contact sales for higher than 1000 rpm
Enterprise customers can negotiate higher per-key throughput.

Policies

Backoff
When 429 is returned, clients should pause and retry using exponential backoff, honoring the Retry-After header value.
Header-Driven Throttling
Free model responses include X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset and Retry-After. Clients should read these headers to pace requests and avoid throttling.
Free vs Paid Routing
osmAPI recommends reserving free models for development and routing production workloads to paid models for higher throughput.
Upstream Provider Limits
Even within osmAPI's published per-key limits, upstream provider rate limits (OpenAI, Anthropic, Google, Groq, etc.) and account credit balance can further bound throughput.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/osmapi-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.