Pismo Rate Limits
Pismo is a cloud-native, horizontally-scaled platform. Public documentation describes OAuth2 access tokens that expire after one hour (3600 seconds) and account-specific tokens for account-scoped calls, but does not publish specific per-endpoint request-per-second or per-minute quotas. Throughput, burst, and concurrency limits are governed by the client's commercial agreement and environment (sandbox vs. production). Specific values are not reconciled in this artifact.
Pismo Rate Limits is the machine-readable rate-limit profile for Pismo on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions, measuring requests, concurrent_requests, seconds, and tokens.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Banking, Card Issuing, Payments, Fintech, and Core Banking.
Limits
Policies
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/pismo-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.