Plyrium Com Rate Limits
VouchSpec documents THAT it rate-limits (a 429 RateLimited response on the paid POST, and "bounded ... rate ... controls" in the operations doc) but publishes no numeric request limit, window or scope, and returns no RateLimit-*, X-RateLimit-* or Retry-After header on the responses observed. The only numeric bounds published are payload and time bounds, recorded separately below. limit_count is therefore an honest zero.
Plyrium Com Rate Limits is the rate-limit profile for Plyrium on the APIs.io network.
The provider publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
Limit state is signalled in the rateLimit, retryAfter, and note response headers, and an exhausted limit returns HTTP 429.
The profile also includes response codes documented for throttled and payloadTooLarge.
Tagged areas include Rate Limiting and Agent Skills.
rateLimitretryAfternote
Limits
Sources
- https://vouchspec.plyrium.com/openapi.json (components.responses.RateLimited on POST /validate; TooLarge 413)
- https://vouchspec.plyrium.com/api/vouchspec/v1/discovery (request.maximum_bytes, payment max_timeout)
- https://raw.githubusercontent.com/mordiaky/vouchspec/main/docs/stage-b-operations.md ("bounded public/tenant registration and commerce limits"; byte bounds)
- live responses of 2026-09-19 (no rate-limit headers on any of 12 probed responses)
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.