Archive Technologies Rate Limits
Two limits apply to an Archive workspace at the same time, and whichever is reached first binds: a per-plan CREDIT BUDGET that refills every second, and a flat ceiling of 5 requests per second. Both are per workspace and never shared — one token covering several workspaces gets a full budget in each, including on agency plans. One credit is one millisecond of backend compute, so cost follows the work a request causes rather than the size of the response. Archive's hosted MCP server draws on the same budget: a tool call maps to a query and costs what that query costs. Every response carries the IETF ratelimit / ratelimit-policy headers, so a client can read its plan, its burst allowance and its remaining credits off any response instead of discovering the ceiling with a 429.
Archive Technologies Rate Limits is the machine-readable rate-limit profile for Archive Technologies on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 2 rate-limit definitions, measuring requests_per_second and credits.
The profile also includes response codes documented for throttled.
Tagged areas include Rate Limiting, GraphQL, MCP, and Creator Marketing.
Limits
Sources
- https://api-docs.archive.com/concepts/rate-limiting
- https://api-docs.archive.com/reference/error-handling
- https://api-docs.archive.com/guides/best-practices
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.