Prometeo · Rate Limits

Prometeo Rate Limits

Prometeo does not publish specific numeric rate limits on its public documentation. Practical throughput on the Banking API is additionally bounded by upstream bank connections and by the asynchronous scrape/poll pattern (submit an operation, then poll a task/result endpoint). Production quotas are set per commercial agreement. Values are not reconciled in this artifact.

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

It captures 2 rate-limit definitions, measuring requests.

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

Tagged areas include Open Banking, Payments, FinTech, LatAm, and Rate Limiting.

2 Limits Throttle: 429
Open BankingPaymentsFinTechLatAmRate LimitingQuotas

Limits

Per-account request rate account
requests
see provider / commercial agreement
Not published publicly; negotiated per production agreement.
Banking upstream latency session
requests
bounded by bank connection
Banking operations depend on live bank connections; long-running scrapes are resolved via an async task/result poll rather than a fixed synchronous quota.

Policies

Asynchronous polling
Long-running banking operations return a task handle; clients poll a task/result endpoint until completion rather than holding a synchronous connection.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429.

Sources