Agents are starting to deal with other firms' agents. Ledger lets each side check who runs the other agent, what it is allowed to do, and whether it has been withdrawn, then keeps one record both sides signed.
An agent moved money this morning. Nobody can say which model it ran, who owns it, or what it was allowed to do. Ledger makes that question answerable in one lookup.
When another firm's agent calls yours, you can't check who owns it, what it is allowed to do, or whether it has changed since it was approved. Today the answer is a contract and an API key.
MCP, agent profiles for OAuth and decentralised identity are all still moving. Ledger sits above the transport, so a firm doesn't have to bet on one before it can start.
When an exchange between two firms' agents goes wrong, each side has its own logs. Neither can show the other, or an examiner, a record both of them signed.
Each agent is bound to the legal entity that runs it and to a named owner inside that firm. Signing keys stay with the institution; Coriqo never holds them.
The owner sets the limits an agent acts under: which actions, with which counterparties, up to what amount, for how long. The other side checks the mandate before it acts on a request.
An owner can suspend an agent or cancel a mandate in one place, and every counterparty's next check sees it. No waiting for each partner to rotate a key.
Both agents sign one receipt for the exchange. Either firm can later prove what was asked, what was done and under which mandate. The receipt carries a fingerprint of the content, not the content itself, so neither side's data leaves its walls.
Each agent gets a cryptographic identity bound to an owner, a purpose and a model version. If nobody owns it, it can't join the network.
Every action is signed where it happens and checked against policy before it leaves. Each record is chained to the last, so an edited entry shows.
A counterparty can confirm an agent's identity and standing before it trusts the request, without seeing the data behind it.
Records are append-only and owned by the institution, not by us. Each one points to the hash of the one before it, so a deleted or edited line breaks the chain where everyone can see it.
bank-a · requesting
partner-b · verifying
Illustrative flow. Names and fields will change before launch.
We're working through the Ledger design with risk, security, architecture and compliance leads at firms whose agents will deal with each other's. Ask for a briefing, or to join as a design partner.