Four protocols. One flow. Your agent does the work.
LaClawClaw is the first agent-native Shopify store. We don't have a checkout form — we have endpoints. An agent discovers us, picks a product, and hands the human a payment link. Here's the whole path.
AWP is the umbrella. Every other agent protocol is a sibling.
AWP doesn't replace A2A, MCP, AP2, x402, or any other agent standard. It's the layer above them — a single manifest at /.well-known/agent.json that declares which of them a site speaks and where to reach each. Agents read one URL, learn the full capability surface, and pick the right pipe.
How AWP stays thin as the ecosystem grows
AWP defines what a site speaks and where to reach each protocol. It never defines message envelopes, tool invocation, or payment semantics. Those live in the protocols AWP points at.
v0.2 ships a known-identifier list (a2a, mcp, acp, ap2, x402, skyfire, openapi, graphql) — but sites can declare custom protocols. Agents MUST ignore unknown identifiers gracefully. This lets AWP stay ahead of new protocols without spec revisions.
via + operationAny action can route through any declared protocol using the via field. Adding a new protocol is one entry in the protocols block — zero AWP spec change needed.
When a site speaks multiple protocols, agents need to pick. v0.3 will declare preferred_order, per-protocol capability flags (streaming, async, batch), health indicators, and fallback chains. Agents negotiate the pipe without extra roundtrips.
Auth, rate limits, idempotency, agent identity — declared once at the manifest root, inherited by all protocols. This stops every new protocol from re-inventing the same primitives.
The meta-principle: keep the spec under 200 lines. If AWP grows past that, it's absorbing semantics that belong elsewhere. That's the discipline that made robots.txt survive thirty years.
The flow — five steps, one agent, no human keystrokes until the final click
/.well-known/agent.json. One document declares every protocol we speak and every action we expose. No manual config.list_products tool, the agent pulls the live Shopify catalog. Structured JSON, not HTML scraping.get_product returns description, variants, availability. Agent has everything a human would read off a product page, but as structured data.create_cartwraps Shopify's stateless cart permalink pattern. The cart is a base64-encoded token — no server-side session needed.create_payment_linkreturns a Stripe URL scoped to the cart. The agent hands this URL back to its human — that's the only point a human touches the flow. PCI stays Stripe's problem. Agent-gated, human-paid.Install it in Claude Desktop
Drop this into your claude_desktop_config.json (on macOS: ~/Library/Application Support/Claude/claude_desktop_config.json), restart Claude Desktop, and you're shopping.
{
"mcpServers": {
"laclawclaw": {
"url": "https://agent.laclawclaw.com/mcp"
}
}
}Point any AWP-aware agent at the manifest and it configures itself. No paths to type, no config snippets to paste. The manifest tells the agent which protocol to speak and how.
curl -sS https://laclawclaw.com/.well-known/agent.json # Returns the full AWP v0.2 manifest — every protocol we speak, # every action we expose. No config required on the agent side.
Verify it's valid AWP v0.2 in one line — ours passes clean:
npx -y agent-json@latest validate https://laclawclaw.com/.well-known/agent.json # Validating: https://laclawclaw.com/.well-known/agent.json # ✓ Valid agent.json — no issues found.
The agent-json validator and the spec itself live at github.com/agentwebprotocol. Same folks behind LaClawClaw — we wrote the spec, shipped the validator, and made this store the reference implementation.
Try it right now — in your terminal
curl -sS https://agent.laclawclaw.com/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/list",
"params": {}
}'curl -sS -X POST https://agent.laclawclaw.com/agent/message \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer <agent_key>' \
-d '{
"type": "acp-request",
"from": "your-agent",
"payload": {
"operation": "checkout.create",
"params": {}
}
}'Both return the same canonical Stripe payment link. MCP is the clean tool-use path. A2A is agent-to-agent peer-speak with a bearer gate. Either gets your human to the $1 Founders Edition pre-order.
Launch partners — where the AI infrastructure lives
OpenClaw — the store-side clerk that converses with visiting agents in natural language — will run as a fine-tuned open-source model on Nebius H100s. Small base (Llama 3.3 / Qwen 2.5), fine-tuned on the LaClawClaw catalog, brand voice, and character lore. Prototype validated; production fine-tune kicks off post-launch. Cheaper, faster, and we own the weights.
When a visiting agent asks a question that leaves the catalog — "what else is in the designer-collectible space?", "who's Jensen Huang and why is he on a jacket?"— OpenClaw calls Tavily's AI-optimized search API and grounds the answer before returning. Keeps the shopping flow intact while letting agents satisfy their humans' tangents.
- Anthropic — Claude Opus 4.6 backs the reasoning scaffold during dev; powers the live demo agent on /agents.
- Shopify — inventory + fulfillment. Our MCP server proxies the Storefront API transparently.
- Stripe — agent-generated, human-paid payment links. Gated on retrieval; PCI is Stripe's problem.
- Vercel — hosts laclawclaw.com.
- Railway — hosts the jester gateway (A2A + ACP + MCP).
- Cloudflare — DNS, SSL, proxy.