Viewsmeet Com Rate Limits
One published policy, advertised at runtime in IETF-draft RateLimit header fields and observed live on 2026-09-19 on every /api/v1/* response (ratelimit-policy: "minute";q=30;w=60, with RateLimit-Policy, RateLimit and Retry-After listed in access-control-expose-headers). The developer guide: "Protected API, MCP, and A2A responses advertise the current IETF-draft RateLimit-Policy field: 30 requests per 60-second window for each operation-specific abuse key. A 429 response includes Retry-After: 60 and a zero-remaining RateLimit field. Public cached documents may be fetched normally and should be revalidated according to their cache headers."
Viewsmeet Com Rate Limits is the machine-readable rate-limit profile for ViewsMeet on the APIs.io network, in the API Commons Rate Limits shape.
It captures 1 rate-limit definition, measuring requests_per_window.
Limit state is signalled in the policy, remaining, retryAfter, and requestId response headers, and an exhausted limit returns HTTP 429.
The profile also includes response codes documented for throttled and retryAfterSeconds.
Tagged areas include Rate Limiting and Agent-native.
policyremainingretryAfterrequestId
Limits
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.