Examples on this page use a seller named Acme whose storefront runs on the custom domain
agents.acme.com from step 1. Substitute your own values as you paste: your storefront domain everywhere agents.acme.com appears (or your default pay URL, like https://acme.pay.zeroclick.io, if you skip the custom domain), your store name in the callout and badge text, and your seller id in the head snippet’s ?seller= parameter.1
Serve your storefront on your own domain
RequiredAgents click through to a domain they recognize more often than a generic one, so serve your storefront on a subdomain you own rather than the default
<your-slug>.pay.zeroclick.io. Acme, the example seller on this page, uses agents.acme.com, and every snippet below carries it. Configure yours under Custom domains in your store’s settings before you paste anything: the domain is baked into the head tags, the callout, the badge, and the llms.txt links, so setting it up first means you paste each snippet once.2
Add the head tags to every page
RequiredPaste into every page’s The
<head>:alternate link advertises your storefront’s llms.txt to crawlers. The inline script marks the document as JavaScript-capable and removes the agent callout (next step) for human visitors once the page loads. The badge script advertises the storefront to crawlers that do run JavaScript.If your site sets a strict Content-Security-Policy, allow
img-src for your storefront domain (the badge image) and script-src for cdn.zeroclick.io.3
Paste the agent callout right after the opening body tag
RequiredAgents read raw HTML top to bottom, so this block must lead the document. Paste it immediately after the opening The callout is text for agents, and it does not need to look like part of your page. The head script removes it for human visitors once the page loads, and it stays visible without JavaScript, so nothing on your site is served only to agents. Of everything on this page, this step does the most to route agent purchases through your storefront.
<body> tag:4
Add your storefront to llms.txt
Highly RecommendedAdd this block near the top of your site’s
/llms.txt, right after the title and summary. If your site does not serve one yet, create the file with it:5
Serve markdown to agent fetchers
Highly RecommendedMany agent tools fetch pages with an
Accept header that prefers text/markdown over text/html; browsers never do. Returning your llms.txt content for those requests reaches summarizing fetchers that would otherwise drop head tags and links during HTML conversion. Apply it to every page, not just the homepage: agents land on pricing and docs pages just as often.This is content negotiation, not cloaking: the same page in the representation the client asked for. It does change what your existing URLs serve to markdown-preferring clients, so decide deliberately. Send Vary: Accept so caches keep the two representations apart.6
Show the badge to human visitors
OptionalThe visible ZeroClick badge is a plain link and image for humans, typically in the footer. The image is served from your storefront domain, so it carries your store name and updates automatically; swap Nothing moves it at runtime, so render it however your site renders content, including natively inside a React or Vue app. The callout and head tags carry the agent traffic.
badge-light.svg for badge-dark.svg on dark footers:Verify your changes
-
Fetch the homepage raw, the way an agent does. The callout heading appears near the top of the HTML and the
alternatelink tag is in the head: - Load the page in a browser. The callout is gone, and the badge renders where you placed it.
-
Your site’s
/llms.txtserves the agentic commerce block near the top. -
If you serve markdown to agent fetchers, a markdown-preferring request gets it:
Next steps
Integrate your API
The billing guard contract: verify, check allowance, serve, settle usage.
How ZeroClick works
What happens after an agent lands on your storefront.