3-shake · Rate Limits
3Shake Rate Limits
3Shake Rate Limits is the rate-limit profile for 3-shake on the APIs.io network.
The provider publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
Limit state is signalled in the ratelimit_draft, x_ratelimit, retry_after, and observed response headers.
Tagged areas include Company, SRE, Data Integration, ETL, and iPaaS.
0 Limits
ratelimit_draftx_ratelimitretry_afterobserved
Transcribed from the provider's documentation on 2026-09-05 — openapi/3shake-reckoner-external-api-openapi.yml.
View Source
Limits
3-shake publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
Reckoner enforces rate limiting and says so in the contract — a 429 TooManyRequests response with a RATE_LIMIT_EXCEEDED code and a worked example is declared on 14 of the 15 operations — but publishes NO number and NO runtime signal. There is no RateLimit-* or X-RateLimit-* header, no Retry-After, and no limits page in the API reference or the help centre index. limit_count is therefore an honest 0: the ceiling exists and is undiscoverable until a client hits it. A client can only detect exhaustion after the fact and must invent its own backoff. Separately, the plan quotas in plans/3shake-plans-pricing.yml (10-50 GB and 200-1,000 workflow runs per month) are the published consumption ceilings, but those are billing quotas measured per month, not per-second request limits, and they are enforced against workflow execution rather than API calls.
CompanySREData IntegrationETLiPaaSWorkflow AutomationVulnerability ScanningAttack Surface ManagementCloud SecurityDevSecOpsSBOMKubernetesJapan
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.