# On: agent site

A landing surface for AI-referred shoppers and their agents. Search the catalog, open products, add to cart. Checkout completes on the brand's own site.

## What is here

- Machine-readable description of this surface: https://on.aigency.bot/api/agent
- Guide for language models: https://on.aigency.bot/llms.txt
- Product sitemap: https://on.aigency.bot/sitemap.xml

## WebMCP tools (in the page)

The page registers these tools on `document.modelContext` for browsers that support WebMCP. Each call updates what the shopper sees.

- `search_products`
- `get_product_details`
- `get_current_view`

## MCP endpoint (UCP)

The UCP manifest at https://on.aigency.bot/.well-known/ucp declares dev.ucp.shopping.catalog.search and dev.ucp.shopping.catalog.lookup and points at an MCP endpoint, `POST https://on.aigency.bot/api/ucp/mcp` (JSON-RPC 2.0 over HTTP). `tools/list` returns `search_catalog`, `lookup_catalog`, `get_product`, the UCP catalog binding; product ids are product URLs. Cart and checkout are not implemented over UCP.

## Product pages and the chat transport

Product pages served to a declared AI user agent carry schema.org/Product JSON-LD and return JSON on `Accept: application/json`; browser user agents receive the app shell, which renders the same product on load.

POST /api/chat is the page's own asynchronous transport (a callable envelope; the answer reaches the page out of band, not in the HTTP response). It is not an interface for agents today. The agent-facing interfaces are the WebMCP tools in the page, the product pages and the sitemap.

## Checkout

Adding to cart returns a checkout URL on the brand's own domain. The purchase is completed there by the human; this surface takes no payment.

## Rate limits

No authentication. Sustained automated load is throttled per agent; be reasonable.
