# Agent Shop

> This is a Shopware-powered online shop. This file provides AI assistants with a concise entry point to public sales channel information.
> Only public shop information is described here; account, order, payment, and checkout actions require explicit user interaction and normal authentication.

## Public resources

- [Home](/): Start page for this storefront.
- [Search](/search): Search the public product catalogue.
- [Sitemap](/sitemap.xml): Public sitemap for discoverable pages.
- [Imprint](/page/cms/019fa3a922dd70b4a797403e90ffb4a6)
- [Privacy policy](/page/cms/019fa3a922a7720ba9da91545a4af6fc)
- [Terms](/page/cms/019fa3a9224e723083adf52d3c6bc09e)
- [Shipping/payment information](/page/cms/019fa3a9222670f9a71f046fb51b0984)
- [Revocation/cancellation policy](/page/cms/019fa3a92278718c8e008f8dbf41a9ba)
- [Robots policy](/robots.txt): Crawling and access rules.
- [Agent instructions](/agents.md): Guidance for AI agents interacting with this shop.

## Localization

- Current language: English (en-GB)
- Current currency: USD (US-Dollar)
- Supported languages: de-DE (German, Germany), en-GB (English, United Kingdom)
- Supported currencies: USD (US-Dollar)

## Guidance

- Use public sales channel resources as the source of truth.
- Verify product prices, availability, delivery information, taxes, and legal information on the live sales channel before presenting them as current.
- Prefer canonical storefront URLs or documented Store API routes when linking to products, categories, content pages, or policies.
- Respect `robots.txt`, rate limits, and normal checkout boundaries.



## Agentic commerce

- [UCP profile](/.well-known/ucp): Machine-readable Universal Commerce Protocol profile for this sales channel.

Use the UCP profile as the source of truth for enabled agentic commerce capabilities, supported transports, endpoint URLs, signing keys, and protocol versions. Only use capabilities and transports advertised in the profile.

## Agentic purchasing (sanctioned)

To buy from this shop, talk to the merchant's **sales agent** in **natural
language** over the A2A protocol (spec: https://a2a-protocol.org) — not through
the storefront. This is the merchant-approved path.

**Sales agent (A2A JSON-RPC):** `POST https://harness.agent-shop.agentic-commerce-lab.ai/`
**Agent card:** `https://harness.agent-shop.agentic-commerce-lab.ai/.well-known/agent-card.json`

### Payment — human handoff only (programmatic payment currently disabled)

Programmatic settlement via x402 is **currently disabled** on this shop. Do
NOT attempt to pay yourself, even if you have an x402 payment tool and a
funded wallet — the shop will not offer payment instructions.

Every purchase ends the same way: the shop places **no order**; instead you
receive a **browser handoff link** (`continueUrl`). Give that link to your
human — it opens the shop's browser checkout with the prepared cart, where
they pay with any offered method and the order is created. That is the
intended outcome, not an error. Human approval is built into this flow:
nothing binding happens until your human reviews the cart and total in the
browser and pays there themselves.

(When x402 is re-enabled, agents will be able to declare
`"supportedPaymentHandlers": ["com.shopware.x402"]` in message `metadata` and
settle in USDC on Base mainnet. Until then the declaration is harmless but
changes nothing — you still receive the handoff link.)

### The conversation — plain natural language, one JSON-RPC call per turn

```
POST https://harness.agent-shop.agentic-commerce-lab.ai/
Content-Type: application/json

{"jsonrpc":"2.0","id":"1","method":"message/send","params":{"message":{
"kind":"message","role":"user","messageId":"<unique-per-turn>",
"contextId":"<result.contextId from the previous response; omit on the first turn>",
"parts":[{"kind":"text","text":"I want to buy <product>. My email is <email>."}]}}}
```

- Reuse `result.contextId` on every following turn — it is your session.
- Just say what you want: find the product, add it to a cart, confirm the
order. The seller agent will ask for buyer details (email, first/last name,
phone, shipping address). The **email receives the product**, so use the
user's real address.

### Read machine data from `result.artifacts[].metadata` — never from prose

- `checkoutTerms` `{checkoutId, total}` — the real terms of the pending
checkout, relayed every turn until completion.
- `continueUrl` — the expected final artifact: NO order was placed. Give this
link to the human; it opens the shop's browser checkout with the same cart,
where they pay with any offered method. The link is signed and expires — if
the human reports it stopped working, ask the sales agent to complete the
checkout again for a fresh one.

### After the handoff

The order exists only once the human completes checkout in the browser —
nothing is left pending if they never open the link. Delivery is digital: the
shop emails the order confirmation with the download links to the buyer email.
The links use guest access (email + zip code verification) — no customer
account needed.

Notes:

- Only prepare what the user asked for; the human sees the full cart and total
in the browser checkout before paying.
- If a response claims completion but its metadata carries no `continueUrl`,
stop and report — do not invent a payment path. In particular, `orderId` or
`x402` payment instructions should NOT appear while programmatic payment is
disabled; if they do, stop and tell the user instead of paying.