Lvlltd Com Rate Limits
LVL LTD publishes one hard limit — the A2A JSON-RPC endpoint at ~120 requests per 60 seconds per isolate, signalled by an X-RateLimit-Remaining response header, HTTP 429 and JSON-RPC code -32005 — and says the REST skill-pay path has "no hard public rate limit on canary path; abuse may be throttled at edge" (Cloudflare). A live REST request carried no RateLimit-* headers; a live A2A request returned X-RateLimit-Remaining: 119, which corroborates the 120/60 s figure. The MCP endpoint documents no limit.
Lvlltd Com Rate Limits is the machine-readable rate-limit profile for LVL LTD CO on the APIs.io network, in the API Commons Rate Limits shape.
It captures 1 rate-limit definition, measuring requests.
Limit state is signalled in the remaining, requestId, retryAfter, and note response headers, and an exhausted limit returns HTTP 429.
The profile also includes response codes documented for throttled and jsonrpc.
Tagged areas include Rate Limiting, A2A, and x402.
remainingrequestIdretryAfternote
Limits
Sources
- https://lvlltd.com/docs/REFERENCE.md#rate-limits-retry-idempotency
- https://lvlltd.com/api/a2a (dev_patterns.patterns.production.rate_limit; jsonrpc_transport.headers + error_codes)
- "119 observed)"}" target="_blank" rel="noopener">{"live POST https://lvlltd.com/api/a2a on 2026-09-19 (X-RateLimit-Remaining" => "119 observed)"}
- live GET https://lvlltd.com/api/catalog on 2026-09-19 (no rate-limit headers observed)
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.