Carnac Live Ink™ · Try a request

Try a request and inspect its receipt.

Carnac Live Ink™ is reading as you type

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.
New · Hive Recorder for AI agents A record of what an AI agent did that the agent can't rewrite. The keys sit outside the agent. Each tool call is witnessed before it runs by a witness that remembers, and public timestamps fix the time. Anyone can ask the witness later, without being handed anything. Running today in real Claude Code sessions. See a real session and ask the witness
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 →

Once you've experienced what Hive has to offer

This is what you get when you join the Hive.

We map every surface where your firm makes a promise, moves data, runs an agent or hands work to a teammate. Each one gets a tile fed by signed receipts, with records for your own sales, compliance, product and support teams. Anyone you share a receipt with can check it in their browser.

The Hive dashboard: every surface on one board See the board we built for a sample firm →

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 →