Invoiced Rate Limits
The Invoiced REST API applies per-account rate limiting to protect platform stability. Specific request-per-second / per-minute thresholds are not published in the public API reference and vary by account. Clients should watch for HTTP 429 responses and back off accordingly. List endpoints are paginated via page and per_page (max 100 per page), which serves as a practical throughput control. Specific numeric limits are not reconciled in this artifact.
Invoiced Rate Limits is the machine-readable rate-limit profile for Invoiced on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 2 rate-limit definitions, measuring requests and records.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Accounts Receivable, Billing, Payments, Subscriptions, and Rate Limiting.
Limits
Policies
Sources
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/invoiced-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.