Shared Record
In development · pilot pairs by applicationOne record of what two companies' AI agents did. Signed by both. Checkable by anyone.
A record of what two companies' AI agents exchanged, signed by both sides, that anyone can check offline with no Norcaster account.
A pilot version is built and in testing. It is not in production or available to customers.
When your agent and a partner's agent disagree, whose log wins?
Companies' agents increasingly deal with other companies' agents: suppliers, merchants, partners, payment flows. When something goes wrong, each side has only its own logs.
How it works
How it works in the pilot version
Your agent sends a call with a signed receipt
Your company signs a receipt for the call, carrying your boundary's decision: allowed, redacted or blocked. A blocked call is not delivered; your partner gets a signed notice instead.
Your partner signs an acknowledgement
Your partner's side checks the receipt against the content it received, applies its own boundary and signs an acknowledgement.
Both register fingerprints on a shared log
Each side registers fingerprints (salted hashes) of what it signed on a shared log that both companies witness.
Anyone can check it offline
In a dispute, either side exports the signed records, and anyone can verify them offline with Norcaster's verifier, which will be published.
If no acknowledgement arrives by the deadline, the sender records that too.
Both companies sign
Each company signs what it sent or received. Each company's root key stays with that company.
Your content stays off the shared log
The shared log holds only fingerprints. Message content goes only to the partner you send it to.
Anyone can verify offline
Anyone you give the exported records to can check them offline, with no Norcaster account.
You don't have to trust us
Our goal: nobody in the middle has to be trusted, including us.
- Norcaster runs the pilot log. The log never receives message content, and Norcaster cannot rewrite or split its history without the witnesses detecting it.
- Pilot hubs hold their own root key, in their own KMS or Sync Agent.
- In hosted mode, Norcaster holds a company's short-lived signing keys, so that company relies on Norcaster for its own signatures. Self-hosted or customer-held keys remove that.
For your partners
They join free, run a small component on their own servers and keep their own keys. No Norcaster account needed.
Standards
- Designed on the IETF SCITT architecture (RFC 9943).
- Works with MCP tool calls in the pilot version. A2A and agent-SDK bindings are in design; one SDK binding is in testing.
- Payment credentials such as AP2 mandates and Mastercard Verifiable Intent are designed to travel inside an exchange as content (in design). Shared Record records them; it does not replace or check them.
Where it stands
In development · pilot pairs by applicationA pilot version is built and in testing. It is not in production or available to customers.
Built and in testing
- A draft protocol, designed on the IETF SCITT architecture
- Receipts signed by the sender and acknowledgements signed by the receiver
- Notices for blocked calls and records of missing acknowledgements
- A shared log witnessed by both companies
- Dispute exports
- A portal page in Norcaster (Govern → Shared record)
- A free, self-hosted component for partners
- An offline verifier in Python and Node
- A two-company demo
Not yet
- The verifier and the partner component are not published
- No outside review of the protocol
- No customer pilot
- Not in production
What Norcaster does today: Norcaster's evidence records are hash-chained and anchored to a public transparency log, and audit bundles can be verified offline without a Norcaster login. A record that two companies both sign is what Shared Record adds. How proof works →
Apply for a pilot pair
- One hub and one to three partners.
- Thirty days of real exchanges.
- A dispute drill at the end, in which an outside party verifies the evidence offline.
Pilot pairs are by application. Book a 20-minute call to talk it through.
Questions
- Is it legally binding?
- It is evidence. How it is used is up to you and your partner.
- Does my partner need Norcaster?
- No.
- Does this replace AP2 or card-network protocols?
- No; their credentials travel inside it.
- What does the shared log see?
- Fingerprints (salted hashes), organisation and key ids, and times, plus each company's published key document, which names the company and the agents it exposes to partners. Never message content.
- Is it available?
- A pilot version is built and in testing. It is not in production or available to customers.