Prove Before Act
中文

Consequences require evidence.

Your agent can act. Can it prove why it acted?

When an autonomous agent moves money, changes production, signs a contract, or delegates to another agent, the audit trail cannot begin after the incident. Commit the decision basis before execution and leave evidence a reviewer can verify.

Prove your first agent decision — 10 free proofs, no wallet, no credit card.

Open the browser experience to register an agent or project, receive a free API key, and create the first independently verifiable proof.

Prove Before Act is the public accountability pattern. xProof is the reference implementation. Current live rate after the free proofs: $0.01 per certification — see /api/pricing.

See the 60-second overview Inspect the standard

Why integrate before anyone requires it?

Evidence cannot be created after the fact. The right time to build an accountability record is before a client, auditor, insurer, or regulator asks for one.

  1. The downside is asymmetric

    A first integration is small and predictable: 10 free proofs, then the current live rate is $0.01 per proof. Waiting costs nothing until someone asks for evidence that was never created. At that point, it cannot be reconstructed.

  2. The proof must precede the incident

    A record written after a dispute shows what you say happened. A commitment anchored before execution proves what the agent declared before it acted. The timestamp is the value.

  3. A verifiable history compounds

    Operators that start now build a durable record across decisions and outcomes. When accountability becomes a requirement, they can show history—not a compliance process that began yesterday.

Prove your first agent decision · Inspect the Prove Before Act standard

How pre-execution evidence works

Build a verifiable trail around the declared decision basis, intended action, and outcome that matter.

  1. Declare a decision basis and intended action

    Your agent records the decision, declared justification, context, and intended action locally. This is not a request for internal chain-of-thought.

  2. Hash locally

    A SHA-256 hash is computed locally from that declared record, a model output, data snapshot, or build artifact. Only the hash is transmitted — source material stays private.

  3. Anchor before acting

    xProof anchors the hash on MultiversX. The agent receives a proof_id and blockchain transaction URL — independently verifiable by any third party before the action begins.

Simple pricing - One price. No subscription.

Current live rate: $0.01 per certification (see /api/pricing). Pay only for what you use. No hidden fees, no commitment.

Frequently asked questions

Is my file uploaded to your servers?
No. Only the SHA-256 hash is transmitted. Source data never leaves the agent's runtime environment.
What is the MultiversX blockchain?
MultiversX is a high-performance, eco-friendly European blockchain. Unlike Bitcoin, it consumes very little energy.
Does it have legal value?
Yes. Blockchain timestamping is recognized in many jurisdictions as proof of prior existence.

Make critical actions accountable

Operators can require independently verifiable pre-execution evidence before deployment, handoff, payment, or another external action. Current live rate: $0.01 per certification; see /api/pricing.