Google Vault Rate Limits
Google publishes the Vault API's quotas in full, as per-minute per-project request budgets split by resource family, plus one organization-wide ceiling and one product limit on concurrent exports. It publishes NO rate-limit response headers, so an agent cannot read its remaining budget at runtime — the only runtime signal is the 429 itself.
Google Vault Rate Limits is the machine-readable rate-limit profile for Google Vault on the APIs.io network, in the API Commons Rate Limits shape.
It captures 10 rate-limit definitions, measuring matter_reads, read_requests, write_requests, and count_requests.
Limit state is signalled in the limit, remaining, reset, and retryAfter response headers, and an exhausted limit returns HTTP 429.
The profile also includes response codes documented for throttled and quotaExceeded.
Tagged areas include Rate Limiting, Quotas, and Throttling.
limitremainingresetretryAfter
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.