AI agents
The servers and documents an AI agent uses to shop, to run a shop, and to find its way in.
Storeware is built for people and for the AI agents that shop and work for them. An agent reaches a shop through the same services the shop front and the admin use, with the permissions its key or sign in carries.
MCP servers
Three servers: one for shopping, one for running a shop, and the UCP binding.
How an agent signs in
Keys a merchant issues, OAuth, and agents that register themselves.
UCP and ACP
The two agent commerce protocols every shop speaks.
Answers
What a search understood, why each product qualifies, and what it turned away.
Ask
A question in plain words, answered by the shop. It never changes anything.
Standing
What an agent has done across Storeware shops, and its own signed copy.
Universal Cart
A basket handed to a shop from another platform, over UCP.
Tools in the browser
The WebMCP tools every shop page declares to an agent in the shopper's browser.
llms.txt and skills
The documents an agent reads first, and the signals a shop states.
x402
Paying a shop in USDC, where the shop has turned it on.
Machine payments
Paying per call over HTTP 402. Built, and switched off today.
MCP servers
Three Model Context Protocol servers, all on streamable HTTP at https://api.storeware.ai:
| Path | Server | For |
|---|---|---|
/mcp | storeware | A shopper's agent, holding a key a merchant issued. It can search, compare, check stock, take a checkout through to payment, and read the shop's own skill. |
/admin/mcp | storeware-admin | A merchant running their shop from an agent: products, orders, content, proposals and background runs. |
/ucp/mcp | storeware-ucp | The Universal Commerce Protocol binding every shop's profile names. |
/.well-known/mcp/server-card.json on storeware.ai describes the merchant server, and the same path on a shop's own hostname describes that shop's UCP server. See MCP servers.
Documents an agent can read first
On storeware.ai:
| Address | What it says |
|---|---|
/auth.md | How an agent acting for a merchant registers itself and gets a credential. |
/.well-known/agent-skills/index.json | The platform's agent skills, including building on Storeware. |
/.well-known/api-catalog | Every API the platform publishes, as an RFC 9727 catalog. |
/llms.txt | storeware.ai for a language model. These docs have their own. |
On a shop's own hostname, while its merchant has those doors open: /llms.txt, /auth.md, /.well-known/ucp, /.well-known/acp.json, /.well-known/agent-skills/index.json and /.well-known/api-catalog. See llms.txt and skills.
What a merchant can switch off
Every door an agent comes through is open on a shop that has said nothing, and the merchant can close each one on the AI shoppers screen in the admin: the Markdown copies of pages, llms.txt, the shop's skill, the tools in the shopper's browser, UCP, ACP, A2A, personal agents, and the shop's agent DNS records. Read a shop's own documents to see what it offers, rather than assuming every shop is the same.
A shop that its merchant has not opened yet is described to no agent, and sells to none.
Building an app agents can use
An app can add tools to every assistant on a shop with [[mcp.tools]], and add what it knows about products to search and every agent's view of the catalogue with [knowledge]. See The manifest.