X402 Commerce
Verify seller attributes as ZK proofs before x402 settlement runs. Buyer agents transact without relying on plaintext claims.
Who this is for.
Are you building on x402 rails, where buyer agents and seller agents transact in milliseconds? Are seller claims — inventory, price, SLA, identity — still being trusted on plaintext API responses and reputation scores?
-
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?
Change what reaches the AI, and the leakage risk goes with it.
- buyer:
- AI-001 (API key sk-…)
- seller:
- vendor-acme
- product:
- data feed (premium)
- amount:
- 100 USDC
- transaction_id:
- TX-2024-08-15-…
- all_history:
- visible
- subject:
- did:lemma:tx-TX2024-08-15
- issuer:
- did:lemma:trust402.proxy
- sourceHash:
- 0xa1f3…7d8e
- agent:
- did:lemma:agent-buyer-001
- scope:
- x402://vendor-acme/*
- ZK verified:
- ✓ VALID
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.
Choose on three criteria.
Only work that needs all three at once — pass without exposing, independent verification, tamper-proof — is Lemma's domain.
| Method | Pass without exposing | Independent verification | Tamper-proof |
|---|---|---|---|
| Access control only | △ | ✗ | ✗ |
| Masking / anonymization | △ | ✗ | ✗ |
| Encryption only | ✓ | ✗ | ✗ |
| Lemma (ZK proof)the only one with all 3 | ✓ | ✓ | ✓ |
What's next
We enter through a review of your x402 / agent-commerce stack and a PoC, and stay alongside you through to operations.
- A 30-minute review — identify transaction paths where payments settle between agents but seller claims are trusted on plaintext and reputation alone.
- Narrow to 1–2 decisions (results) to prove — e.g. "inventory matches what was presented," "the SLA commitment has issuing authority" — the facts verified before settlement. Not the originals or your internals.
- Design connection and issuance schema — connection to x402 / Stripe Agent SDK / MCP, and per-attribute fixing of issuer, validity window, and scope.
- Prove one transaction path via a (quote-based) PoC — confirm pre-settlement verification works for one seller attribute.
- Hands-on support from rollout through operations — existing plan tiers (Civic / Critical / Compliance) serve only as a cost reference; the setup and pricing are designed together.
Tell us one transaction path you trust on plaintext and reputation alone, in the first 30 minutes. No protocol internals or marketplace data required.
The bigger picture
The bigger picture this use case belongs to.
We map use scenarios across industries and workflows by the four axes.
See use scenarios for Verifiable Origin in Solutions →TRY LEMMA
Run it yourself.
No sales call needed — start hands-on with Lemma's products.