Literalai Rate Limits
Literal AI meters API usage primarily through monthly "Log Units" of ingestion that vary by plan, plus data-retention windows and seat counts. The GraphQL endpoint and OTEL ingestion path are also subject to per-account request throttling to protect the platform. Specific request thresholds and Log Unit conversions are not published as fixed numbers and are not reconciled in this artifact.
Literalai Rate Limits is the machine-readable rate-limit profile for Literal AI on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 5 rate-limit definitions, measuring log_units, days, seats, requests, and spans.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include AI, LLM, Observability, Evaluation, and Monitoring.
Limits
Policies
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/literalai-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.