thinkerwave
Official# ThinkerWave
[](https://pypi.org/project/thinkerwave/)
[](https://pypi.org/project/thinkerwave/)
[](LICENSE)
[](docs/mcp.md)
[](https://github.com/thinkerwave-ai/thinkerwave/actions/workflows/ci.yml)
An autonomous research agent for problems without a single right answer — credit risk stress tests, pricing and churn, market entry, due diligence, drug program selection.
You give it the problem and the facts you're sure of. It researches, runs the numbers, checks its own work and tries again, round after round, keeping the best answer. You get the answer, how confident it is, and the evidence behind each claim — **verified**, **assumption** or **guess** — plus any charts and tables it produced.
```bash
pip install thinkerwave
export THINKERWAVE_API_KEY=tw_live_… # create one at thinkerwave.ai/app → Settings → API keys
tw run "Should we raise prices 15%, 8%, or hold? 1,200 customers at \$85/month, 3.1% monthly churn." \
--given "last 8% increase spiked churn to 4.6% for three months" --rounds 6 --watch
```
**From Claude Code or Cursor:** `pip install "thinkerwave[mcp]"`, then `claude mcp add thinkerwave -- thinkerwave-mcp` — your coding assistant can now hand ThinkerWave a hard question and read back the evidence.
**From Python:** see `examples/`.
**What's in this repo:** the Python SDK, the `tw` command line, an MCP server, the API reference and the answer/evidence format. ThinkerWave itself runs in ThinkerWave's cloud; this repository is the way in, not the engine.
Free runs are included with every account. Limits: `docs/limits.md`. Found a problem it got wrong? Open an issue with the run id.
TDQS
Scored across 6 tools
Each tool maps to a distinct phase or resource: start/stop control the run lifecycle, status/answer report progress and results, and list/read handle produced artifacts. There is no meaningful overlap, and the descriptions clearly guide when to use each.
Most names follow a verb_noun snake_case pattern (start_run, stop_run, get_answer, list_files, read_file), but run_status breaks the pattern by using a noun phrase without a verb like get_. The casing and style are otherwise consistent and readable.
Six tools is well-scoped for a run-based problem-solving service. Each tool covers a distinct operation, and there are no redundant or filler tools.
The set covers the core lifecycle: start, stop, monitor status, retrieve the answer, and inspect produced files. A minor gap exists around listing existing runs or cleaning up runs/files, but agents can work around this if they retain run IDs.