Your site ranks on Google. Does it show up when someone asks Claude where to buy something? In 2026 a growing share of buying, booking, and researching is done by agents acting for humans. If agents can't read, query, or call your site, you don't exist in that funnel. Here's the diagnosis — and the fix.
Concrete checklist, no fluff. Use the free tier of wmcp.sh to ship most of it in 10 minutes. Or have us do it for you — see /managed.
Three things shipped this year that flipped the equation: Claude's Computer Use, OpenAI's Operator/Agents API, and Cursor's autonomous mode. All three can drive a browser, call APIs, and execute purchases. Stripe reported >$80M in agent-driven transactions in their first measured quarter. This is real volume, not a demo.
"Agent commerce" / "agentic retail" is at the same point mobile commerce was in 2014: invisible to most operators, exploding for the ones who saw it coming. Making your site agent-ready now is the equivalent of adding viewport meta and responsive CSS then.
Pull up an agent (Claude, ChatGPT, Gemini, Cursor) and ask it to interact with your URL. If it fails, it's almost always one of these five.
Most sites render product info as HTML only — no application/ld+json block, no schema.org markup. Agents have to scrape, guess, or hallucinate the price, name, and availability.
→ Agent sees: a blob of text. Confidence: low.
Fix: Add a JSON-LD Product + Offer block on every product page. Five lines of HTML. Shopify, BigCommerce, Magento, and most CMSes have a setting or plugin that ships this automatically.
If you have an API, is it documented at a stable URL with an OpenAPI 3 spec? Probably not. Stripe, GitHub, Linear, Notion, Shopify all publish theirs. Most companies don't.
→ Agent sees: locked door. Cannot call programmatically.
Fix: Publish your OpenAPI spec at a known URL (e.g. /openapi.json). Take 1 hour. wmcp.sh's OpenAPI adapter then auto-converts every operation into an MCP tool your customers' agents can call.
Cloudflare Turnstile, PerimeterX, Akamai Bot Manager — defending against scrapers, but they also defend against legitimate AI agents. Even with perfect JSON-LD, the agent never reaches your page.
→ Agent sees: HTTP 403. No content extracted.
Fix: Allowlist verified agent user-agents (Anthropic's Claude-User, OpenAI's ChatGPT-User) at the WAF level. Or expose key endpoints through a public read-only API that bypasses the WAF for known shapes.
React/Vue SPAs that return <div id="root"></div> to anything that doesn't run JavaScript. Agents that fetch your URL see a blank shell, not your content.
→ Agent sees: empty document. Hydration required.
Fix: Server-side render (Next.js, Remix, Astro), or use a hybrid renderer that pre-builds key routes (Vite SSG). At minimum, output a static <noscript> block with the essential product/article data + JSON-LD.
Reading is half the job. The other half is doing: add-to-cart, search, book, submit, subscribe. Without an MCP server exposing your site's actions as tools, agents are stuck in read-only mode — useful for research, useless for transactions.
→ Agent sees: data only. Cannot complete a task.
Fix: Expose an MCP server. wmcp.sh's free tier does this automatically by ingesting your URL + structured data + OpenAPI spec, and serving the resulting tools at https://wmcp.sh/u/<your-url-hash>.
If you ship these, agents can read and act on your site within hours.
Product, Offer, FAQPage, Article, BreadcrumbList. The schema.org vocabulary is the de-facto agent-readable format. Five lines per page type.
If you have an API: ship /openapi.json at a stable URL. wmcp.sh ingests it — every operation becomes an agent-callable tool with typed inputs.
Whitelist Anthropic Claude-User + OpenAI ChatGPT-User user-agents at the Cloudflare / firewall layer. Verified, low-volume, legitimate.
wmcp.sh does this for free if you have JSON-LD or an OpenAPI spec. No code on your site — agents point at wmcp.sh/u/<hash> and get your tools.
application/ld+json. If you see Product/Offer schema, you're good on #1.User-Agent: ChatGPT-User. If you get 200 + real HTML, your WAF isn't blocking. If you get 403, fix #3.curl 'https://wmcp.sh/api/v1/tools?url=YOUR_PAGE_URL'. If it returns tools, agents can already work with you. If it returns no_tools_extracted, your site needs #1 or #4./openapi.json, /swagger.json, or /api-docs. If yes → free win. If no → either ship one or skip #2.The cornerstone above covers any site. These dig into the specific gotchas + checklists for each stack:
Variants, add-to-cart, inventory, Shopify Plus WAF. Most stores need zero code changes — wmcp.sh adapter works out of the box.
OpenAPI publishing, operation tagging, MCP-spec OAuth, agent-friendly rate limits. The 5 things API teams miss.
llms.txt template, code-example metadata, version signals, docs MCP servers. Mintlify / Docusaurus / Nextra compared.
Be recommendable when Claude picks tools for your buyer. Six non-technical moves any founder can ship in half a day.
Both paths end in the same place: agents like Claude / Cursor / Codex / OpenAI Agents can call your site's tools natively.
You ship JSON-LD + OpenAPI on your site. wmcp.sh exposes your URL as MCP tools, free, no signup. Works for product pages, blogs, documentation, public APIs.
curl 'wmcp.sh/api/v1/tools?url=…'JSON-LD audit, WebMCP markup on your top pages, OpenAPI spec from scratch if needed, custom MCP server hosted on your domain or ours, monitoring dashboard. 5-day turnaround for the starter package.
mcp.yourbrand.com| Approach | What it costs | Trade-off |
|---|---|---|
| DIY full custom MCP server | 2-6 weeks of engineering | Most control. Most maintenance. Most opportunity cost. |
| SaaS connectors (Composio, Zapier, Pipedream) | $50-500/mo per team + per-customer auth | Curated. Owner-side only. Your customers connect their accounts, not yours. |
| wmcp.sh self-serve | Free / $29 Pro / mo | Auto-generated from your URL. Works for shopper-side use cases. Some non-standard sites won't be covered. |
| wmcp.sh managed | $499 setup / $999+ /mo | Handles the long tail and custom integration. White-label option lets you publish under your own brand. |
Product schema on product pages, a published OpenAPI spec if you have an API, and an MCP endpoint that exposes your actions as tools. wmcp.sh gives you the MCP endpoint for free as long as you have one of the first two.curl 'https://wmcp.sh/api/v1/tools?url=YOUR_SITE_URL'. If tools come back, agents can already work with you via wmcp.sh. If you get no_tools_extracted, the page lacks structured data and no adapter matched — that's the work. /managed includes a free audit.Claude-User, ChatGPT-User) at the Cloudflare WAF rules level, OR expose a separate read-only public API that doesn't go through the Turnstile gate. Our managed service handles this configuration.Drop your URL, see what tools your site already exposes. Free, no signup for the first 100 reads.
Open dashboard →We look at your site, identify what's missing, and quote a fixed price to get it shipped.
Get audit →