What is an agent site?
An agent site is the version of your website that AI agents see. It carries the same products, prices, policies and business logic as the page a human sees, rendered as a surface a bot can read and act on, and it is served only to identified AI agents on your own domain.
The closest analogy is the mobile site. Fifteen years ago, sites noticed a new class of visitor arriving on a small screen with a slow connection, and they built a rendering for it rather than asking phones to cope with desktop pages. AI agents are the next visitor in that line. They arrive without a screen, without JavaScript, and with a budget measured in tokens rather than seconds.
What an agent gets that a human does not
A human page is built for eyes. It carries navigation menus, hero images, cookie banners, a chat widget, tracking scripts, promotional overlays and the CSS that lays them out. An AI agent fetching that page receives all of it as text and has to find the answer inside.
An agent site strips the page down to what the visitor came for. Simple bots and crawlers get server-rendered text with headings, lists, links and tables. On our network a Forbes article went from 1,201 KB of HTML to 41 KB of Markdown, a 97% reduction, and across ten publisher articles the saving ran from 56% to 97.5%. Computer-use agents get slim HTML with forms and buttons intact, overlays suppressed, sticky elements made static and animations disabled, so a task like adding a product to a cart takes fewer steps. The differences between those visitor classes have their own page, linked below.
The facts do not change. The format does. Same facts, cleaner format, bots only.
What stays the same
Everything behind the page. Your catalogue, your pricing engine, your inventory, your checkout and your CMS are untouched. The agent site fetches the human page from your origin, transforms it, and returns the transformed version to the bot. When you update a price on the human site, the agent site reflects it on the next fetch.
Your human visitors never see the agent site. Googlebot and Bingbot never see it either, by design, so there is no effect on search indexing. The agent site exists for the visitor class that search engines and analytics tools do not serve.
How a bot reaches it
The agent site lives on a subdomain of your own domain, typically tollbit.yourbrand.com. A rule in your CDN or WAF (Akamai, Cloudflare, Fastly, CloudFront, DataDome, Imperva or HUMAN) matches the user agents of known AI agents and forwards their requests there. The bot asked for yourbrand.com/product, and that is the URL it believes it read and the URL it cites. The subdomain is plumbing, not a public address.
That is the whole integration: a DNS record and a routing rule. There is no code change on your site and no CMS plugin.
What you can do once it exists
A rendered surface is the first job. The second is control over it. An agent site lets you:
- Rewrite what bots see on any page without touching the human page.
- Publish agent-only pages (comparisons, spec sheets, FAQs) that exist only in the sitemap bots read, with a fallback so a human who clicks a citation lands on a real page.
- Serve different versions to different platforms where their agents behave differently.
- See, in server logs, which agents read which pages and whether they succeeded. Google Analytics cannot show this, because bots do not run JavaScript.
Why this matters now
Bot traffic passed human traffic on the web in 2026. Cloudflare's CEO put automated traffic at about 60% of requests in May 2026 and forecast roughly 1,000 times more automated traffic within five years. AI applications cannot cache the internet, because retrieval loads pages fully into a context window every time a user asks, so the same page is fetched again and again. Our network of 10,000+ sites sees more than 200 million AI bot fetches a day.
That is a visitor, not a nuisance. You already serve humans differently on desktop, mobile, in an app, by email and by SMS. An agent site is the same decision applied to the newest audience.
Where TollBit fits
TollBit has run agent sites for about three years, first for publishers and now for brands and commerce sites. TollBit is the origin for bot traffic on your domain, serves the robots.txt and sitemap bots read, and provides the Agent Site CMS used to edit and publish the agent-facing version of any page. Setup is two IT changes: forward your server logs and point a subdomain.
Frequently asked questions
Does an agent site change my human website? No. The human page is fetched from your origin and transformed for the bot. Nothing is written back, and humans are never routed to the agent site.
Does it affect SEO? Googlebot and Bingbot are excluded from routing, so they continue to index the human page. The agent site serves AI agents only.
Is showing bots a different rendering a form of deception? The facts on the agent site are the facts on the human page, in a format a bot can read. Serving the same content in a form suited to the visitor is what mobile sites, RSS feeds and print stylesheets have always done.