Developers

Integrate in an afternoon. Verify in a minute.

Hive is an SDK that wraps around the model calls you already make. The library handles the envelope, the signing, the origin fields, sealed inspection, and settlement. Your code doesn't have to change shape.

Canon or Developers? The Canon shows what proofs exist and what each one is worth to a buyer. Developers is where you wire them in: the SDK, the code, the envelope, and the reference verifier. Read the Canon to decide what to prove. Come here to ship it.
Node · Python · Go · Rust (roadmap) · Reference verifier
Open the quickstart Reference verifier Gateway benchmark
Quickstart · HTTP

Mint and verify a receipt over HTTP.

The API is live now. No SDK or account is required to mint a free receipt or verify one. Language SDKs are in private preview.

// Live now: mint a free, portable receipt. No SDK required. $ curl -X POST https://receipts.thehiveryiq.com/v1/receipt/free \ -H "Content-Type: application/json" \ -d '{ "input": "your prompt or payload", "purpose": "demo" }' // The response includes a portable, offline-verifiable receipt. // Verify any receipt over HTTP: $ curl -X POST https://receipts.thehiveryiq.com/v1/receipt/verify \ -H "Content-Type: application/json" \ -d @out.hive.receipt.json // Language SDKs (Node, Python, Go) are in private preview. Request access below.
SDKs

Same envelope. Four runtimes.

PRIVATE PREVIEW

Node · TypeScript

Our main SDK. It has an async API, the full envelope, ViewKey helpers, settlement helpers, and an offline verifier built in. In private preview, request access below.

package@hive/sdk · private preview
runtimeNode 18+ · Deno · Bun
PRIVATE PREVIEW

Python

Sync and async clients, same envelope shape. Drops right into FastAPI, Flask, or Django services that make model calls. In private preview, request access below.

packagehive-sdk · private preview
runtimePython 3.10+
PRIVATE PREVIEW

Go

A Go SDK that feels like Go. Context-aware, no dependencies in the verifier, and a good fit for service meshes and operator-side proxies. In private preview, request access below.

moduleprivate preview
runtimeGo 1.21+
ROADMAP

Rust

A native verifier and signer that works without the standard library. This one's still on the roadmap. Reach out if you need it sooner.

cratehive-sdk · ROADMAP
statusroadmap
Request SDK access → Use the HTTP API now →
Wire format

One envelope. Stable shape.

The receipt envelope is versioned, and we only add to it. Existing fields keep their shape across minor versions. New fields show up under their own namespaced keys.

// hive-receipt-v1 · canonical fields { "v": "hive-receipt-v1", "receipt_id": "rcp_…", "request": { "hash", "origin", "purpose", "policy_hash" }, "operator": { "entity", "region", "training_region" }, "hardware": { "class", "attestation" }, "response": { "hash", "sealed" }, "settlement": { "chain", "asset", "tx" }, "signatures": { "requester", "operator", "hive" }, "issued_at": "ISO-8601" }
Receipt profiles · r1.0.0 · LIVE

One envelope. Three profiles. One price ladder.

Every receipt declares a receipt_profile and a receipt_schema_version. Profiles trade off size, retention, and crypto-agile metadata against price. You can pick a profile per call, or let RubricMesh recommend one.

Nano
$0.0001 / call
≤ 600 bytes · 30-day retention · compact field names · high-volume agent attestation
Standard · default
$0.0008 / call
≤ 3 KB · 365-day retention · settlement-reference · SMSH seal · HKTN context
PQ · regulated
$0.0012 / call
~7-year retention · crypto-agile metadata · sealed-evidence ref · auditor-verifier mode
// Nano receipt · receipt_profile: nano · ≤ 600 bytes · compact keys { "ok": true, "a": "did:hive:agent", "h": "8f43…", "t": "application/octet-stream", "profile": "nano", "v": "r1.0.0", "receipt": { "id": "r_…", "sig_b64u": "…", "verify_uri": "/v1/receipt/verify" } }
// Standard receipt · receipt_profile: standard · settlement-ready { "receipt_profile": "standard", "receipt_schema_version": "r1.0.0", "agent_did": "did:hive:agent", "settlement_reference": { "rail": "x402-usdc-base", "chain_id": 8453, "asset": "USDC" }, "smsh": { "sealed": true, "declaration": "agent.commerce.standard" }, "hktn_context": { "reputation_tier": "Tier1" } }
// PQ receipt · receipt_profile: pq · crypto-agile, auditor-verifier mode { "receipt_profile": "pq", "receipt_schema_version": "r1.0.0", "crypto_agile_metadata": { "current_alg": "Ed25519", "signature_posture": "ML-DSA-65-class", "envelope_posture": "ML-KEM-768-class" }, "sealed_evidence_ref": null, "pq_posture": "designed-to-support", "auditor_verifier": true }
// Selector · emit a profile per call POST https://receipts.thehiveryiq.com/v1/receipt/emit?profile=nano POST https://receipts.thehiveryiq.com/v1/receipt/emit?profile=standard // default POST https://receipts.thehiveryiq.com/v1/receipt/emit?profile=pq GET https://receipts.thehiveryiq.com/pricing // machine-readable ladder POST https://receipts.thehiveryiq.com/v1/rubric/select // returns recommended_profile
  • receipt_profile is selected per call. Default is standard when no profile is requested.
  • RubricMesh recommends a profile based on intent × amount × counterparty. Free verify or sub-cent calls get Nano, commerce gets Standard, and regulated or long-retention cases get PQ.
  • The cryptographic verification path is identical across profiles. Verify any receipt at /verify or call /v1/receipt/verify directly.
  • PQ does not claim production ML-KEM / ML-DSA. The crypto-agile metadata declares posture; formal NIST PQC integration is on the ROADMAP.
  • Legacy proof_tier: standard|hive_pq receipts continue to verify. New emits use receipt_profile + receipt_schema_version.
Reference verifier

Run the proofs in your browser.

The /verify page runs five checks for you: a valid receipt that passes, a tampered receipt that gets flagged as a mismatch, a forged signature marked invalid, a sealed AES-GCM check that verifies, and a wrong-key check that fails like it should. Each one runs locally in WebCrypto.

  • No Hive endpoint is contacted.
  • The verifier source is the same code shipped in every SDK.
  • Sample receipts are stable and re-runnable.
Next

Open the quickstart.

Hive sits in front of the model calls you already make. You don't need to switch vendors. You can ship a working receipt in an afternoon.

Get SDK access Run the verifier
Next action
Move from understanding to proof to activation, all on the same URL.
Design my private Hive briefing Activate USDC pilot Verify a receipt Open diligence room

Public endpoint status

Here are the four primitives plus the discovery and prospecting layers, with live status, the current path, and where each one stands.

Receipt verifier

Live
Operational
/verify · /v1/receipts/verify
Checks any signed Hive receipt, offline or online. Public, no login needed.

Receipt emit

Live
Operational
POST /tenants/:id/receipts
The SDK issues a receipt for every AI transaction. Needs a tenant API key.

Sealed inspection

Live
Operational
GET /tenants/:id/evidence
A signed bundle.zip manifest of the customer evidence room. Kept for 365 days.

Settlement reference

Live
Operational
USDC on Base · 0x833589fC…02913
USDC settlement on Base mainnet. Hive never holds the asset.

Rosetta

Pilot
Pilot, partner-gated
/v1/rosetta/normalize
Translates policy across jurisdictions: MAS, EU AI Act, PIPA, and BSP. Open to pilot tenants.

Prospector

Pilot
Pilot, partner-gated
/v1/prospector/qualify
Checks whether an AI transaction surface is ready for receipts before you integrate. Open to pilot tenants.

Full live status on /status · all 17 endpoints, signed, 60-second refresh. Reference-core performance: Gateway benchmark, measured and reproducible with a signed manifest.

Activate the workspace
If your team can wrap one model call, Hive can issue your first verifiable transaction receipt.
Activate a pilot workspace and you'll get SDK access, sample receipts, endpoint status, and evidence-room exports.
Activate pilot workspace Design private briefing Generate sample receipt View endpoint status