merx
Evidence travels with the product.
Structured attributes record their source. Claims carry evidence, and not_for makes product limitations explicit.
OPEN-SOURCE / AGENT COMMERCE
The next customer
is an agent.
Give it a store it can reason about. Merx turns product facts, buying constraints and merchant policies into explainable matches and signed orders.
// one need, verifiable decisions
“Coffee for espresso. Low acidity.”
- 01Discover the storemanifest + public key
- 02Match with reasonsfacts + constraints + limitations
- 03Negotiate within policybounded rounds + signed deal token
- 04Authorize the ordersigned spending mandate
✓ Signed receipt returned
Illustrated flow. Example payments are not settled.
One engine. Three adapters.MCPA2AREST / OpenAPI
SEE THE REASONING
A match is more than a keyword.
Explore actual engine output for a fictional coffee store. Each scenario is calculated from the example catalog when this site is built.
Build-time snapshot · no live checkout
Loading engine results…
The request
Amounts use integer minor units: 8000 means EUR 80.00.
Matches
Why other products were rejected
DESIGNED FOR SOFTWARE BUYERS
Facts in. Decisions out.
Rules a merchant can audit.
Published discounts, private price floors and bounded rounds produce deterministic offers with signed deal tokens.
Authorization has a boundary.
Mandates include spending limits, merchant scope, expiry and a single-use nonce. Orders return a verifiable signed receipt.
TRY THE COMPLETE FLOW
Three commands.
No API keys.
Install Node.js 22.6+ and Git, then run the scripted buyer locally. It starts a store, places a sample order, checks its receipt and demonstrates replay rejection.
No LLM account or dependency installation is needed for this demo.
Run your own store →Terminal
git clone https://github.com/kamilkubik89/merx.git
cd merx
npm run demoPrefer a browser workspace? Open in Codespaces. GitHub account quotas and billing apply.
BEFORE YOU BUILD
What Merx is ready for.
Is this production-ready?
No. Merx is a reference implementation and a draft specification. State is in memory, the sample provider returns bank-transfer instructions, and production wallet identity requires a trusted-key policy. Use it for experiments and integration prototypes.
Does the demo use an LLM or make real payments?
No. The buyer is scripted, matching is lexical and negotiation follows deterministic rules. The demo verifies signatures and creates an example order; it does not transfer money.
Which protocols are implemented?
MCP, A2A and REST/OpenAPI adapters are included. UCP, ACP, AP2 and x402 integrations are roadmap items. The current mandate format is Merx-specific and inspired by AP2; it is not an AP2 implementation.
Does it replace Shopify or WooCommerce?
Merx explores a store engine designed for agents. It currently has no merchant dashboard, persistent order database or production payment integration. It is not a drop-in replacement for a production commerce platform.
How can I help?
Try a catalog, report a reproducible issue or propose a protocol mapping. The first-contribution guide offers small tasks. Larger payment and persistence work starts with a design discussion.
BUILDING IN THE OPEN
Agentic commerce needs a community.
Build the ecosystem with us.
Catalog engineers, merchants, payment integrators and agent developers: bring a problem and help turn it into a testable interface.
Beyond the XML product feed.
Explore signed decision packets with reusable product facts, current offers and the next valid action for a buyer agent.
Payments without one fixed provider.
Register providers, discover their capabilities and select a payment method before a quote is signed.
BUILD THE MERCHANT SIDE
Build the open agentic commerce ecosystem with us.
Try Merx, tell us what is missing, and help shape the next adapter.