Langtrace AI · Rate Limits

Langtrace Rate Limits

Langtrace does not publish explicit per-endpoint request rate limits for its REST API. The practical ceiling on Langtrace Cloud is the span allowance of the active plan (monthly/annual span quotas), rather than RPM/TPM throttles. The trace retrieval endpoint caps pageSize at 100 traces per request, which bounds read pagination. Self-hosted deployments are limited only by the capacity of the operator's own infrastructure. Specific throttle values are not reconciled in this artifact.

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

It captures 4 rate-limit definitions, measuring traces, spans, and requests.

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, OpenTelemetry, and Tracing.

4 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
AILLMObservabilityOpenTelemetryTracingOpen SourceRate LimitingQuotasThrottling

Limits

Trace Retrieval Page Size request
traces
100
POST /api/traces caps pageSize at 100 traces per page.
Cloud Span Allowance account
spans
see plan / provider documentation
Span quota per Cloud plan (e.g., Free monthly cap, Growth annual cap) acts as the usage ceiling.
Ingestion Rate account
spans
see provider documentation
No published per-second ingestion throttle; bounded by plan span allowance on Cloud.
Self-Hosted deployment
requests
operator infrastructure capacity
Self-hosted deployments have no provider-imposed rate limit.

Policies

Span-Based Quotas
Cloud usage is governed by span allowances per plan rather than request-per-minute throttles.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After if a 429 is returned.

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