If the inputs are self-reported outcomes, the reputation is an affidavit the agent wrote about itself. Hive signs the decision instead. It records which model acted, which policy floor it cleared, and whether it was released or held. A counterparty or an examiner can check that offline, without ever touching your systems and without ever seeing your data.
Five agents. Reputation assembled from what each one reported about its own work. Everyone looks excellent, because they always do. Now switch on independent receipts and watch which scores survive.
This is the question that eventually arrives in writing, from a counterparty, a licensing authority, or opposing counsel. Today it starts a forensic reconstruction across logs nobody outside the company can validate. With receipts, it is a lookup, and the answer verifies without you in the room.
Nothing here touches custody, keys, matching, or settlement. The receipt sits above the action, proving the decision that caused it.
Hive forms no opinion about your markets, your users, or your risk appetite. It sizes how much proof a decision needs, records provenance, and signs it. You set the floor. Policy can only get stricter, never looser.
OKX ships an AI agent marketplace, an Exchange OS that institutions build on, and OKX Pay under a European licence. Each one lets a model reach toward value. The Carnac™ family turns each reach into a signed record before anything moves.
When an ops or compliance owner writes an agent policy, each part is marked in the moment it is written, and each part carries the route it earns. The record is built while the work happens, not rebuilt afterward.
Under the Carnac™ family sits a set of signing primitives, each with one job. All are available today. Connecting them to OKX would be a scoped build inside your existing surfaces. A developer can prove one connection in under an hour. One protected workflow takes one to three engineering days. A production pilot takes one to two weeks, because security review and change control still matter.
The first step is small. Point one agent decision at the protected route and see what comes back. No integration, no custody change, no access to your data. The proof verifies offline today, on a post-quantum standard, by anyone you hand it to.
This receipt adds a narrow test of the authority presented for one exchange side agent action, whether it reaches toward a trade or a withdrawal. It is live on the production rail and the run below verifies a real signed receipt.
When an agent places a trade or requests a withdrawal, this receipt compares that one action with the delegated authority supplied for it. It tests the declared amount, currency, timing, and scope against constraints in an authority receipt signed before the action was authorized. The outcome is recomputed by the service, rather than accepted from the exchange side agent. That gives compliance, risk, and market operations a reviewable statement about the action that was presented. It adds evidence above custody, matching, and settlement without changing any of those systems.
What it does not do. It does not prove that a cardholder granted the delegation, that the stated agent identity is genuine, that a network authorized or settled the action, that value was delivered, or that a person read the terms shown. It is not payment authorization and provides no cardholder credential; no card network, issuer, or regulator currently recognises it as authentication data, compelling evidence, or a liability shift; it cannot deny or resolve disputes, limit rights under Regulation E, Regulation Z, or an equivalent rule, test aggregate limits or velocity, or show that the supplied authority was unrevoked at authorization time.
Nothing has run yet. Click Run it and the answer below comes back from the verifier, not from this page.
Nothing has run yet. Click Run it and the answer below comes back from the verifier, not from this page.
Every run above posts a verified request body from this domain to the open verify route and prints what came back. The example receipts are signed with published example keys, so verify reports key_trust example_registry. That is on purpose. Nothing on this page is a production issuance, a customer record, or an endorsement. Patent Pending.
Each link opens that entry in the canon implementation explorer, where its schema, mint route, open verify route, auth requirement and implementation state are stated. The state shown here is read from the same registry file the explorer renders from, so the two cannot drift apart. Nothing here implies a customer, a deployment or an endorsement.
Search the explorer for OKX use case