API
Sleuth’s REST API lets your own software run Sleuth research without the Studio screen. It comes with Enterprise and powers the MCP server.
Most teams don't need the API: agents and AI tools connect through the MCP server on any plan. The API is for applications and internal systems that call Sleuth directly, like a pipeline that refreshes a dataset every night or a portal that shows Sleuth results.
What it does
Everything the MCP server's project tools do, as REST calls:
- Create, list, rename, and delete projects, and send questions.
- Follow a run's status, and approve, reject, or cancel at the plan and column steps.
- Upload documents, including files over 10 MB, which the MCP server can't take.
- Fetch datasets (also as CSV), charts (as SVG), and a whole project in one call.
Keys
| Key | Acts as | Approvals |
|---|---|---|
| Organization key | Your organization | Plans and columns are approved automatically. |
| Personal key | One Sleuth user, so runs show up as theirs in Studio | Follows that user's auto-approve setting. |
Sleuth creates keys for you. Send the key as a bearer token. The same key also works on the MCP server, for agents that run without a person signing in.
Getting access
API access is turned on per organization, with Enterprise. Your Sleuth contact sends the keys and the API reference. Enterprise
Credits
The same as Studio and the MCP server: one credit per analytical cell a run fills. How credits work
Updated November 9, 2026