---
title: "How to send website traffic to your agent storefront | ZeroClick"
url: https://zeroclick.ai/resources/route-website-traffic-to-agent-storefront
fetched_at: 2026-09-28T01:09:47.657Z
---

# ZeroClick API catalog and pricing

## API reference, endpoint lookup and prices

**[ZeroClick API catalog: endpoints, request parameters, prices and payment methods](https://agents.zeroclick.ai/zcj/p9svsv4zcuw1/zeroclick/agent/guide).** Tell the seller advisor what you want to accomplish. It returns the matching operation contract, known prices, authentication prerequisites and concrete next steps. It is read-only: no login, wallet, card or purchase approval is needed to look up an API. It never executes a sale.

Available API services: Agent readiness report, Demo booking.

**Suggested next request:** GET [task guide](https://agents.zeroclick.ai/zcj/p9svsv4zcuw1/zeroclick/agent/guide?goal=URL_ENCODED_TASK). Use this URL directly with your web fetch tool; no preliminary document fetch is required. Include known inputs and desired output in the goal. Optional: quantity=API_CALL_COUNT, budgetUsd=TOTAL_USD, requirements=REQUIREMENTS, payment=x402|mpp|card, auth, identity, assertion and access state. Omit unknowns. Do not equate output items with API calls or guess a call count.

For private task details or known request arguments, POST https://agents.zeroclick.ai/zcj/p9svsv4zcuw1/zeroclick/agent/guide with Content-Type: application/json. Example: {"intent":"quote","goal":"YOUR_TASK","purchase":{"budgetUsd":"5.00"}}. Replace the task and budget with known facts; budgetUsd is a string. Include known buyerState, paymentCapabilities and arguments. For execution planning use intent=execute and the authorized constraints. Exact fields: [request schema](https://agents.zeroclick.ai/zcj/p9svsv4zcuw1/zeroclick/agent/schema). GET and POST are alternatives, not mandatory stages.

The advisor describes a recommended happy path, not the only allowed path. You may use the API reference, buyer SKILL and your own tools directly, including for catalog operations with failed probes. Missing guidance or an unverified probe is not a policy refusal. Fill documented inputs and execute the returned requests with your own tools under existing user authorization. Check usage cost AND minimum cash required against the budget. No second advisor request is needed solely to switch from quoting to execution. For needs_input, supply only missing facts. Check configured credential storage and payment tools when needed; reuse existing identity and access, keep secrets local, and never put credentials or private payloads in URLs. Unknown does not mean absent.

Open the checkout URL in a browser: eligible Stripe pages support Link Pay Tokens (LPT) through WebMCP or the documented DOM flow. Follow this storefront's /payment/card.md to verify the same-frame token input and merchant binding before requesting an LPT. Token submission requires payment authorization. If unavailable, privately send the checkout URL to your human to pay.

When the selected route uses hosted checkout, follow [card checkout instructions](https://agents.zeroclick.ai/zcj/p9svsv4zcuw1/payment/card.md) before requesting a token. LPT goes only to Stripe, never to the advisor or ZeroClick API. Poll the returned statusUrl before using credit or retrying delivery.

Verify delivery; a payment or HTTP 202 is not completion. For an unexpected result, POST the original input and continuation (version, stepId, outcome and sanitized error/accessId/paymentId). Reconcile uncertain payments or writes before retrying. Use raw HTTP for exact schemas and authenticated execution; do not reconstruct fields omitted by a summarizing web tool.

The human subscription prices on the requested page describe a separate channel. Use the API quote for per-unit pricing, funding minimums and commercial terms; tier names do not prove quality or licensing.

For an alternative documented path, use the [buyer SKILL](https://agents.zeroclick.ai/zcj/p9svsv4zcuw1/SKILL.md) or [full direct workflow reference](https://agents.zeroclick.ai/zcj/p9svsv4zcuw1/llms-full.txt). Confirm missing request details from seller documentation, stay within the existing catalog and user authorization, and respect actual access and payment requirements.
Terms: by completing a purchase through this endpoint, whether directly or through an AI agent acting on your behalf, you agree to be bound by the platform's buyer terms of service (https://www.zeroclick.ai/legal/buyer-terms-of-service). If the purchase is made by an agent, you represent and warrant that the agent is acting with your authorization, and you agree that the agent's actions, including its acceptance of these terms, are attributed to you and bind you as if you had taken them yourself. Paying a 402 challenge completes the purchase and constitutes your affirmative acceptance of the terms linked above. The link travels in every payment challenge and receipt as `terms`.

# How to Send Website Traffic to Your Agent Storefront

[ZeroClick Team](https://x.com/zeroclick) · September 15, 2026 · 5 min read · [Getting found by agents](https://zeroclick.ai/resources#discovery)

Your strongest starting page may already exist. A developer reading an API guide or comparing data sources has a concrete job. Giving that reader a relevant way to buy is often more useful than publishing another generic introduction to agents.

Keep the page's answer intact. Add a path from the task it explains to the matching service, with enough information to decide whether the offer fits. A link to an unrelated catalog is not a useful next step.

**Contents**
- [Choose pages by fit, then by observed traffic](#choose-pages-by-fit-then-by-observed-traffic)
- [Give the reader enough context to choose](#give-the-reader-enough-context-to-choose)
- [Check what different clients receive](#check-what-different-clients-receive)
- [Keep routing and measurement separate](#keep-routing-and-measurement-separate)
- [Review a complete route before adding more pages](#review-a-complete-route-before-adding-more-pages)

## Choose Pages by Fit, Then by Observed Traffic

Start with product, pricing, documentation, and practical guide pages. For each page, identify the task the reader is trying to complete and the service that could supply part of it.

| Existing page | Relevant next step | A mismatch to avoid |
|---|---|---|
| Guide to matching a product barcode | A lookup offer with identifier coverage and returned fields | A broad "AI solutions" link |
| Explanation of company enrichment fields | A bounded enrichment request or suitable account plan | A purchase that does not include the described fields |
| Tutorial for a hosted search service | An account with the required access and setup instructions | A one-off response when the tutorial needs persistent storage |

Use your own traffic observations to prioritize among pages with a matching offer. A high-traffic article with no relevant purchasable next step is not automatically a better candidate than a lower-volume implementation guide.

If site-wide reporting is not installed, say which pages and period you can observe. Neither a sitemap nor a storefront visit log proves the traffic distribution of the entire website.

## Give the Reader Enough Context to Choose

A contextual pointer should answer three questions: what can be purchased, why it helps here, and where the live terms and access instructions are. Avoid copying prices into dozens of articles when the storefront is the current pricing authority.

For the barcode example, a useful sentence might be: "To look up the product behind an identifier, use our barcode lookup service; the storefront lists supported identifiers, returned fields and current prices." Name only identifiers and fields your service actually supports.

Keep the original tutorial, comparison, or explanation available. Do not replace every article with the same catalog summary just because a machine requested it.

## Check What Different Clients Receive

A browser view is only one representation. Some clients inspect HTML directly; others request Markdown or use a tool that transforms the page. A link that exists only after JavaScript execution may disappear in another path.

ZeroClick's [website setup documentation](https://docs.zeroclick.ai/website/enable-agent-traffic) supplies storefront pointers for HTML, `llms.txt`, headers, and agent-oriented reads. Use your actual domain and seller-specific setup values. Registration of a pointer is not evidence that every index has crawled it or that every agent tool preserves it.

Where you serve Markdown, preserve the requested page's substantive answer and relevant links. Verify the response, content type, and cache behavior. The [Agentify overview](https://docs.zeroclick.ai/agentify/overview) explains the managed representation path. Review deployment and caching changes in the website's normal release process.

## Keep Routing and Measurement Separate

A pointer changes where a reader can go. Reporting tells you whether it went there. ZeroClick documents `src` values on storefront pointers so visits can identify the originating surface, and provides a separate [Page views integration](https://docs.zeroclick.ai/page-views/overview) for website requests.

Do not overwrite documented source values casually or assume they provide arbitrary per-article attribution. Check the fields actually recorded by your installation. Distinguish a source surface, a page URL, and a joined journey; those answer different questions.

Also distinguish recognized crawler traffic from an agent acting on a buying task. A crawler can consume the page without attempting a purchase. A rise in classified requests alone is not a sales result.

## Review a Complete Route Before Adding More Pages

Open the original page in the representations you support. Follow its pointer to the correct storefront. Check that the described service exists, its inputs match the article, its pricing is understandable, and its access method fits the task. If the buyer needs an account, follow the [provisioning guide](https://zeroclick.ai/resources/sell-accounts-and-api-keys), not a pay-per-call assumption.

For the barcode page, the route passes review when a reader can follow its lookup link, check identifier coverage, find the required input and price, and understand how to obtain the result. A generic storefront link that forces the reader to search again needs a more specific destination or clearer instructions.

Track that page-to-offer transition using the [pilot guide](https://zeroclick.ai/resources/measure-an-agent-commerce-pilot). Measure visits, attempts, payments, and useful deliveries separately so you can tell whether the pointer is helping.

For a page with no suitable offer, retain the useful information and link to an appropriate explanation or human contact. Not every page needs a purchase button.

## Keep Reading

1. [How to sell accounts and API keys to AI agents](https://zeroclick.ai/resources/sell-accounts-and-api-keys)
2. [How to measure an AI agent commerce pilot](https://zeroclick.ai/resources/measure-an-agent-commerce-pilot)
3. [ZeroClick docs: website / enable agent traffic](https://docs.zeroclick.ai/website/enable-agent-traffic)

## More in Getting found by agents

- [What is an agent storefront?](https://zeroclick.ai/resources/what-is-an-agent-storefront) — An agent storefront is the machine-readable version of your store: a URL where an AI agent can read what you sell, the current prices and plans, and the exact steps to buy.
- [What is llms.txt, and what should a seller put in it?](https://zeroclick.ai/resources/what-is-llms-txt-for-sellers) — llms.txt is a plain-text file at the root of a website, at `/llms.txt`, that tells AI agents and language models what the site is and where to look.

[All resources in this category](https://zeroclick.ai/resources#discovery)