streamable-httpMITupdated 8d ago
Merchant Context is an open merchant preflight for agent builders.
What can you do with Merchant Context?
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 merchant publishing checklist;
- a draft merchant-context schema;
- a worked SaaS example; and
- a map of the main commerce and discovery standards.
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.
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/mcp - Free MCP tool:
resolve_merchant - Free HTTP:
POST https://api.merchant.atomandbits.com/v1/resolve - Paid MCP tool:
refresh_merchant - Paid HTTP x402:
POST https://api.merchant.atomandbits.com/v1/refresh - Price: $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/mcp
Start 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-run
Contributing
Issues, examples, and corrections are welcome. Read CONTRIBUTING.md before opening a pull request.
License
MIT. See LICENSE.
Install
Add Merchant Context to your client. Pick the one you use.
claude mcp add --transport http merchant-context https://api.merchant.atomandbits.com/mcpcodex mcp add merchant-context --url https://api.merchant.atomandbits.com/mcp{
"mcpServers": {
"merchant-context": {
"url": "https://api.merchant.atomandbits.com/mcp"
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
{
"servers": {
"merchant-context": {
"type": "http",
"url": "https://api.merchant.atomandbits.com/mcp"
}
}
}Add to `.vscode/mcp.json` in your workspace.
{
"mcpServers": {
"merchant-context": {
"url": "https://api.merchant.atomandbits.com/mcp"
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"merchant-context": {
"serverUrl": "https://api.merchant.atomandbits.com/mcp"
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
Score
39 / 100
Incomplete
- Documentation20/25
- Maintenance19/25
- Trust13/20
- Capability0/15
- Install experience12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 1 days ago
- Has a release history
- Repository is not archived
- Licensed MIT
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 0 tool(s) documented
- Provides prompt templates
- Provides resources
- 6 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Version history
| Versions | Published |
|---|---|
| 0.3.0Latest | Aug 11, 2026 |
| 0.2.0 | Aug 4, 2026 |