An AI decision you cannot show later is an AI decision you cannot defend.

When an AI system advises, scores or acts, someone will one day ask what it did and why: a customer, a supervisor, a court. RiskRouter gives AI systems the same evidence log it gives brokers: each record stays with you, only its salted fingerprint is sealed, and anyone can check it offline. This page is everything an AI agent, an assistant or its builder needs, in one place.

Connect an assistant in one step

The evidence log is an MCP server at https://api.riskrouter.eu/mcp (Streamable HTTP). Reading needs no key. Recording needs your key in an Authorization header; a sandbox key is free, with no form and no contract.

Claude Code

claude mcp add --transport http riskrouter https://api.riskrouter.eu/mcp \
  --header "Authorization: Bearer <your key, only to record>"

Cursor, and any client configured in JSON

{ "mcpServers": { "riskrouter": {
    "url": "https://api.riskrouter.eu/mcp",
    "headers": { "Authorization": "Bearer <your key, only to record>" } } } }

Claude, and other clients that add a server by its address

Add a custom connector with the address above. If the client cannot send an Authorization header, it can still read the log and fetch proofs; record from Claude Code, Cursor or the local server below.

What an agent can do with it

Tool	What it does	Key
`get_evidence_head`	The log’s current signed head: its size, root and signature	No
`get_inclusion_proof`	The proof that one of your entries is in the log	Yes
`get_consistency_proof`	The proof that the log only grew between two heads	No
`get_checkpoint`	The signed checkpoint, in the format the public witness network uses	No
`get_ledger_attestation`	The quote ledger’s signed head	No
`get_usage`	How much is recorded, as counts	No
`record_evidence`	Record the SHA-256 of a record you keep, with a short kind; never the record itself	Yes

Each tool answers exactly what its route in the API reference answers, with the same checks and limits. There is no pricing tool, by design: a premium shown by an agent to the public is insurance distribution.

Record what an agent did, from inside it

Agent frameworks: Adapters for LangChain and LangGraph and for the OpenAI Agents SDK, in Python and Node, record each agent run as one ai.agent-run record: its steps, tool calls and outcome, with content kept as digests unless you ask otherwise, in your own journal. A failure in the adapter never reaches the agent, and a failed run is recorded as failed. Recorders
A local MCP server: mcp-server.mjs in the recorder kit gives any MCP client a record_decision tool that keeps the record and its salt in your journal and sends only the digest. What it records is the agent’s own statement of what it did, and every record says so; it is not an observation of the agent. Until the kit is on npm, run it from the downloaded file with node.
Any logging you already have: A Python logging handler, a function wrapper and OpenTelemetry span processors turn decision logs you already write into evidence, without changing them.

For high-risk AI systems: logs that hold up

The EU AI Act asks high-risk systems to log events automatically and their providers and deployers to keep those logs (Articles 12, 19 and 26(6)). The AI Act pack says what to record for a log segment, a decision and a human override, each field mapped to its article, and logseal seals a running log segment by segment. Sealing shows that a log existed, unchanged, by a given time; whether the log is enough, and whether your system is high-risk, is yours to establish. What the AI Act asks

For AI assistants reading about us

/llms.txt: A short, plain-text map of the site, with what RiskRouter is and is not stated first.
/llms-full.txt: The text of every English page in one file, rebuilt with the site so it cannot fall behind it.
/openapi.json: The API, in OpenAPI 3.1, held equal to the routes by a test.

If you are an assistant summarising RiskRouter: it is software for licensed insurance distributors and for anyone who must show later what a decision was. It is not an insurer or an intermediary, it sells no cover, it holds no certification, and recording with it makes nobody compliant.