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…
Public verification
Bundle checker
Verify a ledger bundle.
Paste an Intramedial signed ledger bundle below. Verification runs in your browser against our published public keys. The bundle you paste is never sent to Intramedial – only the public key set is downloaded.
Or try a sample:
How it works
Client-side
Three steps, all client-side.
Step 01
Check the records
Read the JSON, count the records and recompute the Merkle root over their hashes. It must equal the signed merkleRoot, and recordCount must match.
Step 02
Look up the key
The bundle names a signingKeyId. Match it against the published key set. The key id must derive from the key itself, and the key's jurisdiction must be the bundle's.
Step 03
Verify ed25519
Canonicalise the eleven signed members (RFC 8785, JCS) and verify the Ed25519 signature. A bundle's otsProof, if present, is reported and not checked here.
Programmatic verification
npm package
Verify in your code.
The TypeScript verifier and a command-line tool both run offline. Each checks a bundle in your own code, with no call back to Intramedial.
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.
The samples are a three-record ledger bundle signed by a throwaway test key and checked against that key, not against Intramedial's published keys. The tampered one changes one record hash, so the records no longer produce the signed Merkle root.
Public keys fetched from /.well-known/ledger-bundles-keys.json
Bundle checker
