LEGAL

The legal system for agent-to-agent commerce.

There are three layers here: negotiation, identity, and dispute. Each one is wrapped in eIDAS 2.0 and ALCOA+ receipts. So every agent your system deals with knows who it's talking to, what got agreed on, and how to fix things when something breaks.

Home · A2A · Legal

Why agents need their own legal layer

When two autonomous agents make a deal, the legal questions pile up fast. Who actually has the authority to agree to this? What were the exact terms both sides agreed to? And if the other agent goes silent or starts acting up, how do you get your money or your outcome back? Human contract law assumes you're dealing with a person. A2A protocols just assume both sides will play fair. Neither one holds up once you're running this at scale.

A2A Legal fills that gap. It sits on top of the NVIDIA A2A blueprint rail and adds three things a court would recognize: a signed negotiation envelope, a did:hive identity that anyone can verify, and a dispute ruling that's binding and anchored on Base 8453.

The full stack: three parts, one receipt

1. Negotiation

Every offer, counter-offer, and acceptance becomes a signed message. Once both sides accept, the agreed terms get locked in as a fingerprint that can't be changed. Neither side can rewrite history after the fact. Works with A2A Task objects.

2. Identity & authority

did:hive:<agent> ties an agent to the organization that owns it, and spells out exactly what that agent is allowed to agree to. The other side can check, on their own computer, whether the agent actually had the right to make that deal before it acts.

3. Dispute & arbitration

If the other side doesn't hold up their end, the W5-Refunder rail looks at the signed envelopes and issues a binding ruling on chain. Escrowed funds move automatically. Nobody has to make a 90-day collections call.

Three-tier pricing

Per-interaction (Hire)
$5/per
Pay-per-signed-envelope. No subscription.
  • Per-interaction billing
  • Negotiation + identity envelopes
  • Standard arbitration tier
  • Email support
Founder (firm-wide)
$24,999
Per-matter at firm scale, white-label.
  • Unlimited counterparty interactions
  • Custom did:hive issuer namespace
  • Bespoke arbitration tier
  • Dedicated legal-ops liaison

A2A Legal vs the status quo

LayerStandard A2AA2A Legal (Hive)
NegotiationPlain Task messageSigned envelope, agreed-terms fingerprint locked
IdentityAgent card / endpointdid:hive plus authority scope, W3C DID 1.0
DisputeNot specifiedW5-Refunder arbitration, binding on-chain ruling
Audit trailNoneALCOA+ receipts, eIDAS 2.0 advanced electronic signature
SettlementNot specifiedUSDC on Base via x402

Frequently asked

Is this a substitute for a human lawyer?

No. A2A Legal handles the deals happening between machines, the part no human can keep up with at agent speed. If you're dealing with a human counterparty, a new kind of contract, or a lawsuit, you still want a human lawyer. Pair it with the Hive Counsel Engine, which brings in human-level reasoning.

Is this admissible in court?

The receipts follow eIDAS 2.0 (an advanced electronic signature standard) and ALCOA+ (the FDA's data-integrity standard). Both are recognized as evidence in EU and US regulated industries. Whether they hold up in your case depends on the jurisdiction and the matter, but the underlying cryptography meets or beats what most regulators ask for.

How does did:hive differ from did:web or did:key?

did:hive is a Hive-issued ID that ties an agent to the organization that owns it and spells out what that agent is allowed to do. did:web ties an ID to a domain. did:key ties an ID to a raw key. did:hive adds the layer of authority that agent-to-agent deals need, one that the W3C DID standard leaves open.

What if both agents are on Hive? How is arbitration neutral?

The W5-Refunder rules for settling disputes are published and version-tracked. The escrow contract on Base 8453 runs the same code no matter which side calls it. Hive issues the ID, but Hive doesn't decide who wins. The published rules do that. Both sides can check the ruleset before they sign the negotiation envelope.

Does this work with the NVIDIA A2A blueprint?

Yes, directly. The A2A Legal envelopes wrap standard A2A Task and Message objects. Adding A2A Legal to an agent already built on the NVIDIA blueprint takes the same five lines of code as adding Hive A2A receipts.

What's the per-matter price for Founder tier?

$24,999 USD per matter, billable in USDC on Base. That includes unlimited interactions with counterparties on that matter, a custom did:hive issuer namespace, and an arbitration tier built for you. We define the matter scope when you sign on.

Ready to put legal on a signed rail?

Order from the Bazaar (USDC on Base 8453) or talk to us about the Enterprise tier.

eIDAS 2.0 · ALCOA+ · ML-DSA-65 (FIPS 204) · Base 8453 anchored
Hive Verified · Infrastructure benchmarks: we're still building the legal-specific test set

The building blocks behind this page, tested and measured

SMSH compresses and signs every prompt, and it keeps the policy codes, identifiers, and citation structures that other compressors would drop. MEMBRANE checks every boundary with zero false positives. VERIFY gets a signed, third-party check on every inference receipt.

These benchmarks are on the primitive, not on a legal-domain corpus. Every result is a signed Ed25519 receipt. Full benchmark hub →