Hive is signed-receipt infrastructure for automated systems. In an integrated workflow, selected actions can carry a signed record of captured event, time, and authority statements. A signed model identifier records an assertion; proving execution requires an identified evidence source and separate checks.

What does post-quantum mean for AI agents?

ML-DSA-65 is a post-quantum signature algorithm specified in NIST FIPS 204. ML-KEM-768 is key encapsulation, not a signature. Signatures authenticate statements rather than encrypting their contents. Check endpoint-specific algorithm acceptance. Later verification depends on retained signed bytes, trusted historical keys, compatible software, and continuing cryptographic security.

How do payment records relate to Hive receipts?

Hive describes payment workflows using x402 and USDC on Base. Signing, submission acknowledgment, preconfirmation, block inclusion, and finality are separate events. A USDC payment establishes receipt anchoring only when evidence binds that receipt to the included transaction.

Is Hive open or proprietary?

Hive publishes receipt specifications and verifier resources. Offline verification requires a supported schema and algorithm, the complete signed material, and a trusted issuer key configuration. A key included in a receipt alone does not establish the issuer's identity. See the developer capability table for endpoint-specific support.

What can I build with Hive today?

Explore workflow-specific receipt primitives and the developer capability table. Select an integration by its supported schema, algorithm, deployment status, and required acceptance tests. A catalog entry describes a product, not a passed production run.

Carnac Live Ink™ · Try a request

Try a request and inspect its receipt.

Carnac Live Ink™ is reading as you type

Receipt this Run against the Hive indexi

See how Carnac marks a request*

*Use public test text. Carnac highlights parts of the request as you type.

A receipt sits beside the answer. Check each part separately.

Timing

reported per response, not a guarantee of total request cost

0 changes

to your answer. The receipt sits beside it, never inside it

Offline

checks need a supported receipt, verifier resources, and trusted keys

Model execution, routing, retries, and signing contribute separately to request time and cost. A signature checks the signed statement, not the answer's accuracy or which model actually ran.

CONNECTING TO PULSE UTC

HIVE RADAR™ / LIVE INFERENCE OBSERVATORY

See how inference providers respond.

Review Hive’s provider checks, timestamps, recorded evidence, and gaps.

Enter the live observatory Healthcare AI evidence

CURRENT VERDICT CONNECTING Waiting for the witness log

Next sounding: Calculating
This hour: Reading history
Reported proof checks: Waiting for providers

60 MINUTE SOUNDING COMBFull hour

SIGNED ACTIVITY

Waiting for the durable witness log

Radar sends synthetic requests through selected provider paths and signs the records it captures. These checks cover the tested paths, not the provider’s entire service. Providers do not sign the model output shown here.

Carnac Live Ink™

What the highlights show

Carnac Live Ink™ highlights selected parts of your request in the browser without changing your text. The highlighting itself is unsigned.

Test scenario: request a $40,000 payment to a fictional vendor.

See how Carnac Live Ink™ reads a request →

The Carnac™ family

How the Carnac components fit together

These are the roles in an integrated workflow. The demonstration returns service metadata; it does not verify that all three systems ran.

1 · CarnacPrompt™

Records the original request.

CarnacPrompt™ reads your prompt where it starts and signs a record of exactly what was asked. This is the origin signature.

See CarnacPrompt™ →

2 · Carnac™

Applies your evidence requirements.

Carnac™ applies your signed policy to determine the required evidence and route the request: routine, review, hold, or abstain. This evaluates evidence requirements, not the merits of the request.

See Carnac™ →

3 · Carnac Gateway™

Proof at the Door.

Carnac Gateway™ compares an arriving instruction with an approved version and can countersign the arrival. Change, replay, destination, and chain checks depend on the integrated route and policy. A countersigned statement is separate from proof that an action executed.

See Carnac Gateway™ →

Go deeper on the Carnac™ page →

From decision to primitive

See which receipt type fits your request

This preview matches words in your prompt to a relevant primitive. It illustrates a possible integration; it does not move money, change access, or execute that primitive.

Your prompt

→

Carnac™ decision

→

Payment Healing

See this primitive →

Find a relevant example

Describe your workflow.

Enter your role, company, and the action you need to document. This quick matcher suggests receipt types. Account Studio adds company resolution, workflow confirmation, a proof blueprint, and a synthetic tamper test.

Open Account Studio →

Hive Proof Architecture

Add receipts to selected workflow actions.

Carnac™ and Carnac Gateway™ are two systems in a broader set of proof primitives. When the relevant primitive is integrated with a workflow, selected AI actions, payments, agent runs, and signed documents can leave a separate receipt that an authorized party can check later.

Explore the five service surfacesSee how existing canon components combine across evidence contracts, action boundaries, decisions, reconciliation, and portable trust. Each page states its production and proof limits.

Payment Healing Receipt Relay Receipted Feeds and Triggers Insurance Evidence Studio Verify receipts Model Receipts Signed Agent Runs HiveWallet

Keep a record of the request and its source.

Inspect the signed fields and the evidence used to identify the issuer.

Explore Hive Proof Architecture →