Warrant · Rate Limits

Warrant Dev Rate Limits

Warrant did not publish fixed numeric per-endpoint rate limits for its hosted API. As a real-time authorization service, the check endpoint (POST /v2/authorize) was designed for high-volume, low-latency traffic on the application hot path; sustained throughput was governed by plan and fair-use rather than a documented per-minute request cap. On the open-source self-hosted server (github.com/warrant-dev/warrant, default port 8000), throughput is bounded only by your own infrastructure and datastore (MySQL, Postgres, or SQLite), with no vendor-imposed limit. RETIRED - the hosted service was sunset 2025-11-15; any current limits are governed by WorkOS FGA.

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

It captures 3 rate-limit definitions, measuring 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

Authorization Check Requests account
requests
not published
The /v2/authorize hot-path check had no documented fixed numeric rate limit; governed by plan and fair-use. RETIRED.
Management API Requests account
requests
not published
No fixed numeric request-rate limit was documented for the v1 management endpoints (objects, warrants, object-types, roles/permissions). RETIRED.
Self-Hosted Throughput deployment
requests
hardware-bound
The open-source server (port 8000) is bounded only by your own infrastructure and backing datastore, not by Warrant.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Local Enforcement
SDKs supported client-side caching / local decision paths to reduce check-endpoint load for latency-sensitive hot paths.

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/warrant-dev-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.