Overview
The Calculation API turns poker math into JSON. Send a scenario, get back a typed, versioned
result — the same engines that power Poker Lab, available over REST. Authenticate from trusted
server code with a product API key (pw_test_ / pw_live_); each successful call draws a small
number of credits.
Use this plane for safe tools and composed explanations: equity breakdowns, ICM deal suggestions, payout and blind planning, starting-stack calculators, and educational widgets. Use the Management API when you need to operate a room, schedule tournaments, receive webhooks, or verify tournament results.
Endpoints
| Endpoint | What it does |
|---|---|
| Hold'em equity | Win/tie/loss probabilities for hands or ranges |
| ICM deals | ICM-fair prize-pool splits from chip stacks |
| Tournament payouts | Payout schedules from entrants and prize pool |
| Blind structures | Blind-level schedules for a target duration |
| Chip starting stacks | Chip denominations and per-player counts |
Code
What you can rely on
- Stateless by design. Calculation calls do not create rooms, publish tournaments, mint browser sessions, or manage player data.
- Deterministic where it can be. Calculations use exact enumeration when the scenario is small enough, and a seeded Monte Carlo estimate (with sample count and margin of error) otherwise.
- Reproducible and auditable. Responses include the engine identifier, so you can store, share, and re-run a scenario later.
- Math and explanation, not live strategy. The API computes probabilities, structures, and safe explanations; it never gives live action advice like "call" or "fold," solver-like RTA output, or bot-driving decisions for a human seat.
Conventions
Every endpoint returns the same envelope — requestId, creditsCharged, the engine identifier, and a
result — so you can handle responses uniformly. See How the API works
for authentication, the response envelope, and usage semantics, and the
Calculation API Reference for the full schemas.