Poker Solver APIs and Automation
A solver API lets you run and query solves programmatically instead of clicking. What an API adds, who needs one, and where automation stays legal.
On this page · 6 sections
A solver API is simply a way to drive a solver with code instead of clicks: you send it a spot and settings programmatically, and it returns the solved strategy as raw data you can process however you like. For the vast majority of players it’s overkill — the graphical app is faster for studying a few spots. But for anyone running solves at scale, an API turns a manual, one-at-a-time chore into an automated pipeline.
What an API actually adds
The solver engine itself is the same whether you click or script. The API layer wraps that engine so a program can:
- submit a solve — the board, ranges, stack depth, and bet sizes, expressed as data rather than form fields,
- run many solves in a batch — a whole grid of boards or stack depths unattended,
- read the output as structured data — action frequencies and EVs your own code can parse,
- pipe results downstream — into a database, spreadsheet, chart, or training tool.
That last point is the real payoff. Clicking through 500 river spots and copying numbers by hand is a week of tedium; a script does it overnight and dumps the results somewhere you can query them.
Who needs one — and who doesn’t
Be honest about which group you’re in, because most players are in the second.
| You probably want an API if you… | You don’t need one if you… |
|---|---|
| Build training tools or charts from solves | Study a few spots per session |
| Produce content requiring bulk solves | Want to understand one line deeply |
| Do research across many game trees | Prefer visual output to raw data |
| Feed solver data into another app | Play and review normally |
For a working player, the graphical app is not just sufficient — it’s better, because the visuals help you internalize the strategy. Automation optimizes throughput, not learning.
Open source is the natural home for automation
If you want to script solves, open-source engines are the path of least resistance. Because the code is open, you can call the engine directly from your own program, batch as many solves as your hardware allows, and parse the raw output with no black box in the way. This flexibility is exactly why developers and researchers gravitate to open-source poker tools — the trade-off is the usual one: more setup and less polish in exchange for total control.
Closed, commercial solvers sometimes expose their own scripting or API surface too, but access and terms vary, so check what your specific tool allows before building on it.
The legality line — same as always
Automation raises an obvious worry, and the answer is the familiar one: it’s about when, not how.
Running solves through an API to study away from the table is completely legitimate. You’re doing the same thing the app does, just faster and in bulk — building strategy for later. Wiring that same API into your live play to fetch an answer while a real-money hand is running is real-time assistance, and it’s cheating that gets accounts and balances seized.
A practical note on cost
Bulk solving isn’t free. Each solve consumes real compute and, for detailed spots, meaningful memory and time. Fire off thousands of high-resolution solves and you’ll feel it in either your electricity bill or your cloud spend. Serious automation projects budget for hardware or a compute service the same way they’d budget for any other tool — worth knowing before you queue up ten thousand solves.
The bottom line
A solver API is an automation layer, not a better solver: it lets you run and harvest solves programmatically, which matters enormously if you build tools or process solves in bulk and not at all if you study a handful of spots at a time. Open-source engines are the friendliest to script, and the legality rule never changes — automate all the study you want, but keep it out of live play. Learn the engine underneath in how a solver works, explore the scriptable options in open-source poker tools, stay on the right side of the RTA line, and see the full toolkit in the tools & software hub.
Frequently asked
What is a poker solver API?
An API is a programmable interface to a solver — instead of clicking through the app, you send it a spot and settings in code and get the solved strategy back as data. It lets you run many solves automatically and pull results into your own scripts, spreadsheets, or databases.
Who actually needs a solver API?
Mostly content creators, coaches, and tool builders who need to run hundreds or thousands of solves and process the output at scale. A player studying a handful of spots a day gains nothing from an API — the graphical app is faster and clearer for that.
Is using a solver API against poker room rules?
Running solves via an API for study away from the table is fine — it's the same as clicking the app, just automated. It only becomes a violation if you wire it into live play to get answers during real-money hands, which is real-time assistance and banned everywhere.
Can I script an open-source solver?
Yes. Open-source solvers are especially suited to scripting because you can call the engine directly from your own code, batch many solves, and parse the raw output. That flexibility is a major reason developers and researchers choose open-source engines over closed apps.