For AI agents

AI agents don't need to scrape this site. IntentSite publishes a controlled interaction surface: every answer comes from one governed, human-approved knowledge base, and machines get first-class doors into it — no HTML parsing, no guessing.

Four doors, one knowledge base

Humans

Chat on the site

Visitors ask in natural language and get the canonical answer with rich media.

Crawlers & AI platforms

Read llms.txt

Every canonical question, answer summary, and URL in one plain-text file.

In-browser agents

WebMCP tool on every page

Pages register an ask_intentsite tool via the emerging WebMCP browser API.

MCP-native clients

Official MCP server

Claude, Cursor and other MCP clients connect over streamable HTTP.

All four doors open into the same room: identical answers, identical limits, identical conversation threads.

Live artifacts

llms.txt — machine-readable index of every canonical question and answer
GET /api/v1/ask — the Intent Map — every question the assistant can answer, as JSON
openapi.json — OpenAPI specification of the public API

Ask endpoint (REST)

One endpoint, two verbs. GET returns the Intent Map; POST asks a question (max 100 characters). Pass back the returned thread_id to continue a conversation. No API key required.

curl https://api.intentsite.com/api/v1/ask

curl -X POST https://api.intentsite.com/api/v1/ask \
  -H "Content-Type: application/json" \
  -d '{"question": "What is an IntentSite?"}'

curl -X POST https://api.intentsite.com/api/v1/ask \
  -H "Content-Type: application/json" \
  -d '{"question": "Tell me more", "thread_id": "<thread_id from previous answer>"}'

MCP server (Model Context Protocol)

IntentSite runs an official MCP server for MCP-native clients. In Claude, Cursor, or any MCP-capable tool, add it as a Streamable HTTP connection — no API key needed.

Endpoint

https://mcp.intentsite.com/mcp(also at https://api.intentsite.com/mcp)

Connection type

Streamable HTTP (stateless)

Auth

None required

Tools

ask_intentsite(question, thread_id?) — ask in natural language, max 100 characters; pass back thread_id to continue a conversation

list_intents() — discover every question the assistant can answer

Answers, rate limits, and conversation threads are identical to the REST API — MCP is a second door into the same assistant.

Try it live

This widget calls the public endpoint directly from your browser and shows the raw response — the same thing any agent receives.

Try:

Boundaries & provenance

Governed answers. Every answer comes from human-authored, approved content — not from free-running generation over scraped pages.
Rate limits. 10 requests per minute and 200 per day per caller, enforced server-side across all access doors.
Question length. Questions are capped at 100 characters.
Open by design. No authentication, cookies, or hidden headers required on any machine door.

Questions about machine access? Contact support@intentsite.com. See also Legal & Trademark.