The front door for every AI agent

Convert customers faster when AI agents ask you directly

Your buyers' agents are already reading your site and guessing. CAP lets them ask your agent instead and get the answer you published, with a link to buy or book. In our benchmark, that took 3.5 steps.

The problem

Websites weren't built for the agentic era

Buyers now send their own agents to compare, shop, and book. Cloudflare saw daily AI-agent requests grow more than 1,700% over the past year, and Meta says more than 10 million people set up its Muse agent in about six weeks, mostly to shop. Those agents still read pages built for people, often a dozen page loads for one answer, and the buyer still has to find the page and act. You have no say in the answer, and no idea the visit happened.

A browsed answer

The agent loads page after page, works past banners and scripts, and returns its best reading: maybe a stale price or the wrong store’s hours. The buyer still has to find your page. You never see the question.

A CAP answer

The agent asks once. Your agent answers from the content you publish, with a link to the exact product, plan, or booking page. The question shows up in your dashboard.

Less friction

From a question to checkout

Every layer between a buyer's question and checkout is a place they drop off. CAP removes the layers that exist only because your site was built for people.

Without a door

  1. 1The agent searches the web for your site.
  2. 2It loads page after page, past banners and scripts.
  3. 3It guesses which price, size, or store is current.
  4. 4The buyer opens your site to check the answer.
  5. 5They find the page again, or fill out a form and wait.

With CAP

  1. 1The agent reads agent.txt and asks your agent.
  2. 2Your agent answers from your content, with a link.
  3. 3The buyer follows the link to buy, book, or sign up.

In our benchmark, the visiting agent took 3.5 steps per question through CAP, against 11 to fetch the site and 13 to browse it, and each correct answer cost 76% less than fetching and 83% less than browsing. See the results

For your business

Your answer, your checkout, your limits

Answers that end in a sale

The reply links to the right product, plan, or booking page. Checkout and signup stay on your site.

No wait for a reply

A pricing, stock, or policy question is answered when it is asked, not after a contact form and a callback.

Know why they came

Every agent asks a question, so you see the intent behind each visit in your dashboard. Your agent answers buyers, routes big deals to your team, and declines questions you would rather not answer.

Your record, not your pages

The agent answers from the content you publish in Cosmic. When a page is out of date, the visitor still gets the current price, hours, or policy.

One agent for people and agents

Visitors chat with your agent on your site today. Agents ask the same agent through the door.

Your tools stay behind the door

Visiting agents get the answer, never your keys, tool list, or drafts. A daily token limit keeps a busy day from running away with usage.

Behind the door

The same Cosmic agent, connected to your record

CAP is a door on the agent you already run in Cosmic. It answers from your published content, your APIs, your MCP tools, and account questions after login. Those calls stay on your side. Visiting agents only see the reply. About the customer agent

Your content

  • Content you publish in Cosmic: products, plans, locations, policies, docs
  • Semantic search, so a question lands on the right object even when it names no page
  • Structured queries for exact questions, like which stores are open Saturday

Your systems

  • Your own APIs, called on your side with your keys
  • MCP servers your agent already uses
  • Account questions, after the person logs in with OAuth

Try it

Is your website CAP-able?

Enter a domain. We read its agent.txt, ask one public question, and report what passed.

See it running

Try the door at cosmicjs.com

Leo answers questions about Cosmic from the docs we publish. Point your agent at cosmicjs.com/agent.txt, or ask directly.

curl https://www.cosmicjs.com/cap/v1/messages \ -H 'content-type: application/json' \ -H 'cap-version: 1.0' \ -H 'cap-from: agent:your-agent' \ -d '{"message":"What is Cosmic?"}'

Ready when agents arrive

Why agents will use your door

An agent takes the cheapest reliable path to an answer. A front door is that path, so agents that know about it use it.

It knows where to go

agent.txt at the domain root gives one URL. No guessing which pages matter and no sitemap walk.

It gets the record, not the page

No cookie banners, bot blocks, or JavaScript rendering. The answer comes from the content the company publishes.

It saves tokens

One message instead of dozens of pages of HTML. In the CAP benchmark, an answer took about 19,000 tokens through CAP, against 48,000 by fetching the site and 112,000 by browsing it.

Follow-ups are cheap

Send the next question with the earlier message id. The company keeps the thread, so nothing is sent twice.

Same answers, a fifth of the cost of fetching the site and a seventh of browsing it. Read the CAP benchmark · Cosmic's results

Most assistants don't look for agent.txt on their own yet. The homepage link lets agents that read your page find the door, and the CAP MCP server lets Claude, Cursor, and other assistants ask it today.

How it fits

A front door, alongside the rest

How CAP fits with llms.txt, MCP, and A2A
CAPThe front door. One question in, the company’s own answer out, for public questions and account questions.
llms.txtDocumentation written for models to read.
MCPTools for your own agent. In Cosmic, they stay behind the door and visiting agents never load them.
A2AAgent to agent, once two agents already know each other.

Setup

Cosmic hosts the agent

The agent is ready in your dashboard. Drop it on a site with one line of code for people, or one agent.txt file for their AI agents. You do not run a server for either.

For people on your site

Open the agent under Agents, then the Website tab. Turn the widget on and paste this line. Website widget docs

<script src="https://www.cosmicjs.com/agent.js" data-key="pk_your_key" async></script>

For their AI agents

On the same agent, open Other agents and set the front door to Active. Publish the file it gives you at /agent.txt, next to robots.txt. These are the real lines from cosmicjs.com/agent.txt. CAP docs

Protocol: CAP/1.0 Name: Leo Chat: https://www.cosmicjs.com/chat CAP: https://www.cosmicjs.com/cap/v1 OAuth: https://www.cosmicjs.com/oauth Spec: https://conciergeprotocol.org/cap.txt

Turn it on in Cosmic

CAP is free and available on every Cosmic agent. On the agent, the Website tab is the chat line, and Other agents is the agent.txt file. Paste one, publish the other, and the site has a front door.

Want us to do it with you? Contact us for a hands-on agent-ready assessment and activation. Already a customer? We'll add 10 million AI tokens to your account to cover it.