Flipside Crypto · Rate Limits

Flipside Rate Limits

The Flipside Data API governs usage primarily through a query-seconds (warehouse-seconds) credit budget rather than fixed RPS limits: each account has a free monthly allotment of query seconds and may purchase more. Result retrieval is paginated, with each result page capped at roughly 30MB and a default page size of 1000 rows. Concurrency and request-rate ceilings are enforced per account and per tier. Specific numeric request-per-second and concurrency values are not publicly fixed in this artifact.

Flipside Rate Limits is the machine-readable rate-limit profile for Flipside Crypto on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring query_seconds, rows, bytes, and concurrent_queries.

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

Tagged areas include Blockchain, Analytics, SQL, Web3, and Data.

4 Limits Throttle: 429
BlockchainAnalyticsSQLWeb3DataRate LimitingQuotasThrottling

Limits

Query Seconds Budget account
query_seconds
500 free per month, more via paid tiers
Primary usage governor; warehouse-seconds consumed by query execution.
Result Page Size request
rows
1000 default
Configurable per getQueryRunResults page; large result sets paginate.
Result Page Payload request
bytes
~30MB per page
Each result page is capped at approximately 30MB.
Concurrency account
concurrent_queries
see provider documentation
Concurrent query execution varies by account tier.

Policies

Credit-Metered Usage
Usage is debited against a query-seconds budget; exhausting it blocks new runs until topped up or reset.
Result Caching
createQuery maxAgeMinutes and resultTTLHours control reuse of cached results to avoid re-spending query seconds.
Backoff Strategy
Clients should poll getQueryRun with intervals and implement backoff; cancel long-running queries via cancelQueryRun to control cost.

Sources