Quickstart & Guides

Three steps to your
first signed receipt.

You do not need to rewrite your agents or prompts. Wrap an existing MCP server or add our lightweight middleware to your agent framework.

STEP 01

Wrap any MCP server (Claude Code, Cursor, Claude Desktop)

Packages publish at launch

Prefix your MCP server command with hvr mcp wrap (bound to publishing-targets.json). Every tool call can be evaluated against your policy and saved as a signed .hvr receipt.

# Wrap any stdio or HTTP MCP server (public registry packages activate after Step B6)

$hvr mcp wrap -- npx -y @modelcontextprotocol/server-github

STEP 02

Verify the receipt in your browser or terminal

Apache-2.0 CLI

Drop the generated .hvr file onto the Verify page or run the open-source hvr CLI verifier with zero network calls.

# Offline verification with the hvr CLI

$hvr verify action.hvr --checkpoint checkpoint.note --trust roots.json

STEP 03

Add to your agent framework or API gateway

Packages publish at launch

Adapters are available for TypeScript, Python, Go, and Rust, plus drop-in middleware for popular agent frameworks. Publishing targets are bound in publishing-targets.json and activate after repositories and packages are public.

# Packages publish at launch (Step B6: repos -> packages -> site links)

$node scripts/receipts-oss-export.mjs && hvr verify --help

Adapters

Supported frameworks & gateways.

TypeScript & JavaScript

Vercel AI SDK & LangChain.js

Wrap tool definitions with withHivemindReceipts() to attach a verified receipt ID to every tool execution.

Python Frameworks

LangGraph, CrewAI, AutoGen, LlamaIndex & OpenAI Agents

Use the @receipt_tool decorator or callback handler built from source.

Infrastructure & Gateways

Envoy, Kong, Cloudflare Worker & OpenTelemetry

Issue receipts at the network edge or convert OpenTelemetry gen_ai.* spans into signed receipts automatically.

Compliance & Regulatory Mapping (C5)

Compliance evidence mapping.

Evidence mapping only, not a legal opinion or certification

EU AI Act · Art. 12 & Art. 14

Record-keeping & human oversight

Maps signed tool call receipts and passkey approval records to automatic event logging and human-in-the-loop oversight controls.

DORA · Art. 10 & Art. 17

ICT incident & change audit trail

Maps sequence-complete agent logs and emergency halt receipts to operational resilience evidence.

SOC 2 CC6 / CC7 & ISO/IEC 42001

Access & AI system change records

Maps policy evaluation digests and checkpoint inclusion proofs to logical access and change-management controls.

Three steps to yourfirst signed receipt.