--- title: "What is ZeroClick? - ZeroClick" url: https://zeroclick.ai/docs/product-shapes fetched_at: 2026-10-04T14:48:37.557Z --- # 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/gprh5vsv5d7l/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/gprh5vsv5d7l/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/gprh5vsv5d7l/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/gprh5vsv5d7l/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/gprh5vsv5d7l/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/gprh5vsv5d7l/SKILL.md) or [full direct workflow reference](https://agents.zeroclick.ai/zcj/gprh5vsv5d7l/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 ZeroClick? ZeroClick turns any API or offering into an agent-purchasable service. It provides [x402](https://www.x402.org) and [MPP](https://mpp.dev) support, a machine-readable storefront, and agent transaction analytics. ZeroClick is the storefront and transaction layer for selling to AI agents. Connect an existing API or product, and agents can discover it, pay for it, and use it. You keep the API and the product experience. ZeroClick operates the agent-facing payment, identity, and proxy layer in front of it. Revenue settles to your connected Stripe account, in fiat or USDC. On encrypted calls, ZeroClick processes payment and routing without reading the body plaintext. The proxy holds no private key for the [request or response body](https://zeroclick.ai/concepts/end-to-end-encryption). ## How it works Every seller gets a hosted pay URL, for example `https://acme.pay.zeroclick.io`. The pay URL is a machine-readable storefront. Agents read it to find your services, plans, and prices, then transact with your API through it. **Step 1: An agent calls your pay URL.** A shopping assistant, coding agent, or procurement agent discovers your storefront, picks a plan, and calls your service through the pay URL using x402 or MPP. **Step 2: ZeroClick authenticates and charges.** ZeroClick resolves the agent's identity, handles the payment challenge, then signs the request and forwards it to your API. If an agent has no wallet, ZeroClick creates one on the spot. **Step 3: Your API serves the request.** Your API verifies the request signature, checks the agent's allowance, and returns the result. **Step 4: You get paid.** Funds settle to your Stripe account. ZeroClick records the usage and the transaction for analytics: which agents bought, which payment rails they used, and how each service converts. Availability by country is listed under [supported countries](https://zeroclick.ai/resources/supported-countries). The [how ZeroClick works](https://zeroclick.ai/concepts/how-zeroclick-works) page covers the same lifecycle at the protocol level. ## What ZeroClick handles, and what you build ZeroClick operates the agent-facing side: the storefront, payment challenges, wallet and identity resolution, payment verification and settlement, request signing, usage recording, and transaction analytics. You add one thing to your API: a billing guard. On each forwarded request, your backend verifies ZeroClick's signature, checks the agent's allowance, does the work, and reports what was used. The [seller SDKs](https://zeroclick.ai/sdks/overview) for TypeScript, Python, Go, and Ruby implement the guard. The [REST walkthrough](https://zeroclick.ai/integrate/rest-walkthrough) covers doing it without an SDK. ## Core concepts | Concept | Meaning | |---|---| | Seller | Your storefront on ZeroClick. Each seller gets a pay URL that agents call and pay through. | | Service | One thing agents can buy: an API, a model, a workflow, or a feature. | | Meter | A billable measurement within a service, such as requests or output tokens. | | Plan | How agents pay for a service: pay as you go, credits, subscription, or subscription plus usage. | | Agent | The buyer. Every agent is identified and verified, and every call is logged. | | Allowance | The pre-request check that decides whether an agent's plan covers its usage. | ## Explore - [Quickstart](https://zeroclick.ai/quickstart) - Serve your first paid agent request in about ten minutes. - [Integrate your API](https://zeroclick.ai/integrate/overview) - The integration contract: verify, check allowance, serve, settle usage. - [Enable agent traffic](https://zeroclick.ai/website/enable-agent-traffic) - The website changes that point agents at your storefront. - [Buy with AI widget](https://zeroclick.ai/website/buy-with-ai-widget) - Give shoppers an on-page handoff to the AI agent they already use. - [SDKs](https://zeroclick.ai/sdks/overview) - Seller SDKs for TypeScript, Python, Go, and Ruby. - [API reference](https://zeroclick.ai/api-reference/introduction) - Manage sellers, services, meters, plans, usage, and analytics with the REST API. Questions? Email [help@zeroclick.ai](mailto:help@zeroclick.ai).