Agave Rate Limits
Agave publishes numeric rate limits and returns runtime rate-limit headers. This artifact replaces an earlier generated one that stated "Agave does not publish numeric rate limits" — that was wrong: https://docs.agaveapi.com/agave-api/rate-limits has carried both an Agave-imposed ceiling and a per-source-system table. Agave layers its own limits on top of each connected source system's, and surfaces BOTH in the response headers, which is the useful part for an agent: a caller can read its remaining Agave budget and its remaining Procore/QuickBooks/Intacct budget from the same response.
Agave Rate Limits is the machine-readable rate-limit profile for Agave on the APIs.io network, in the API Commons Rate Limits shape.
It captures 4 rate-limit definitions, measuring requests per minute per Linked Account, concurrent requests across all Linked Accounts, concurrent requests per Linked Account, and Requests are processed serially with a 90-second maximum execution time and a maximum of 5 queued requests.
Limit state is signalled in the Agave-RateLimit-Total, Agave-RateLimit-Remaining, {SourceSystem}-RateLimit-Total, and {SourceSystem}-RateLimit-Remaining response headers, and an exhausted limit returns HTTP 429.
The profile also includes 1 backoff/retry policy defined and response codes documented for throttled and serviceUnavailable.
Tagged areas include Accounting, Construction, Integration, and Rate Limiting.
Agave-RateLimit-TotalAgave-RateLimit-Remaining{SourceSystem}-RateLimit-Total{SourceSystem}-RateLimit-Remaining
Limits
Policies
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.