Until now, Decision Horizon records lived where they were written: a .jsonl file per session on your own host. That's still the default, and for many teams it's the right place. But a security or risk team usually wants one place to search every agent's decisions, check a session, and put it on hold when something's in dispute. So today there are two new pieces: a hosted record store at api.decisionhorizon.dev, and the Console.
The hosted record store
You upload your signed chains to it, and it keeps them per tenant. The important part is what it doesn't do:
- It never holds your signing key. You pin your public key once. Pins are permanent: a different key can't be swapped in under the same id.
- It checks every record on upload. A record that doesn't verify under your pinned key, or doesn't link to the chain already stored, is rejected, and nothing from that upload is stored.
- It's append-only. No endpoint edits or deletes a stored record. Chains come back byte for byte as you sent them, so your signatures still verify.
- It isn't trusted for the truth. When it verifies a stored session, the response says the expected head came from the server's own store. Compare it with a head you saved yourself, or download the chain and run
dh verifyon your own machine.
Behind that: API keys are stored only as hashes, every query is scoped to your tenant, and every pin, upload, verification and hold goes into a hash-chained audit log you can download.
Before it went live, we checked it against a conformance pack generated from the offline verifier: eleven chains, clean and tampered, with exact expected results. The hosted answer matches dh verify on every one, because it uses the same verification code.
The Console
The Console is the read side, in the browser. Sign in with your tenant API key; it stays in that browser tab and is cleared when you close it. Then you can:
- browse sessions, live or closed, with their record counts and heads;
- search decisions by tool, rule, verdict, target, outcome, what the agent had read, session or date, and share the view as a link;
- open a session and read each record in plain language: what the agent wanted to do, what it had read, what it was and wasn't allowed to do, and which rule decided;
- verify a session in one click, optionally against a head from your own records;
- download the chain and your public key to verify offline;
- place or lift a legal hold;
- check pinned keys and the audit log, or verify a file you hold without storing it.
You can try it without an account: open the Console with sample data. One of the sample sessions has been tampered with, so you can see what a failed verification looks like.
Using it
The hosted API reference covers every route, with curl examples for pinning a key, uploading records, verifying and querying. Hosted storage is available to pilot customers. If you'd like a tenant, book a call and we'll set one up with you.