Skip to main content
Each plan sets how many tool runs and new integrations an account gets. This page lists the allowances, what counts against them and how to recover when you reach one.

​
Plan allowances

A Business account’s allowances are one pool that every member shares, and Pomerado can set a limit for the account. Personal accounts keep one saved login per website; see saved logins.

​
What counts

  • A tool run counts when it ends with a result, on the day Pomerado accepted it. A run that fails or is cancelled doesn’t count.
  • A build counts once, when it publishes a tool, in the month it publishes. A build that fails counts nothing.
  • Repeating a request with the same idempotency key doesn’t count again. Reading a job or answering its questions doesn’t count.
Work in progress holds a reservation against the allowance until it ends.

​
Check your usage

The Dashboard’s Settings > Usage page shows each allowance, how much is used and when it resets. From the API, GET /v1/quota returns the same, and GET /v1/usage returns tool runs over a time range. Both need usage:read.

​
When you reach a limit

A new run or build is refused with quota_exceeded (HTTP 429), and no job is created. details.reset_at says when the allowance resets.
1

Wait or upgrade

Wait for the reset, or upgrade a Personal account to Premium in the Dashboard’s Settings. A Business account’s limit is set by Pomerado; email founders@pomerado.ai.
2

Send a fresh request

Send the request again with a new idempotency key. The old key keeps its refusal.
  • When Pomerado can’t check quota, work is refused with temporarily_unavailable. Retry the same request later; nothing was done.
  • quota_expired means a reservation expired before the request was accepted. Confirm no job was accepted, then send a fresh request with a new key.
  • See errors for every code and retries and idempotency for safe retries.