Run a signed receipt, then find it indexed and searchable right here. The ledger is the convenience layer; each row points back to a receipt that verifies on its own.
Hive Ledger™ is the searchable receipt index for AI actions, model calls, agent tasks, x402 payments, API workflows, and human-origin attestations. Each indexed row points back to a Hive Receipt that verifies on its own, canonical bytes, a SHA-256 hash, an Ed25519 signature, a published public key, and a public verifier. The ledger makes those receipts discoverable, searchable, and auditable. It is not required to trust them.
The ledger is convenience. The receipt is proof. Verification is portable: a receipt carries everything needed to check it offline: canonical bytes, hash, signature, and public key, verifiable by any party with no required call back to Hive. The ledger helps you find and audit receipts; it never sits between you and the truth of one.
Trace one event through the pipeline. Proof is established at the offline verifier (green). The ledger index and any anchor / mirror are convenience and durability. They're additive, never on the trust path.
Each module is tagged by what is live today versus next-stage or enterprise. Nothing here is required to verify a receipt. Every module is built on top of portable proof.
Browse, page, and inspect indexed receipts across every event type. The read API is live today; a fully embedded, browsable UI inside third-party apps is next-stage.
Verify any receipt against the published Ed25519 public key. Free, and the proof is portable. The same check runs offline with no call back to Hive.
Every x402 event becomes its own receipted row, real payment_required metadata on quote and
emit. x402 is the only payment rail.
Agent-task receipts across registered adapters (Manus configured today). Index a full route as a chain of signed receipts. See Agent Trip.
A signed, append-only Merkle accumulator: Ed25519-signed roots across canonical provenance domains, live today. External public / blockchain anchoring is next-stage; post-quantum ML-DSA roots are reserved for a future algorithm epoch.
Today you can assemble an audit bundle yourself from the public index plus the offline verifier. Each receipt is self-contained. A one-click signed bundle export endpoint is next-stage.
Per-tenant portal ledger read is live today. A fully customer-hosted, self-hosted mirror you run in your own infrastructure is an enterprise / next-stage capability, not live yet.
A browsable receipt explorer embedded natively inside your own app or a partner surface. The read APIs exist today; the drop-in embedded UI is next-stage.
payment_requiredWe do not claim public blockchain anchoring is live. The live transparency log is a signed Ed25519 Merkle accumulator, and external public anchoring is next-stage. We do not claim a fully customer-hosted mirror is live. Per-tenant portal read is live, and self-hosting is enterprise / next-stage. And the ledger is never required to verify a receipt.
Read-only. This pulls the public ledger summary from receipts.thehiveryiq.com directly,
numbers reflect current state. If the endpoint is briefly unreachable, the widget says so rather than inventing data.
All read/verify endpoints below are live today against https://receipts.thehiveryiq.com.
Verification is free and portable. The public key lets you check a receipt offline, with no call back to Hive.
curl https://receipts.thehiveryiq.com/v1/receipts/pubkey
curl 'https://receipts.thehiveryiq.com/v1/receipts?limit=5'
curl https://receipts.thehiveryiq.com/v1/receipts/summary
curl https://receipts.thehiveryiq.com/v1/receipts/verify/13100
curl -X POST https://receipts.thehiveryiq.com/v1/model-receipts/run \
-H 'Content-Type: application/json' \
-d '{"provider":"mistral","model":"leanstral-1-5","prompt":"State the theorem add_comm for Nat."}'
curl -X POST https://receipts.thehiveryiq.com/v1/x402/quote \
-H 'Content-Type: application/json' \
-d '{"sku":"receipt.emit"}'
curl https://receipts.thehiveryiq.com/v1/agent-receipts/adapters
curl https://receipts.thehiveryiq.com/v1/accumulator/policy
curl https://receipts.thehiveryiq.com/v1/accumulator/receipts/root
R3Pv™, short for Receipt Relay, Recovery, and Routing Proof Vectors, is the higher-order
layer the ledger builds from signed receipts: receipt group → receipt graph → signed proof vector → permitted
next action. The vector encodes verification depth, policy, economic exposure, recoverability / healing, routing, risk, and the single
permitted next action an agent or workflow may take. It is now a live callable primitive: POST /v1/r3pv/groups
teams signed receipts, GET /v1/r3pv/vector?group_id=… generates and Ed25519-signs the vector under
did:hive:hivemorph, and the vector itself round-trips POST /v1/receipt/verify. At enterprise scale these vectors underwrite Protected Flow Fleets → and package as a Proof Credit Profile →. Model your own in the proof-state calculator.
POST /v1/r3pv/groups teams signed receipts (inline objects and/or receipt IDs) with optional graph edges, and returns a group_id.GET /v1/r3pv/vector?group_id=… computes and Ed25519-signs the vector under did:hive:hivemorph. POST /v1/r3pv/vector does group + vector in one call.POST /v1/receipt/verify (verified: true, signature-verified). It is a first-class proof object, not just JSON.GET /v1/r3pv/health declares the schema, signer, 11 healing states, and vector dimensions.The live pipeline is three calls: sign a receipt, group it, then generate the signed vector.
All are live against https://receipts.thehiveryiq.com and were smoke-tested 2026-07-06.
curl -sS -X POST https://receipts.thehiveryiq.com/v1/receipt-relay/event \
-H 'Content-Type: application/json' \
-d '{"action":"stablecoin_transfer","external_system":"usdc","actor":{"did":"did:example:agent"},
"payload":{"asset":"USDC","amount":"25.00","from":"0xSender","to":"0xRecipient","network":"base","note":"no_funds_moved"}}'
# receipt.json = the "receipt" object from step 1
GID=$(curl -sS -X POST https://receipts.thehiveryiq.com/v1/r3pv/groups \
-H 'Content-Type: application/json' \
-d "{\"label\":\"agentic-payment-flow\",\"receipts\":[$(cat receipt.json)]}" \
| python3 -c 'import sys,json; print(json.load(sys.stdin)["group_id"])')
curl -sS "https://receipts.thehiveryiq.com/v1/r3pv/vector?group_id=$GID"
# the signed vector round-trips the public verifier (verified: true)
curl -sS "https://receipts.thehiveryiq.com/v1/r3pv/vector?group_id=$GID" \
| python3 -c 'import sys,json; v=json.load(sys.stdin)["signed_vector"]; json.dump({"receipt_id":v["vector_id"],"payload_sha256":v["payload_sha256"],"sig_b64u":v["sig_b64u"],"ts":v["ts"]}, open("vector.json","w"))'
curl -sS -X POST https://receipts.thehiveryiq.com/v1/receipt/verify \
-H 'Content-Type: application/json' --data @vector.json
{
"signed_vector": {
"vector_id": "r3pv.vector_1783314171_1943fee9f9ba",
"payload_sha256": "0037409e…d8c1bbf",
"sig_b64u": "YJXZqVrv98I6…tkP3aDg",
"key_id": "did:hive:hivemorph",
"algorithm": "Ed25519",
"vector": {
"schema": "r3pv-v1.0.0",
"group_id": "r3pv.group_1783314047_e3ee9cb9351d",
"receipt_count": 1, "resolved_receipts": 1, "unresolved_receipts": 0,
"verification_depth": { "strongest_tier": "self_attested", "source": "computed_from_signed_receipts" },
"weakest_proof_boundary": { "tier": "self_attested", "meaning": "The group is only provable up to its weakest receipt." },
"healing_state": "not_applicable",
"recoverability_window": { "state": "not_applicable", "note": "Rail-/window-dependent. R3Pv does not reverse finalized chain transactions." },
"economic_exposure": { "inferable": false, "note": "no asset/amount present on grouped receipts" },
"policy_state": "not_evaluated",
"routing_recommendation": "require_approval",
"permitted_next_actions": ["hold", "require_approval", "export_evidence"]
}
},
"verification": { "ok": true, "verify_endpoint": "/v1/receipt/verify" }
}
This is a live response, not a mock. economic_exposure is inferable: false here because a
standard relay receipt stores only an intent_hash, not cleartext amounts. Supply asset/amount on the grouped
object and the vector computes exposure by asset. Unresolved receipt IDs weaken the vector and force
require_approval; a settled / chain_verified receipt yields evidence_only_final with
no recover action offered.
Real measured round-trip latency for receipt generation, group creation, signed-vector generation, and verification, all live, plus runnable curl, is published on the R3Pv benchmark page. Numbers are network-dependent round-trips, not server signing time.
R3Pv tells you the honest state of a receipt group. Hive Protected Flow is the premium decision layer that takes that vector, applies a declared policy pack and declared exposure at risk, and returns an Ed25519-signed assessment: one of eight decision classes (permit, permit_with_evidence, require_approval, hold, recover, reroute, escalate, block), the risk factors that drove it, the permitted next actions, and a three-part meter quote: platform fee, plus R3Pv/Healing premium band, plus optional basis points on protected exposure. The meter is a quote, not a settlement. No funds move. Overrides can only make policy stricter, never looser.
The decision is the strictest of the R3Pv routing recommendation, the exposure band, and any policy hard-fail. POST /v1/protected-flow/assess returns signed_assessment with decision, rationale, risk_factors, and permitted_next_actions, all signed by did:hive:hivemorph. The assessment round-trips /v1/receipt/verify like any Hive receipt.
Broad coverage prices as lightweight infrastructure. Protected/high-risk flow prices as protected value: platform_fee_usd + protection_premium_usd (banded by decision class) + optional exposure_premium_usd (basis points on declared exposure). Named policy packs ship today: default, strict_bank, high_risk_agent.
GET /v1/protected-flow/evidence/{group_id}/export bundles the signed R3Pv vector, the latest signed assessment, the referenced signed receipts, and the signer's pubkey material into a single signed bundle. Everything an auditor needs to re-verify the whole flow offline, no Hive call required.
{
"signed_assessment": {
"assessment_id": "protected_flow.assessment_1783344027_2941ed841f06",
"payload_sha256": "2d137891401ae1a8d1820478…",
"sig_b64u": "lTCi2JjQO4c-y9SiHeGBWnk7…",
"key_id": "did:hive:hivemorph",
"algorithm": "Ed25519",
"assessment": {
"schema": "protected-flow-v1.0.0",
"decision": "hold",
"rationale": "r3pv_routing=require_approval→require_approval; exposure_band=permit; policy_hard_fail=hold; strictest wins.",
"permitted_next_actions": ["hold","export_evidence","preserve_evidence"],
"risk_factors": [
{"factor": "weakest_boundary_below_policy", "severity": "high"}
],
"policy_pack": {"name": "default", "require_min_tier": "relay_observed"},
"declared_exposure_usd": 500.0,
"meter_quote": {
"platform_fee_usd": 0.10,
"protection_premium_usd": 1.00,
"exposure_premium_usd": 0.0001,
"total_usd": 1.10,
"note": "Quote only. No funds move."
}
}
},
"verification": { "ok": true, "verify_endpoint": "/v1/receipt/verify" }
}
Assess a Circle-shaped USDC intent under the default policy pack, then again under strict_bank. Same receipt, stricter policy → stricter decision. No funds move. This service never calls Circle APIs.
# Protected Flow: end-to-end smoke against live production curl -sS https://receipts.thehiveryiq.com/v1/protected-flow/health | head -c 400; echo # Sign a stablecoin-intent receipt (no funds moved) curl -sS -X POST https://receipts.thehiveryiq.com/v1/receipt-relay/event \ -H "Content-Type: application/json" \ -d '{"action":"stablecoin_transfer","external_system":"circle","actor":{"did":"did:example:agent"},"payload":{"asset":"USDC","amount":"1000.00","from":"0xSender","to":"0xRecipient","network":"base","net_moved":"0.00"},"healing_state":"pre_broadcast_stoppable"}' \ | python3 -c 'import sys,json; json.dump(json.load(sys.stdin)["receipt"], open("receipt.json","w"))' # Assess (default policy, $500 exposure): expect hold on self_attested weakest boundary curl -sS -X POST https://receipts.thehiveryiq.com/v1/protected-flow/assess \ -H "Content-Type: application/json" \ -d "{\"label\":\"circle-usdc\",\"receipts\":[$(cat receipt.json)],\"policy_pack\":\"default\",\"declared_exposure_usd\":500.0}" # Assess (strict_bank policy, $50k exposure): expect hold with chain_verified requirement curl -sS -X POST https://receipts.thehiveryiq.com/v1/protected-flow/assess \ -H "Content-Type: application/json" \ -d "{\"receipts\":[$(cat receipt.json)],\"policy_pack\":\"strict_bank\",\"declared_exposure_usd\":50000.0}"
Broad coverage prices as lightweight infrastructure. Protected/high-risk flow prices as protected value: platform fee + R3Pv/Healing premium band + optional basis points on declared exposure. Named policy packs ship today: default, strict_bank, and high_risk_agent. Custom packs are a strategic-window conversation. Protected Flow is category-defining and, like R3Pv, it never reverses finalized chain transactions and never calls Circle APIs.
The fastest way to understand the ledger is to put one receipt in it. Run a paid receipt over x402, test a model receipt, or request an activation key, then watch it appear in the index and verify it portably.
Hive does not claim every payment can be reversed. It proves what happened early enough to act where the rail allows, and proves what happened afterward when it does not. The Circle/USDC-compatible receipt schema is live today; direct Circle integration is next-stage.
R3Pv™ (Receipt Relay, Recovery, and Routing Proof Vectors) is the higher-order layer: Receipt Relay signs → R3Pv groups receipts into teams & graphs → R3Pv proof vectors route, recover, and heal. The vector primitive is live: POST /v1/r3pv/groups then GET /v1/r3pv/vector returns an Ed25519-signed vector that verifies at /v1/receipt/verify. Smoke path: /v1/r3pv/health returns HTTP 200 today. Measure receipt latency separately from settlement / rail latency.
Hive Ledger™ is the convenience and indexing layer. It aids discovery, search, and audit and is not required to
verify a Hive Receipt. Receipts verify portably and offline against a published Ed25519 public key with no call back to
Hive. Live-today claims reflect endpoints on receipts.thehiveryiq.com as of 2026-07-05: the receipt index and
summary, the public key and public verifier, model receipts, x402 quote and receipt emit with real
payment_required metadata, agent-task receipts, a signed Ed25519 Merkle transparency-log (accumulator) API,
and per-tenant portal ledger read. External public / blockchain anchoring, a fully customer-hosted self-hosted mirror, a
drop-in embedded explorer inside third-party apps, a one-click signed audit-bundle export endpoint, and post-quantum
ML-DSA signature roots are next-stage or enterprise, not live today. The signature field is historically named
mock_sig for compatibility; production signatures are real Ed25519 with a 0xsig: prefix. A
receipt attests the operation: what happened, by whom, over what bytes. It never gives a route on whether the result was correct.