--- title: "What is an agent storefront? | ZeroClick" url: https://zeroclick.ai/resources/what-is-an-agent-storefront fetched_at: 2026-10-02T02:24:57.879Z --- # 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/217sna9wi4v1/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/217sna9wi4v1/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/217sna9wi4v1/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/217sna9wi4v1/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/217sna9wi4v1/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/217sna9wi4v1/SKILL.md) or [full direct workflow reference](https://agents.zeroclick.ai/zcj/217sna9wi4v1/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`. # What is an agent storefront? **ZeroClick Team** | September 15, 2026 · 6 min read | [Getting found by agents](https://zeroclick.ai/resources#discovery) 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 pay, then buy and use your product without a human filling in forms. On ZeroClick every seller gets one at a pay URL, and most serve it on their own subdomain. **Contents** - [What an agent finds when it arrives](#what-an-agent-finds-when-it-arrives) - [How a purchase moves through it](#how-a-purchase-moves-through-it) - [Storefront versus website](#storefront-versus-website) - [Where storefronts get found](#where-storefronts-get-found) - [What stays yours](#what-stays-yours) - [Frequently asked questions](#frequently-asked-questions) **In short** - An agent storefront is text and structured data first. Agents read it the way curl does, with no JavaScript and no forms. - It publishes four things a buyer needs: the catalog, live prices and plans, the payment steps, and the machine specs (`manifest.json` and `openapi.json`). - It sits in front of your existing API. Agents call the storefront's pay URL with the request they would have sent you directly, and the storefront handles identity, payment and forwarding. - It is separate from your website. Your site points agents at the storefront; humans keep the pages they already use. ## What an agent finds when it arrives A ZeroClick storefront answers at a pay URL such as `https://acme.pay.zeroclick.io`, or at a custom domain like `agents.acme.com`. Its front door is a plain-text file, `llms.txt`, that opens with what the business sells and then links a short set of pages written for agents: - An overview of the API and a map of the documents. - Services and pricing, one page per service with its full price matrix, how to call it, and the API reference. - How to pay, which walks the 402 flow and each payment rail step by step. - An error reference, so the agent knows how to react to every code. - Identity, where an agent registers a credential for plan purchases and free allowances. - Hand off to a human: a tracked referral link for anything a person needs to finish. - A machine catalog at `manifest.json` and the full API spec at `openapi.json`, both meant to be read at call time rather than cached. The storefront also carries structured data in JSON-LD for agents that read schema before prose. It states up front that no signup and no API key are needed: agents pay per use with x402, MPP or a card, autonomously or with their human's approval. ## How a purchase moves through it The storefront is a transparent proxy over your API. An agent sends the same method, path, query and body it would send you directly, to the pay URL instead. An unpaid request comes back as a single priced 402 response. The agent pays the challenge with its wallet, or its human pays by card, and retries the identical request with the proof attached. ZeroClick verifies the payment, binds it to a buyer identity, signs the request and forwards it to your upstream base URL, which agents never see. Your backend verifies the signature, checks the buyer's allowance, does the work and reports the usage. The response goes back to the agent, and the money settles to your Stripe account in fiat or USDC. An agent that shows up without a wallet is not stuck. It can create a managed wallet on the spot, or hand its human a card checkout page that Stripe hosts under your branding. ## Storefront versus website Your website is for people. It runs JavaScript, shows images and asks visitors to click through menus and fill in forms. Agents read raw HTML top to bottom, without running any of that, so a page built for humans gives them little to work with. The storefront is the agent's version of the same business. It carries the catalog and the prices in a form an agent can act on, and it stays in sync with what buyers are charged because both come from the same catalog. Your website's job is to point agents at it: a link tag in the head, a short callout only agents see, a line in your own `llms.txt`, and a visible badge. ZeroClick calls that set of pointers the Agent Magnet, and each pointer is stamped so the storefront records which one routed each agent. ## Where storefronts get found Agents reach a storefront through the seller's website, through the indexes agents search, and through links other agents pass along. ZeroClick lists every storefront on [zero.xyz](https://zero.xyz/), agentic.market, x402scan and mppscan. A seller can also add a Buy with AI button to its own pages, so a person can hand the storefront to the assistant they already use. ## What stays yours You keep the API, the product and the customer relationship. ZeroClick operates the agent-facing layer: the storefront pages, the payment challenges, wallet and identity resolution, verification and settlement, request signing, usage records and transaction analytics. Your integration is the billing guard in your backend, which the seller SDKs for TypeScript, Python, Go and Ruby implement. ## Frequently asked questions ### Do I need to build a new API for an agent storefront? No. You connect an existing API. The storefront maps each agent request onto your upstream base URL and forwards it signed, so the endpoints, paths and bodies are the ones you already run. ### Does an agent storefront replace my website? No. Humans keep your website. The storefront is the agent-readable counterpart, and the website's job is to point agents at it. ### Can agents buy plans, or only single calls? Both. A storefront can sell pay-as-you-go calls, prepaid credits, subscriptions, subscriptions with included usage, and free trials. It can also create a durable account and issue an API key the buyer then uses with you directly. ### What happens when an agent has no wallet? It can create a managed wallet itself at no cost, or hand its human a Stripe-hosted checkout page for a card, Link, Apple Pay or a bank account. Free actions such as booking a demo need no payment method at all. ### Should the storefront live on my own domain? Yes, when you can. Agents click through to a domain they recognize more often than a generic one, and ZeroClick's setup treats a custom subdomain as the first step. ## Keep reading 1. [What makes a product agent-purchasable?](https://zeroclick.ai/resources/what-makes-a-product-agent-purchasable) 2. [How to send website traffic to your agent storefront](https://zeroclick.ai/resources/route-website-traffic-to-agent-storefront) 3. [What is llms.txt, and what should a seller put in it?](https://zeroclick.ai/resources/what-is-llms-txt-for-sellers) 4. [DeepAI x ZeroClick: AI image tools any agent can buy](https://zeroclick.ai/blog/deepai-ai-image-tools-any-agent-can-buy) 5. [ZeroClick docs: what is ZeroClick](https://docs.zeroclick.ai/index) ## More in Getting found by agents - [How to send website traffic to your agent storefront](https://zeroclick.ai/resources/route-website-traffic-to-agent-storefront) — ZeroClick Team, September 15, 2026 - [What is llms.txt, and what should a seller put in it?](https://zeroclick.ai/resources/what-is-llms-txt-for-sellers) — ZeroClick Team, September 15, 2026 [All resources in this category](https://zeroclick.ai/resources#discovery) --- [Get started](https://zeroclick.ai/get-demo) | [Read the docs](https://docs.zeroclick.ai)