X402 Commerce
Verify seller attributes as ZK proofs before x402 settlement runs, so buyer agents can transact safely without relying on plaintext claims.
For agent-commerce teams
Verify seller claims — inventory, price, SLA, identity — before settlement instead of trusting plaintext responses and reputation scores, closing the gap.
-
Operators of agent-commerce platforms and marketplaces built on the x402 protocol
-
Product leads designing buyer and seller agents in MCP-compatible agent ecosystems
-
Digital commerce backbones that need pre-settlement verification on top of Coinbase x402 or the Stripe Agent SDK
Hand over the source, or just the facts?
Nothing changes on the floor. Everything changes for the receiver.
① Your team just saves, as always.
- The usual step
- Fill in the record and save
- On save
- A proof is attached (API, behind the scenes)
- The document itself
- never sent
② They just open a link.
- Proven fact
- the seller's attributes are satisfied before payment
- the seller's internal data
- not shown
- Login / keys
- not needed
- The document stays private — the record itself is never sent or disclosed.
- Independent verification — the receiver just opens a link. No account, no keys.
- Edits are detected — even a one-character edit fails verification.
Lemma wraps the attributes a seller agent presents — identity, authority, inventory, price, SLA, issuer signature — in ZK proofs. The buyer agent verifies them cryptographically before committing, with no need to trust plaintext claims. Transactions without verifiable proofs stop at the boundary before settlement runs.
x402 carries the settlement rail; Lemma carries the pre-settlement trust rail. The two run in parallel: each agent transaction completes in three stages — pre-settlement verification → x402 settlement → post-settlement cryptographic evidence. Even if an ephemeral seller agent lies, the buyer-side verification rejects it structurally — no reliance on reputation systems.
Where the pre-settlement verification layer fits into your x402 / agent-commerce stack is what we map out in a first conversation.
Why the usual methods fall short.
Only work that needs all three at once — pass without exposing, independent verification, tamper-evidence — is Lemma's domain.
| Method | Pass without exposing | Independent verification | Tamper-evident | What happens |
|---|---|---|---|---|
| Access control / permissions | △ | ✗ | ✗ | “Someone inside could have edited it” remains possible |
| Masking / redacted copies | △ | ✗ | ✗ | Redaction work grows; the original is still unproven |
| Encrypt and store / send | ✓ | ✗ | ✗ | To verify, the receiver needs it disclosed after all |
| Lemma (ZK proof)the only one with all 3 | ✓ | ✓ | ✓ | The receiver just opens a link |
How it works — and how to start.
We help design disclosure scope and retention, run the PoC, and support production.
Start with a 30-minute call.
Tell us one transaction path you trust on plaintext and reputation alone, in the first 30 minutes. No protocol internals or marketplace data required.
Related Use Cases
Find the case that matches your industry and problem
Browse all 36 use cases →TRY LEMMA
Run it yourself.
No sales call needed — start hands-on with Lemma's products.