Agent surface reference

What an agent sees has two parts: the Agent Page served at your normal URL, and an MCP endpoint for the Actions you approved.

URLs

Agents request the same public URLs everyone uses:

https://www.yourdomain.com/pricing

Your CDN passes requests to your existing site by default. It asks camolabs only for eligible agent requests. If camolabs can serve the Agent Page, the agent gets that version. Human navigations, search crawlers, unpublished pages, and misses all pass through to your existing site.

The installed adapter reads a routing policy from camolabs:

https://agents.yourdomain.com/.well-known/camolabs-routing-policy.json

This is infrastructure, not a discovery page. There is no llms.txt, hosted index, or public camolabs URL for agents to crawl. Agents reach everything through your own domain.

The page

An Agent Page is plain HTML built from your source page. It keeps the facts, links, and section order, and points at the site's MCP endpoint:

<link rel="mcp" href="https://agents.yourdomain.com/mcp" />
<meta name="camolabs-actions" content="2 action(s) via MCP at https://agents.yourdomain.com/mcp" />
<h1>Pricing</h1>
<section>
  <h2>Pricing facts</h2>
  <p>Starter begins at $499 per month.</p>
</section>
<section>
  <h2>Agent capabilities</h2>
  <p>Use this document's MCP link and call <code>tools/list</code> before submitting information to the site.</p>
</section>

JavaScript, decorative media, scraper noise, and unsupported claims are stripped out.

MCP

Each site has one MCP endpoint for its Actions:

curl -X POST https://agents.yourdomain.com/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Method	What it does
tools/list	Returns approved, active, configured Actions for published pages
tools/call	Validates input and completes an email_relay or webhook

The protocol calls these tools; the product calls them Actions. MCP exposes Actions only, not page content.

Action behavior

Email relay validates the submitted fields and sends a message to your verified destination address. camolabs records the outcome, not the message content.

Webhook validates the submitted fields and posts structured JSON to your endpoint. Static fields and a signing secret are configured in the Actions workspace.

Events

camolabs records server-side events when it serves a page, lists Actions, completes or fails an Action, relays an email, runs a liveness check, or runs a Task. Agent-ready pages set no cookies and carry no client-side state.