How to get your data out of Arbiter
Your investigations are yours. This guide covers every way to take them out of Arbiter: a spreadsheet from the console, the full record as JSON through the API, a public link, and deletion.
Arbiter saves each investigation as a session: its sources, claims, evidence and every verdict (called a judgement) the engine produced for it.
A spreadsheet from the console (paid plans)
- Sign in to the console and open a session.
- Open the Audit tab.
- Click Export CSV.
The file lists one row per claim: who made it, what it is about, how strongly the evidence supports and opposes it, and how uncertain it remains. It is named arbiter-audit-<session id>-<time>.csv. The CSV export needs a paid plan; on the free plan the button returns a message saying so.
The full record as JSON (REST API)
Every session is readable through the REST API, the plain JSON interface for your own software. Create an API key under Connection in the console and send it in the x-api-key header. The base address is https://api.arbiter.housecarl.cloud.
| To get | Call |
|---|---|
| A list of your sessions | GET /api/v1/sessions |
| One session: sources, claims, evidence and latest result | GET /api/v1/sessions/{id} |
| Every judgement of a session | GET /api/v1/sessions/{id}/judgements |
| The audit trail of the latest judgement | GET /api/v1/sessions/{id}/judgements/latest/audit |
| Your workspaces, and the sessions in one | GET /api/v1/workspaces, GET /api/v1/workspaces/{id}/sessions |
For example, to save one session to a file:
curl -sS https://api.arbiter.housecarl.cloud/api/v1/sessions/SESSION_ID \
-H "x-api-key: se-YOUR_KEY" > session.json
The audit endpoint returns JSON on every plan. Send Accept: text/csv to the same endpoint to get the CSV described above instead; that form needs a paid plan and returns HTTP 402 without one. The full list of endpoints is in Connect your tool.
Through your AI assistant
If Arbiter is connected to an assistant over the Model Context Protocol (MCP), the assistant can list your sessions and read any of them back, then save or reformat the result for you. See Arbiter with an MCP connection.
A public read-only link
To share an investigation rather than download it, publish a snapshot: from the console, or with PUT /api/v1/sessions/{id}/share. The snapshot is read-only. Your private notes on a session are never included in it.
Deleting your data
Delete a session from the console, through your assistant, or with DELETE /api/v1/sessions/{id}. Deletion removes it from the production database at once; daily backups keep deleted data for up to 30 days before they expire. The details are in the privacy policy.
Related: MCP or REST API: which to use · Arbiter for researchers