Hive · Build

Describe an agent. Hive builds it.

Tell Hive what the agent does, what it touches, and which regulators care. We scaffold the receipt schema, the assurance tier, the settlement path, and the SDK. Spec to live agent in minutes.

Open the agent designer → SDK quickstart

How it works

Four steps. Real receipts.

01 · Describe

Workflow + materiality.

Tell Hive the agent’s job, the data it touches (PCI, HIPAA, PHI, none), and the counterparties it acts for.

02 · Scaffold

Schema + tier.

Hive picks the assurance tier (Verified → Verified Regulated), the AFiR primitive (S, RC, Stream), and the receipt envelope.

03 · Wire

SDK + endpoints.

Node, Python, or Go. One REST surface. Code samples for your stack. Receipts go live the moment you call.

04 · Verify

Counterparties verify offline.

Every receipt is portable. Your customer, regulator, or counsel verifies without calling Hive.

Example spec

What the designer captures.

Voice triage agent · healthcare

Workflow: Patient calls in; LLM triages symptoms; routes to nurse line or scheduled appointment.
Sensitive data: PHI · voice + transcript · HIPAA boundary required.
Cadence: Real-time voice, ~300ms segments, 60s typical call.

→ Tier: Verified Regulated.
→ Primitive: AFiR-Stream · per-segment compliance-boundary receipt, off-path signing.
→ Anchor: Base · USDC settlement · ML-DSA-65 PQ-finalize at session close.
→ SDK: hive-py 1.x · stream.session() · deterministic verification offline.

Design your agent → Assurance tiers Pricing SDK quickstart