How do I calculate tournament ICM with the PokerKit API?
Send ordered tournament payouts and chip stacks to POST /v1/pokerkit/icm to receive ICM equity values in the same player order.
payouts and chips arrays. In the documented response, each value in result.icm corresponds by array position to that player's submitted chip stack and the tournament payout structure.Quick facts
| Endpoint | POST /v1/pokerkit/icm |
|---|---|
| Required inputs | payouts and chips, both number arrays in the public OpenAPI schema |
| Response | A result object with an icm number array |
| Use boundary | Tournament equity calculation for training, coaching, hand review, study, and research; no real-money RTA |
Input semantics
chips supplies the tournament chip stacks, and payouts supplies the payout values. Both fields are required by the public IcmRequest schema. Keep the player order stable: the documented response returns an icm array, so its positions are interpreted against the submitted chips positions.
Minimal request and response
Use JSON and an API key. This request and response are the public pokerkitIcm docs-code example.
curl -s https://pokerai.bet/v1/pokerkit/icm \
-H "Authorization: Bearer $POKERAI_API_KEY" \
-H "Content-Type: application/json" \
-d '{"payouts":[50,30,20],"chips":[5000,3000,2000]}'{"result":{"icm":[38.392857142857146,32.75,28.857142857142854]}}Interpreting ICM equity
For the example, the first submitted stack, 5000, maps to the first returned ICM value, 38.392857142857146; the second and third positions map the same way. Treat those values as the endpoint's ICM equity output for this payout-and-stack input. Do not relabel them as chip counts, a winning probability, a solver strategy, or a recommended poker action.
Scope and use
Use this endpoint when a tournament training, coaching, or completed-hand review workflow needs an ICM equity calculation from a stated payout structure and set of stacks. It does not provide hand ranges, cards, betting actions, tournament strategy, or an in-game recommendation. Keep it out of live real-money decision assistance.
Quota and errors
This endpoint uses the same API key and account quota system as the public PokerKit API. Check the quota documentation, pricing, and dashboard for current account limits instead of hard-coding a limit.
The public OpenAPI contract declares a 422 validation error response. Check that both required arrays conform to the current Reference or OpenAPI schema before correcting and resubmitting a request. For authentication and account-quota handling, use the current error documentation; do not retry an unchanged invalid request.
No real-money RTA
Pokerai API is for training, coaching, hand review, study, and research only. Real-time assistance at real-money tables is prohibited. Do not turn ICM output into a live-table action instruction or automation signal.
Related resources
Use the current public contracts and account documentation alongside this Guide.
| Resource | What it covers | Use it for |
|---|---|---|
POST /v1/pokerkit/icm | ICM equity calculation from payouts and chips | Inspecting the current public request and response contract |
SDK, MCP, and related resources
- Developer docs — official SDK and MCP setup alongside authentication and quotas
- API Reference — inspect the current ICM request and response contract
- OpenAPI snapshot — machine-readable English contract
- Python SDK — official package entry point
- TypeScript / JavaScript SDK — official package entry point
- MCP server — official package entry point
- Poker hand review API guide — place ICM calculation in a post-session workflow
- llms.txt — concise LLM entry point