API access

Your Decision Map isn't locked inside the app. A workspace API key lets your own tools ask it questions - the same reasoning, citations included, delivered wherever work happens.

Creating a key

Go to Settings → API access and choose Create key. The key (rk_…) is shown once - store it somewhere safe. Keys are scoped to the workspace they were created in, and you can revoke one at any time; revocation takes effect immediately.

Using the API

Send the key as a bearer token: Authorization: Bearer rk_… against https://api.therationale.ai. Three endpoints are available today:

GET /v1/workspace - identify the workspace a key belongs to.
POST /v1/reasoning/scope - resolve what part of the map a question is about (a project, a system, a decision).
POST /v1/reasoning/query - ask a question and get the reasoning back: relevant decisions, supporting knowledge, and source citations. Answers carry the same honesty as the app - what the map knows, how well it's supported, and what it doesn't know.

Reasoning clients

The API exists so reasoning can show up where the question does - a sidebar in your issue tracker instead of another tab. A Jira/Confluence client is in early access; contact us if you'd like to try it with your team.

Good to know

API access is read-only: clients can ask, never modify the map.
Keys are workspace-scoped - one key can never read another workspace.
Requests are rate-limited; a well-behaved client won't notice.