Kintsugi Rate Limits
Kintsugi's REST API is authenticated per organization with an API key in the x-api-key header and the x-organization-id header. Specific published per-endpoint request-rate limits are not documented in the public reference; clients are expected to paginate list endpoints and handle standard HTTP throttling responses. Specific numeric limits are not reconciled in this artifact.
Kintsugi Rate Limits is the machine-readable rate-limit profile for Kintsugi on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 2 rate-limit definitions, measuring requests and items.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Sales Tax, Tax Compliance, Tax Automation, Rate Limiting, and Quotas.
Limits
Policies
Sources
- https://docs.trykintsugi.com/docs/making-authenticate-request-using-api-key
- https://docs.trykintsugi.com/docs/error-handling
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for rate limits
4 MCP tools reach this
find_rate_limitsBrowse and filter every rate limit in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/kintsugi-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.