Accredible Rate Limits
Accredible does not publish fixed numeric rate limits for its REST API in the public API reference. The practical governor on issuance volume is the plan's annual unique-recipient allowance rather than a per-minute request cap. Clients should treat the API as rate-limited in principle - implement exponential backoff, honor any Retry-After header, and prefer the bulk-create endpoint over many single-credential calls for large batches. The API authenticates each request with an API key in the Authorization header (`Token token=YOUR_API_KEY`); an invalid key returns 401.
Accredible Rate Limits is the machine-readable rate-limit profile for Accredible on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring requests, recipients, and credentials.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled and unauthorized.
Tagged areas include Digital Credentials, Certificates, Badges, Rate Limiting, and Quotas.
Limits
Policies
Sources
- https://docs.api.accredible.com/
- https://help.accredible.com/s/article/api-faq
- https://help.accredible.com/hc/en-us/articles/115003470989-What-are-the-API-endpoints-
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/accredible-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.