Literal AI · Rate Limits

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, in the API Commons Rate Limits shape.

It captures 5 rate-limit definitions, measuring log_units, days, seats, requests, and spans.

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 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include AI, LLM, Observability, Evaluation, and Monitoring.

5 Limits Exhausted: HTTP 429
Method: generated, dated 2026-06-20.
Written by API Evangelist on 2026-06-20 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
AILLMObservabilityEvaluationMonitoringRate LimitingQuotasThrottling

Limits

Log Units (Monthly Ingestion) account
log_units
see provider documentation
Primary metering unit; 10,000/month on Basic, higher on Pro/Enterprise.
Data Retention account
days
see provider documentation
30 days on Basic; extended on paid tiers.
Team Members (Seats) account
seats
see provider documentation
Up to 3 on Basic; more on Pro/Enterprise.
GraphQL Requests account
requests
see provider documentation
Per-account throttling on the /api/graphql endpoint.
OTEL Ingestion account
spans
see provider documentation
OpenTelemetry (OTLP) trace ingestion counts toward Log Unit usage.

Policies

Tiered Limits
Log Unit quotas, retention, and seats increase from Basic to Pro to Enterprise.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

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/literalai-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.