Composable primitives
Agentic checkout, cart and feed, delegated payment, delegated authentication, and order webhooks are defined separately, so we implement the ones a merchant needs.[4]
The interface we publish for machines.
Most shops hope an AI will scrape them. We publish a contract: a catalogue an agent can query, a checkout an agent can complete, and a crawl policy that says yes instead of maybe.
Interface
Five machine-readable surfaces
| Surface | Path | Format | Purpose |
|---|---|---|---|
| MCP server | /mcp | Model Context Protocol | Tools for search, product detail, stock, delivery promise and configuration. Read-only unless an authenticated session grants more. |
| ACP checkout | /.well-known/acp.json | JSON + REST | Declares the checkout endpoint, capabilities, payment handlers, fulfillment options and per-agent spend policy. |
| LLM index | /llms.txt, /llms-full.txt | Markdown | A curated map and a full-text mirror of this site, so a model reads prose instead of parsing a layout.[1] |
| Structured data | every page | JSON-LD (schema.org) | Organization, WebSite, SoftwareApplication, Offer, FAQPage and BreadcrumbList, with real prices and real availability. |
| Data endpoint | /data/market-data.json | JSON | The same sourced market figures a human reads, with per-record source and verification status. |
Agentic Commerce Protocol
Why ACP and not a bespoke integration
ACP was released on 29 September 2025 by OpenAI and Stripe, with Meta since joining as a co-maintainer, under Apache-2.0.[2][3] Betting on a closed format would make every future agent integration a negotiation. Betting on an open one makes it a configuration.
Merchant of record stays you
The merchant keeps the customer relationship across fulfillment, returns and support. The agent is a channel, not the store.
Credentials never travel
Payment credentials are passed as scoped tokens rather than being exposed to the agent. Approval happens in the customer's own banking app.
REST or MCP, your choice
The spec supports publishing checkout configuration over a conventional API or an MCP server, so adoption doesn't dictate your stack.[3]
Crawl policy
We let AI crawlers in, and we say so in the file
A robots.txt that silently blocks the assistants your customers use is a business decision disguised as a technical default. Our policy is explicit, machine-readable and generous — with one line drawn around bulk resale.
# --- AI answer engines: allowed, with attribution ---
User-agent: GPTBot
User-agent: OAI-SearchBot
User-agent: ChatGPT-User
User-agent: ClaudeBot
User-agent: Claude-User
User-agent: PerplexityBot
User-agent: Google-Extended
User-agent: Applebot-Extended
User-agent: CCBot
Allow: /
# --- Bulk dataset harvesting: not allowed ---
User-agent: Bytespider
Disallow: /
Sitemap: https://swiftshop.pl/sitemap.xml
# LLM index: https://swiftshop.pl/llms.txt
Content-Signal: search=yes, ai-input=yes, ai-train=noThe distinction matters. ai-input=yes means you may retrieve our pages to answer a user's question right now. ai-train=no means the content is not donated as training volume. Those are different asks and they deserve different answers.
- Every page has a Markdown twin at the same path with a
.mdextension. - Every page declares that twin with
<link rel="alternate" type="text/markdown">. - Prices, stock and delivery promises are served as data, so an agent is never guessing from rendered pixels.
- All copy is present in the initial HTML response — no JavaScript execution required to read it.
Guardrails
What an agent is not allowed to do
| Control | Default | Why |
|---|---|---|
| Spend ceiling without human approval | 2 000 PLN | Above this, the session pauses and asks the customer to approve in their banking app. |
| Payment method access | Tokenised only | Raw card or BLIK credentials are never surfaced to the agent. |
| Catalogue write access | None | Agents read and transact. They do not change prices, stock or copy. |
| Order cancellation | Customer or merchant | Irreversible actions stay with the accountable party. |
| Data shared per order | Minimum viable | Only what is needed to fulfil, nothing for profiling. |
| Refund window | 14 days | Statutory consumer withdrawal right, applied uniformly. |
Build with us
Integrating an agent against SwiftShop
Spec access for integrators
The MCP tool manifest and the ACP policy schema are available to design partners under the same open terms we ship under.
Sources cited on this page
Every figure above is drawn from the sources listed here. The machine-readable register lives at /data/market-data.json.
- llmstxt.org. The /llms.txt proposal — a Markdown convention for LLM-friendly sites —
- OpenAI. Buy it in ChatGPT: Instant Checkout and the Agentic Commerce Protocol —
- Agentic Commerce Protocol. An open standard for programmatic commerce flows (Apache-2.0) —
- Stripe. Agentic Commerce Protocol — integration documentation —
SwiftShop.pl is pre-launch. Figures come from the sources below; projections are labelled as such.