Stigg · Rate Limits

Stigg Rate Limits

Stigg enforces per-operation rate limits on its GraphQL API (and REST API). High-read operations allow up to 6000 requests per minute, mid-tier read operations 3000 per minute, and mutations 250 per minute. Event reporting uses a per-second window. Entity-level limits prevent concurrent mutation storms at 30 calls per minute per entity identifier. Limits are enforced per API key.

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

It captures 5 rate-limit definitions, measuring requests and bulk-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 4 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include FinOps, Pricing, Billing, Entitlements, and Usage-Based Billing.

5 Limits Exhausted: HTTP 429
Method: generated, dated 2026-06-13.
Written by API Evangelist on 2026-06-13 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
FinOpsPricingBillingEntitlementsUsage-Based BillingSaaSRate Limiting

Limits

Edge / Public Read Operations api-key
requests
6000
Highest-traffic read paths served via Edge CDN.
In-App Read Operations api-key
requests
3000
Mutation Operations api-key
requests
250
Event Reporting api-key
bulk-requests
1000
reportEvent uses a per-second window rather than per-minute. Limit is per bulk batch size.
Per-Entity Mutation Limit entity
requests
30
Prevents repeated concurrent mutations on a single customer or subscription entity. Applies to customerId, subscriptionId, and customerId:resourceId combinations.

Policies

Per-Endpoint Limits
Stigg sets distinct rate limits per operation rather than a single global account ceiling.
Per-Entity Limits
In addition to global per-endpoint limits, each entity (customer, subscription, resource) has its own 30/min concurrent mutation cap to prevent stampede scenarios.
Backoff Strategy
Clients receiving HTTP 429 should back off and retry; exponential backoff with jitter is recommended.
Limit Escalation
Higher rate limits are available upon request by contacting support@stigg.io.

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/stigg-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.