How do I analyze a poker board with an API?
Send a flop, turn, or river board to the public PokerKit board-only operations; choose the response shape that the review or training workflow needs.
board only to POST /v1/pokerkit/board-report for texture plus nuts in one response; use POST /v1/pokerkit/category-combos for live two-card combos grouped by made category, POST /v1/pokerkit/texture for board labels, or POST /v1/pokerkit/nuts for the strongest makeable hand and tying combos. These board-only results are not equity or strategy.Quick facts
| Required input | board: a no-separator string of 3, 4, or 5 community cards, for example AsKsQs |
|---|---|
| Board Report | POST /v1/pokerkit/board-report returns texture and nuts |
| Category Combos | POST /v1/pokerkit/category-combos groups live two-card combos in by_category |
| Use boundary | Training, coaching, completed-hand review, study, and research only; no real-money RTA |
Choose the board operation
| Need | Public operation | Result |
|---|---|---|
| One board overview | POST /v1/pokerkit/board-report | texture plus nuts. |
| Live made-hand combos | POST /v1/pokerkit/category-combos | by_category groups live two-card combos by made category. |
| Board labels | POST /v1/pokerkit/texture | Wetness, connectivity, rank band, draw labels, and suit-shape booleans. |
| Best makeable hand | POST /v1/pokerkit/nuts | Strongest makeable hand, tying combos, and documented flags. |
All four operations are board-only: concatenate standard two-character card codes without separators, such as AsKsQs. Do not add hole cards. Optional hand_type and dead are only those defined by the current public OpenAPI schema.
Verified Board Report request and response
This public pokerkitBoardReport example calls POST /v1/pokerkit/board-report.
{"board":"AsKsQs"}{"result":{"texture":{"cards":["As","Ks","Qs"],"wetness":{"name":"WET","value":"Wet"},"are_monotone":true},"nuts":{"hand":"TsJsKsQsAs","combos":[{"cards":["Ts","Js"]}],"candidate_count":1176,"board_is_nuts":false,"is_royal":true,"label":{"name":"STRAIGHT_FLUSH","value":"Straight flush"}}}}The response reports a monotone board and the strongest makeable hand plus its tying combo. It does not say how often that hand wins, which range should act, or which action to take.
Category combos, texture, and nuts are different questions
Use Category Combos when a review UI needs live two-card combinations by made category; its public example returns by_category entries such as HIGH_CARD. Use Texture for board descriptors only. Use Nuts for the strongest makeable hand, tying combos, candidate_count, board_is_nuts, is_royal, and its label. Board Report is the compact choice when both texture and nuts are needed.
What this does not answer
Board analysis does not calculate equity, estimate hand strength, compare ranges, produce a solver result, or recommend an action. For a submitted player hand, see the Poker hand analysis API guide; for focused board labels, see the PokerKit texture API guide.
Errors, integrations, and no-RTA
A documented 422 means to validate board and optional fields against the current API Reference or OpenAPI snapshot; do not retry an unchanged invalid request. See developer docs for official SDK and MCP setup, and quotas for account handling. Pokerai API is for training, coaching, completed-hand review, study, and research only. Real-time assistance at real-money tables is prohibited; do not connect board analysis to live-table automation or present it as an action instruction. llms.txt lists public entry points.
Real-time assistance at real-money tables is prohibited.