Receipt an event, payment intent, API call, or on-chain transaction — then see it in Hive Ledger. The relay endpoints are live now; Circle/USDC direct integration is a next-stage target, not a live Circle call.
Hook any external action, API call, agent step, payment claim or on-chain transaction into Hive and get back a signed, verifiable receipt.
Evidence is graded honestly into tiers so a receipt never over-claims: self_attested (your described
claim, signed as-is), relay_observed (Hive made the outbound call and signed the request/response hashes,
status and timing it directly witnessed), and chain_verified (an on-chain tx read back from a public RPC and
confirmed) — falling back to submitted_unverified when a chain read-back is not available. Every receipt
round-trips the public verifier against did:hive:hivemorph. This relay is how
arbitrary actions join the same signed proof layer as model calls and agent trips.
A relay receipt proves exactly what its evidence tier says — no more. A self_attested receipt signs the claim you described; it does not prove the underlying action happened. A relay_observed receipt is only issued when Hive itself made the HTTP call and signs the request hash, response hash, status and timing it directly witnessed. A chain_verified receipt is only issued when a transaction was read back from a public RPC and confirmed. Circle / USDC is a receipt schema on the event endpoint — Hive signs your stablecoin-transfer claim, it does not contact Circle. Nothing is ever fabricated, and the chain verifier never fails open.
/v1/receipt/verify — offline-checkable, ok.You describe an event — an API call, an agent action, an invoice paid, a stablecoin transfer. Hive signs it exactly as described.
Hive performs an SSRF-guarded outbound HTTP request itself and signs the request hash, response hash, status code and timing it directly witnessed.
A named on-chain tx is looked up on a public RPC (Base, Ethereum, Solana). Confirmed → chain_verified; a genuine miss → chain_not_found; any RPC error → verification_unavailable.
The chain verifier does existence / status read-back only and never fails open — any exception resolves to
verification_unavailable, never to a verified result. It does not decode transfer amounts or match
recipients. The relay_observed HTTP path refuses private, loopback, link-local and cloud-metadata targets
(no open proxy / SSRF), does not follow redirects, and caps body size and timeout.
/v1/receipt-relayliveAdvertises supported modes, evidence tiers, action schemas, the receipt schema, and the signer / verify endpoints. No key required, no secrets returned.
Signs a receipt over any event payload you describe. Hashes intent plus optional request / response / evidence. Circle/USDC, generic API calls and agent actions all land here as self-attested claims.
SSRF-guarded outbound request Hive performs itself, signing the request hash + response hash + status +
timing it directly observed. dry_run:true = a prepare-only signed event, no request made. No free tier
— it makes outbound calls.
Records a base / ethereum / solana tx. Default
submitted_unverified. verify:true does a read-only public-RPC lookup that can upgrade to
chain_verified.
This calls receipts.thehiveryiq.com/v1/receipt-relay/health directly from your browser and
reads back the live schema version and advertised evidence tiers. If a fetch fails, the copyable
curl commands below still work on their own.
Discovery and verification are free. The event and chain endpoints allow a small
free per-IP burst, then return a real HTTP 402 with a redeemable x402 nonce. The http pass-through always
requires an activation key or x402 access token because it makes outbound calls.
curl -sS https://receipts.thehiveryiq.com/v1/receipt-relay/health
curl -sS -X POST https://receipts.thehiveryiq.com/v1/receipt-relay/event \
-H 'Content-Type: application/json' \
-d '{"action":"stablecoin_transfer","external_system":"circle",
"payload":{"asset":"USDC","amount":"10.00","network":"base"},
"actor":{"agent_did":"did:example:agent"}}'
curl -sS -X POST https://receipts.thehiveryiq.com/v1/receipt-relay/http \
-H 'Content-Type: application/json' \
-H 'X-Hive-Activation-Key: tk_live_...' \
-d '{"url":"https://api.example.com/ping","method":"POST","body":"hi","dry_run":true}'
curl -sS -X POST https://receipts.thehiveryiq.com/v1/receipt-relay/chain \
-H 'Content-Type: application/json' \
-d '{"chain":"solana","tx":"<signature>","verify":true}'
curl -sS -X POST https://receipts.thehiveryiq.com/v1/receipt/verify \
-H 'Content-Type: application/json' \
-d '{"receipt_id":"<id>","payload_sha256":"<hash>","sig_b64u":"<sig>","ts":<ts>}'
Circle / USDC (and any stablecoin): a self_attested event on /event with
action:"stablecoin_transfer" and external_system:"circle". Hive signs the claim; it does
not contact Circle. With an on-chain tx hash, the caller can escalate to /chain with
verify:true for a chain_verified receipt. Direct Circle API integration is an
opportunity, not a live capability.
Solana: /chain with chain:"solana" and a transaction signature.
verify:true does a getTransaction lookup; confirmed → chain_verified with
slot and success. EVM (Base / Ethereum): /chain with the tx hash; verify:true does an
eth_getTransactionByHash lookup; confirmed → chain_verified with block number.
"Receipt anything" refers to the relay's pass-through architecture, not a claim that every external action is
independently verified. Evidence is graded into tiers: self_attested signs your described claim without
proving the underlying action; relay_observed is issued only when Hive itself made the outbound HTTP call
and signed what it directly witnessed; chain_verified is issued only when an on-chain tx was read back from
a public RPC and confirmed, and otherwise the event stays submitted_unverified /
chain_not_found / verification_unavailable. Circle and USDC are receipt schemas on the event
endpoint, not live Circle API calls — Hive signs the transfer claim you describe and does not contact Circle. Chain
verification is existence / status read-back only and does not decode transfer amounts or match recipients. The live
controls call receipts.thehiveryiq.com directly and reflect current state. Every relay receipt verifies
against did:hive:hivemorph via the public /v1/receipt/verify endpoint.