What are Pokerai API quotas and pricing boundaries?
Pokerai API has separate monthly counters for presolved lookups and real-time solves. Use the public Pricing page for current paid-plan information; do not treat this Guide as a price list or infer unpublished tier details.
busy solver response is capacity availability, not a quota statement. For paid plans, open the current Pricing page: this Guide deliberately does not restate Builder, Pro, or Scale prices, limits, or entitlement details that are not established here.Quick facts
| Free presolved quota | 1,000 presolved lookups per month |
|---|---|
| Free real-time solve quota | 25 real-time solves per month |
| Two counters | Presolved lookups and real-time solves are separate monthly counters |
| Verifiable operation | The POST /v1/gto/preflop request is a documented presolved lookup; validate its request parameters and responses against the current OpenAPI snapshot |
| Quota boundary | Check the current quota docs, dashboard, and documented error response when a counter is exhausted |
| Busy boundary | A busy response means solver capacity is unavailable; it does not establish that quota was consumed or exhausted |
| Use boundary | Training, coaching, hand review, study, and research only; no real-money RTA |
Use the published Free quota as the stable baseline
The public Free tier states 1,000 presolved lookups and 25 real-time solves per month. Keep the counters separate in product messaging and integration UX; a lookup allowance is not interchangeable with a real-time solve allowance.
Use the dashboard and current quota documentation for an account's actual usage. Do not reproduce account accounting in a client or assume that usage, resets, or entitlements beyond the published contract apply to every account.
Read pricing from the current Pricing page
The Pricing page is the public source for current paid-plan presentation. This Guide links to it rather than copying Builder, Pro, or Scale amounts, quotas, feature bundles, availability, or billing terms into a second page.
That omission is intentional: when a paid-plan fact is absent here or changes in its source, this Guide does not stabilize it by inference. Confirm a current paid-plan question on Pricing or through the appropriate account or sales channel.
Quota exhausted is different from solver busy
A quota response concerns a monthly counter. Check the documented quota error, the quota docs, and account usage before deciding that an integration must wait for a reset or use a different eligible workflow.
A busy response concerns current solver capacity. It does not by itself prove quota exhaustion, a charge, a refund, a plan entitlement, a queue position, or a completion time. Apply bounded retry behavior only as documented by the current API and avoid promising capacity or latency that the public contract does not publish.
When this Guide is useful
Use it when designing a study, coaching, hand-review, research, SDK, or MCP workflow that must explain the Free quota, route users to current pricing, and avoid conflating usage limits with temporary solver capacity.
Use the linked Docs, Reference, and OpenAPI snapshot before associating a particular operation with a counter or error. Those sources, rather than a marketing shorthand, are the current public contract for integration behavior.
When not to use it
Do not use this Guide as a checkout quote, service-level commitment, price lock, billing receipt, or a source for unstated Builder, Pro, or Scale details. Do not infer tax, currency, payment method, refund, upgrade, downgrade, reset, rollover, concurrency, priority, or support terms that are not explicitly published in the linked source.
Do not use API output for real-money live-play assistance. Pokerai API is for training, coaching, hand review, study, and research only. Real-time assistance at real-money tables is prohibited.
Public-source provenance
The Free quota figures and the quota-versus-busy boundary are traceable to the public quota documentation, API Reference, and OpenAPI snapshot. Current paid-plan presentation is linked to Pricing instead of duplicated here.
The official Python SDK, JavaScript SDK, and MCP package links below come from locales/product-facts.json. They are discovery links, not claims about a package's version, registry publication state, or runtime behavior.
Current public sources
Use the source that owns the question. This Guide makes no paid-tier claim beyond directing readers to current Pricing.
| Source | What it establishes | Use it for |
|---|---|---|
Pricing | Current public paid-plan presentation | Verify a current paid-plan question |
Docs · Quotas | Free monthly counters and documented quota guidance | Explain usage-limit boundaries |
OpenAPI snapshot | Machine-readable API contract and documented responses | Validate an integration's current behavior |
Pricing, quota, API, and workflow links
- Pricing — current public paid-plan presentation
- Quota docs — published Free counters and quota guidance
- FAQ — public product and account answers
- Developer docs — authentication, quota, SDK, MCP, and error guidance
- API Reference — current operation-level contract
- OpenAPI snapshot — machine-readable English public contract
- Python SDK — official package entry point
- JavaScript SDK — official package entry point
- MCP server — official package entry point
- llms.txt — concise LLM entry point