Apivault · Rate Limits
Apivault Rate Limits
Apivault Rate Limits is the rate-limit profile for Apivault 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 limit, remaining, reset, and retryAfter response headers.
The profile also includes response codes documented for throttled and throttled_note.
Tagged areas include API Catalog, API Directory, API Discovery, Open Source, and Public APIs.
0 Limits
limitremainingresetretryAfter
Read from the provider's live responses on 2026-09-04 — Live response headers from api.apivault.dev (GET /api/cou....
View Source
Limits
Apivault publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
ApiVault documents no rate limits and signals none at runtime. Not one of X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset, RateLimit-Policy or Retry-After appeared on any observed response, and no 429 was ever returned. An agent has no runtime signal to back off on — the honest zero IS the finding. Cloudflare sits in front of api.apivault.dev, so an undocumented edge protection may exist, but it is not advertised and cannot be planned against. THIS REPLACES A SCAFFOLD. The previous version of this file was written by the 2026-05-04 bulk sweep (method: generated) and declared an X-RateLimit-*/Retry-After/RateLimit-Policy header set and a 429 throttled response code. None of those headers is actually sent. They have been removed rather than carried forward.
API CatalogAPI DirectoryAPI DiscoveryOpen SourcePublic APIs
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.