# Site for Agents

> Make your website readable, quotable, and buyable for AI agents. Site for Agents is a self-serve subscription ($30/mo) that makes any website agent-ready: a hosted MCP server, ACP support, schema.org structured data, llms.txt, markdown mirror pages, AI-crawler configuration, and a WordPress plugin. Installed in minutes, kept in sync automatically.

Key facts:
- Price: 30 USD/month, single all-inclusive plan, cancel anytime
- Platforms: WordPress (one-click plugin), any other site via snippet
- Sign up / contact: https://siteforagents.com/#signup · hello@siteforagents.com

## Docs

- [Homepage as markdown](https://siteforagents.com/index.md): full product description, feature list, pricing, and FAQ in plain markdown
- [Full content](https://siteforagents.com/llms-full.txt): everything in one file

## For agents

- [MCP endpoint](https://siteforagents.com/mcp): live MCP server (streamable HTTP, JSON-RPC 2.0) — tools: get_product_info, get_pricing, get_readiness_checklist, get_faq, how_to_sign_up

---

# Site for Agents — Make your website readable, quotable, and buyable for AI agents.

> AI agents are already on your website. They can't read it.

ChatGPT, Claude, and Perplexity now research, compare, and buy on behalf of your customers. Sites they can parse get cited and chosen. Sites they can’t get skipped. One subscription makes yours machine-readable — MCP, ACP, schemas, llms.txt, and agent-formatted pages, generated and kept in sync.

**Price:** $30/mo (30 USD/month, everything included, cancel anytime)
**Sign up:** https://siteforagents.com/#signup
**Contact:** hello@siteforagents.com

## Is your site agent-ready?

Most websites fail this checklist:

- [ ] **llms.txt** — typical result: `404 NOT FOUND`. How to check: Fetch https://your-site.com/llms.txt — most sites return 404.
- [ ] **Markdown versions of pages** — typical result: `NONE DETECTED`. How to check: Try appending .md to a page URL, or look for rel="alternate" type="text/markdown" links.
- [ ] **schema.org structured data** — typical result: `0 OBJECTS FOUND`. How to check: View source and search for application/ld+json — check coverage of Product, Offer, FAQPage.
- [ ] **MCP endpoint** — typical result: `CONNECTION REFUSED`. How to check: POST a JSON-RPC initialize request to /mcp — almost no site answers.
- [ ] **ACP / agentic commerce** — typical result: `NOT DETECTED`. How to check: Check for agent-consumable product feeds and checkout intent support.
- [ ] **AI crawler directives** — typical result: `UNMANAGED`. How to check: Read robots.txt — are GPTBot, ClaudeBot, PerplexityBot explicitly handled, or blocked by a default?

## What you get

### A live MCP server for your site
Agents connect over the Model Context Protocol and query your products, pages, pricing, and docs directly — structured answers instead of scraped guesses.
`→ /mcp · JSON-RPC 2.0 · streamable HTTP`

### Ready for agentic commerce
Agentic Commerce Protocol readiness so shopping agents don’t just read your catalog — they can act on it.
`→ product feeds · checkout intents`

### schema.org on every page
The JSON-LD that agents and answer engines actually rely on — products, offers, FAQs, organization — generated and validated for you.
`→ Product · Offer · FAQPage · Organization`

### A machine-readable map of your site
llms.txt and llms-full.txt generated from your live content and kept in sync, so models know exactly what you offer and where to look.
`→ /llms.txt · /llms-full.txt`

### Every page, stripped for agents
Clean text/markdown versions of your pages — no JavaScript, no layout soup, no cookie banners. Just your content, in the format models read best.
`→ /any-page.md · text/markdown`

### One-click install on WordPress
Install the plugin, activate, done. The full agent layer runs on your existing WordPress site and stays synced as you publish.
`→ one-click install · auto-sync`

### The right agents, let in properly
robots.txt directives and headers tuned for GPTBot, ClaudeBot, PerplexityBot and friends — so the crawlers that feed answer engines get what they need.
`→ GPTBot · ClaudeBot · PerplexityBot`

## How it works

01. **Install** — Add the WordPress plugin or paste a single snippet. No re-platforming — nothing about your human-facing site changes.
02. **We generate your agent layer** — Your MCP server, schemas, llms.txt, and markdown mirrors are built from your live content — hosted by us, synced automatically as you publish.
03. **Agents read, cite, and buy** — Answer engines cite you. Research agents quote you accurately. Shopping agents parse your catalog. You show up where decisions now happen.

## Pricing

One plan: **$30/mo**. Everything above included — MCP server, ACP support, schema.org structured data, llms.txt, markdown mirrors, WordPress plugin, AI crawler configuration, and support for future protocols as they ship. Cancel anytime.

## FAQ

### What does "agent-ready" mean?
AI agents — ChatGPT, Claude, Perplexity, and the shopping and research assistants built on them — visit websites on behalf of your customers. Most sites serve them megabytes of JavaScript and layout markup with no structured meaning, so agents misread prices, miss products, and move on. An agent-ready site exposes its content through the channels agents actually use: structured data, llms.txt, markdown versions of pages, and live protocols like MCP and ACP.

### Will this change my website for human visitors?
No. The agent layer runs alongside your existing site — humans see exactly what they see today. If anything, it helps your classic SEO too: structured data, clean sitemaps, and crawler configuration are ranking signals for traditional search as well.

### Do I need a developer?
On WordPress, no — install the plugin, activate it, and the agent layer is generated for you. On other platforms it’s a copy-paste snippet or a DNS-level setup we walk you through. Nothing about your stack changes.

### What are MCP and ACP?
MCP (Model Context Protocol) is the open standard AI agents use to connect to external systems — we host an MCP server that answers questions about your site with structured, current data. ACP (Agentic Commerce Protocol) is the emerging standard for letting agents transact — product feeds and checkout intents — so agents can buy, not just browse.

### Which platforms are supported?
WordPress has a dedicated one-click plugin today. Shopify, Webflow, custom stacks, and anything with a public sitemap work via a snippet. If agents can reach your site, we can make it readable to them.

### How is this different from an SEO tool?
SEO tools optimize how you rank in a list of blue links. Site for Agents makes your site machine-operable: agents can parse your content, verify facts, cite you in answers, and act on your catalog. It’s the infrastructure layer for the traffic that no longer starts at a search results page.

### What happens when a new protocol ships?
It’s included. Your subscription covers the agent layer as a living service — when the next standard emerges, your site supports it without you touching anything.

### Can I cancel anytime?
Yes. It’s a monthly subscription with no lock-in. Cancel and your site simply goes back to being agent-invisible — we hope you won’t want that.

## For agents

This site practices what it sells:

- https://siteforagents.com/llms.txt — site map for LLMs
- https://siteforagents.com/llms-full.txt — full content, one file
- https://siteforagents.com/index.md — this page as markdown
- https://siteforagents.com/mcp — MCP · streamable HTTP · JSON-RPC 2.0

The MCP endpoint at https://siteforagents.com/mcp speaks stateless MCP streamable HTTP (POST JSON-RPC 2.0). Available tools: get_product_info, get_pricing, get_readiness_checklist, get_faq, how_to_sign_up.

---

## Using the MCP endpoint

POST JSON-RPC 2.0 messages to https://siteforagents.com/mcp with Content-Type: application/json.
The server is stateless: no session id required, responses are plain application/json.

Example — initialize:
{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"your-agent","version":"1.0"}}}

Example — list tools:
{"jsonrpc":"2.0","id":2,"method":"tools/list"}

Example — call a tool:
{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"get_pricing","arguments":{}}}