Merchant Context
Allows agents using the OpenAI Responses API to access Merchant Context capabilities, including merchant resolution, search, offer comparison, safe action handoff, and preflight.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Merchant Contextresolve merchant.atomandbits.com and show what they sell, prices, and unknowns"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Merchant Context
Merchant Context is an open merchant preflight for agent builders.
It starts with a practical question:
Can an agent tell what you sell, who it is for, what it costs, which rules apply, and what action comes next without guessing?
This repo contains:
a worked SaaS example; and
Canonical sources
Product and machine brief: https://merchant.atomandbits.com/llms.txt
Version 0.1 schema: https://merchant.atomandbits.com/schema/merchant-context-v0.1.json
UCP discovery: https://merchant.atomandbits.com/.well-known/ucp
Open source and history: https://github.com/ihint/merchant-context
The domain schema and schema/merchant-context.schema.json
must stay semantically equal. Versioned releases preserve old contracts.
Related MCP server: agenteconomy.cloud MCP server
Status
This is an early public draft from Atom & Bits. It is not a new payment or checkout protocol. It does not certify ACP, UCP, MCP, A2A, x402, or Web Bot Auth support.
The UCP profile declares no services, checkout capabilities, or payment handlers. It gives agents an explicit discovery response without claiming operations that do not exist.
The goal is to give merchants one testable context layer that can map to those systems as they mature.
No outside adoption is claimed from internal tests, registry views, repository activity, or self-funded payments.
Agent endpoints
MCP:
https://api.merchant.atomandbits.com/mcpFree MCP tool:
resolve_merchantFree HTTP:
POST https://api.merchant.atomandbits.com/v1/resolvePaid MCP tool:
refresh_merchantPaid HTTP x402:
POST https://api.merchant.atomandbits.com/v1/refreshPrice: $0.01 USDC on Base
First verified settlement: Base transaction
0x2f0f…57af
The first paid call settled on 2026-08-04 and returned a live inspection of
https://merchant.atomandbits.com.
Quick start
Work through CHECKLIST.md.
Copy examples/saas.json.
Replace every sample value with a fact from your own site or system.
Keep prices, stock, policies, and action URLs current.
Run
python3 scripts/validate.pybefore publishing.
Add it to an agent
The remote MCP endpoint works with clients that support Streamable HTTP:
https://api.merchant.atomandbits.com/mcpStart with resolve_merchant.
It is free.
A cache hit makes no merchant fetch and no paid inspection call.
See the agent integration guide for Codex, Claude Code, Gemini CLI, Cursor, and the OpenAI Responses API.
Agents that support the open Agent Skills format can use
skills/merchant-context.
Design rules
Facts beat slogans.
A URL is not an API.
Agents must not infer price, stock, policy, or authority.
Each claim should name its source and update time.
A purchase or other high-impact action should state when human approval is required.
Existing standards win. Map to them instead of inventing a private dialect.
Agent service
The worker directory contains the hosted MCP service under test. It exposes:
resolve_merchant, a free sourced merchant record with freshness, unknowns, safe actions, and attribution;search_merchants, a neutral search over cached sourced records;compare_offers, a sourced comparison that keeps unknown values;get_safe_actions, a merchant-owned action handoff with approval and recovery rules;preflight, the reusable resolution and action gate;check_merchant, a free merchant-site diagnostic;refresh_merchant, a $0.01 x402 fresh inspection that needs explicit approval;inspect_merchant, a first-release compatibility alias for paid refresh;direct HTTP routes under
/v1; and/.well-known/merchant-context, a public service record for agents and registries.
The inspector accepts public HTTPS origins only. It blocks local and IP targets, checks each redirect, caps response size and time, and returns no page body. The payment path records hashes, not wallet addresses or signed payment tokens.
Run its local checks:
cd worker
npm install
npm test
npm run typecheck
npx wrangler deploy --dry-runContributing
Issues, examples, and corrections are welcome. Read CONTRIBUTING.md before opening a pull request.
License
MIT. See LICENSE.
This server cannot be deployed
Maintenance
Related MCP Connectors
Read-only discovery for exact-commit Agent Skill validation, x402 payment, and signed receipts.
Agent-native MCP for governed commerce, x402 payments, paid capabilities, and verifiable receipts.
Find Nexez sellers, inspect offers, and validate checkout or negotiation before buyer approval.
Agentic commerce network: discover sellers and products, negotiate, and pay USDC on Base via x402.
Related MCP Servers
AlicenseAqualityFmaintenanceEnables agents to search and inspect live service offerings, generate x402 payment snippets, and understand blockchain-only balance policies.440 npm3MIT- FlicenseNot gradedqualityCmaintenanceProvides paid and free tools for AI agents to buy from or sell to other agents over x402, including discovering sellers, verifying on-chain payment histories, running test purchases, and registering sellers for audited listings.-
- AlicenseNot gradedqualityCmaintenanceEnables AI shopping agents to send plain-language requests and receive deterministically ranked, cross-merchant product offers with grounded reasons and inline product images. Enforces a merchant-controlled disclosure layer so individual product facts can be hidden from the agent while still used for matching.1,470,813 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to discover products, verify signed catalog feeds, negotiate within published policies, and place mandate-bound orders with signed receipts via MCP, A2A, or REST.1MIT