Topaz · Rate Limits

Topaz Rate Limits

Topaz does not publish fixed numeric rate limits. Because Topaz is self-hosted (you run the authorizer yourself, typically as a local sidecar or nearby service), authorization throughput is bounded by your own hardware and configuration rather than by a vendor quota. The authorizer is designed for low-latency, high-volume in-process/near-process decisions; the embedded directory and OPA engine evaluate against local data. Any per-tenant quotas or request caps would come from the Aserto hosted control plane, not from the open-source Topaz authorizer.

Topaz Rate Limits is the machine-readable rate-limit profile for Topaz on the APIs.io network, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring decisions and requests.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Access Control, Authorization, Fine-Grained Authorization, Rate Limiting, and Quotas.

3 Limits Exhausted: HTTP 429
Method: generated, dated 2026-07-11.
Written by API Evangelist on 2026-07-11 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Access ControlAuthorizationFine-Grained AuthorizationRate LimitingQuotas

Limits

Authorizer Decisions deployment
decisions
hardware-bound
Bounded by your own CPU/memory and replica count; no vendor-imposed cap on self-hosted Topaz.
Directory Reads/Writes deployment
requests
hardware-bound
Directory object/relation/check throughput is a function of the embedded store and your infrastructure.
Aserto Control Plane tenant
requests
per plan
Any request or seat quotas apply to the Aserto hosted control plane, not to the open-source authorizer.

Policies

Sidecar/Local Deployment
Topaz is typically deployed as a sidecar or nearby service so decisions are made with minimal network latency and no external rate limit.
Backoff Strategy
Clients calling a shared Topaz instance should implement exponential backoff with jitter and honor Retry-After on any 429 responses returned by an upstream proxy or the Aserto control plane.

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.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/topaz-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.