Intramedial is in restricted beta. At sign up or sign in, you have to provide the beta tester password you received or request one at preview@intramedial.com. Thank you.
Loading…
Seal a signed evidence bundle
Seal the audit log into a Merkle-rooted, signed bundle and check it offline with the published key.
3 stepscurlJavaScriptPythonShell
ledger.bundles-snapshot
Intralock · Leases · Parley · Fleet Map
A Trustvice Product
Agents act when the plane says yes, and the record says why.
Put admission in front of your MCP servers, repositories, SaaS tools and cloud accounts. Every agent gets a lease or a reason – and you keep the lever to stop any of them.
An auditor or a customer asks for the record, and you want to hand over something they can check without asking Intramedial. A bundle seals a range of the hash-chained audit log under a Merkle root and an Ed25519 signature.
The code reads the key from INTRAMEDIAL_KEY. Keep it in your shell or your secret store, never in a file you commit. Calls that need a signed-in person cannot use a key: the console makes them.
03
Walkthrough
Steps
1
Seal a log range
Post an empty body for the full history to date, or give scope, rangeStart and rangeEnd for a slice. With no signing key for your region the call answers 503.
04
Sample output
What comes back
The bundle holds the Merkle root, the record count and the signature. otsProof is null until the daily anchor confirms a Bitcoin block.
The matching public key is published without authentication at a well-known JWK address. Pick the entry named by signingKeyId; the public verify route and the offline verifier use the same key.
That the coordination ledger is in it: a bundle seals the audit log, which ledger.blame does not read.
That the Bitcoin anchor is confirmed.
The ledger is append-only and sealed under Merkle roots. The time on an entry is Intramedial's own clock, and a signed bundle can be checked offline with the published key.
A Trustvice Product
