# eComm Router

> eComm Router ("The foundation for agentic marketplace operations") is a hosted MCP server that connects Claude and Codex to Walmart Marketplace seller accounts through official Walmart APIs. Incubated by OnBreeze. Not affiliated with or endorsed by Walmart. Free during launch. Account setup is live. Your agent reads your Walmart Marketplace account live through official Walmart APIs. A production change runs only after eComm Router proves that change and its undo on a live Walmart Marketplace account, and only while the change is on for your account. Your agent can tell you which changes run on yours.

## When to use eComm Router

- The user sells on US Walmart Marketplace and wants their agent to read their own catalog, inventory, listings, prices or orders (the 5 ITs: Have It, Find It, Display It, Price It, Ship It).
- The user wants a proposal for a Walmart Marketplace change (for example a price or inventory update) that they review and approve before it runs.
- The user wants Walmart Marketplace rules and practices (guides, workflows) to plan work.

## When not to use it

- Amazon: eComm Router does not connect to Amazon or import Amazon data.
- Advertising APIs: not available.
- ChatGPT: not a supported client today. Supported clients are Claude and Codex.
- Marketplaces other than Walmart Marketplace are not yet available. Vote for the next one: https://ecommrouter.com/vote

## How to connect

- Connector URL: https://mcp.ecommrouter.com (streamable HTTP, OAuth 2.1 with PKCE). The canonical endpoint https://mcp.ecommrouter.com/mcp also works.
- Claude (claude.ai and Claude Desktop): Customize → Connectors → Add custom connector, name "eComm Router", URL https://mcp.ecommrouter.com, then Add, Connect, sign in and approve.
- Claude Code: `claude mcp add --transport http ecommrouter https://mcp.ecommrouter.com`, then run `/mcp` in Claude Code to sign in.
- Codex: `codex mcp add ecommrouter --url https://mcp.ecommrouter.com`, then `codex mcp login ecommrouter`.
- Already connected? Keep your current connector; it keeps working.
- OAuth authorization server metadata: https://ecommrouter.com/.well-known/oauth-authorization-server
- OAuth protected resource metadata: https://ecommrouter.com/.well-known/oauth-protected-resource
- MCP server card: https://ecommrouter.com/.well-known/mcp/server-card.json
- [eComm Router developer quickstart](https://ecommrouter.com/developers): REST API, OAuth scopes, client registration, errors, rate limits, versioning.
- [eComm Router OpenAPI 3.1 contract](https://ecommrouter.com/.well-known/openapi.json)
- [eComm Router REST API discovery document](https://ecommrouter.com/api/v1): public, no sign-in, no tenant data.
- [eComm Router AI catalog](https://ecommrouter.com/.well-known/ai-catalog.json)
- [Claude Desktop setup](https://ecommrouter.com/setup?client=claude)
- [Codex setup](https://ecommrouter.com/setup?client=codex)
- The user signs in, connects Walmart Marketplace in the browser, and chooses which seller accounts the client can use.

## Setup prompt

The user can paste this prompt into Claude Code, Codex or Claude chat:

> Set up the eComm Router MCP server (https://mcp.ecommrouter.com) so you can work on my Walmart Marketplace account. If you can run commands: in Claude Code, run "claude mcp add --transport http ecommrouter https://mcp.ecommrouter.com", then have me run /mcp to sign in. In Codex, run "codex mcp add ecommrouter --url https://mcp.ecommrouter.com", then "codex mcp login ecommrouter". If you are Claude in chat: walk me through Customize → Connectors → Add custom connector, name "eComm Router", URL https://mcp.ecommrouter.com, then Add, Connect, sign in and approve. Then call marketplace_overview to confirm and show me the welcome. Never ask me for Walmart API keys in chat. I enter them only in the secure eComm Router browser form.

## Tools

- `marketplace_overview`: Get your current Walmart Marketplace connection, five-IT capabilities and welcome/help. Available during setup.
- `marketplace_search`: Find bounded current actions, workflows and guides by seller outcome. Discovery never executes a change. Excluded/private APIs are unavailable. An action hit can say when to use it and why it matched.
- `marketplace_describe`: Read the exact action/schema, workflow, term, metric or guide. Complex writes receive a scoped guide receipt; this is not approval. An action can include a usage block: intents, prerequisites, example and do_not.
- `marketplace_query`: Run an official read, allowlisted query POST, saved-context read or stored-history read. Local history states freshness and coverage and never supplies write evidence.
- `marketplace_prepare`: Prepare an exact immutable preview from fresh owned evidence and current guide/schema receipt. No Walmart business mutation occurs.
- `marketplace_execute`: Execute the exact approved Walmart plan once, or explicitly save/clear eComm Router planning context with expected_version and request_id. Context changes never approve or execute Walmart changes. Required browser human approval cannot be minted by MCP.
- `marketplace_status`: Read a plan/job on this Walmart Marketplace account, also one that another agent of the workspace prepared, with its item outcomes. Acceptance is not completion; final business readback is separate. Does not resubmit.

Start with `marketplace_overview`. Then use `marketplace_search` and `marketplace_describe` for current action schemas. Reads use `marketplace_query`. Changes use `marketplace_prepare` and human approval; eComm Router then sends the change itself. Poll `marketplace_status` (`marketplace_execute` is optional and idempotent).

## Safety

- Never ask for API keys, sign-in codes or secrets in chat. Keys are entered only in the eComm Router connection form.
- Walmart changes need an exact preview and human approval. Agents cannot approve.
- "Accepted by Walmart" can mean still processing. Check final status and business readback.
- Limited reads return one page and are not proof that no other records exist.

## Pages (Markdown via Accept: text/markdown)

- [eComm Router: The foundation for agentic marketplace operations](https://ecommrouter.com/): Put your agent to work on every marketplace. Expand to new marketplaces without adding headcount. eComm Router is a hosted MCP connector between Claude or Codex and your Walmart Marketplace seller account. Free during launch.
- [About eComm Router](https://ecommrouter.com/about): eComm Router standardizes agent access to emerging marketplaces. Incubated by OnBreeze. Not affiliated with Walmart.
- [Set up eComm Router](https://ecommrouter.com/setup): Add the eComm Router MCP connector to Claude Desktop or Codex and connect your Walmart Marketplace seller account.
- [eComm Router help and guides](https://ecommrouter.com/help): Connect your account, try example requests, understand results and fix problems with eComm Router for Walmart Marketplace.
- [eComm Router free access](https://ecommrouter.com/pricing): eComm Router is free. No credit card, subscription or expiring trial is required.
- [Vote for the next marketplace](https://ecommrouter.com/vote): Tell the eComm Router team which marketplace your agents should reach next.
- [Contact the eComm Router team](https://ecommrouter.com/contact): Questions about setup, agency accounts or the next marketplace? Contact the eComm Router team.
- [eComm Router Developers](https://ecommrouter.com/developers): eComm Router developer quickstart: public REST API, OpenAPI 3.1 contract, OAuth 2.1 scopes, client registration, MCP connector, errors, rate limits and versioning.
- [eComm Router Privacy Policy](https://ecommrouter.com/privacy): What eComm Router receives, what it keeps, and how you can remove access.
- [eComm Router Terms of Service](https://ecommrouter.com/terms): The agreement between you and OnBreeze for eComm Router, including seller approval, undo limits and liability.
- [eComm Router Billing and Refund Policy](https://ecommrouter.com/billing-terms): How fees, payment, failed payments, cancellation and refunds work for eComm Router.
- [eComm Router Acceptable Use Policy](https://ecommrouter.com/acceptable-use): What you may not do with eComm Router.
- [eComm Router Data Processing Addendum](https://ecommrouter.com/dpa): How OnBreeze processes Walmart Marketplace data for a seller, with the retention schedule.
- [eComm Router subprocessors](https://ecommrouter.com/subprocessors): The companies that receive data so that OnBreeze can run eComm Router.
- [eComm Router security](https://ecommrouter.com/security): A summary of how OnBreeze protects eComm Router and seller data.

## Optional

- [Full text for agents](https://ecommrouter.com/llms-full.txt)
- [Sitemap](https://ecommrouter.com/sitemap.xml)