Langwatch Rate Limits
LangWatch does not publish per-second or per-minute REST rate limits in its public documentation. Usage is gated primarily by per-plan event quotas (Developer 50k/mo, Growth 200k/mo with metered overage, Enterprise custom) rather than by request-rate throttling. AI Gateway provider bindings can enforce per-virtual-key budgets and semantic-cache rules as a separate governance layer.
Langwatch Rate Limits is the machine-readable rate-limit profile for LangWatch on the APIs.io network, in the API Commons Rate Limits shape.
It captures 4 rate-limit definitions, measuring events and gateway-spend.
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 response codes documented for throttled and quotaExceeded.
Tagged areas include LLM Observability, Rate Limiting, and Quotas.
limitremainingresetretryAfter
generated, dated 2026-05-25.
Limits
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.