--- title: "What makes a product agent-purchasable? | ZeroClick" url: https://zeroclick.ai/resources/what-makes-a-product-agent-purchasable fetched_at: 2026-09-30T00:03:23.117Z --- # 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/7clndwyarud3/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/7clndwyarud3/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/7clndwyarud3/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/7clndwyarud3/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/7clndwyarud3/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/7clndwyarud3/SKILL.md) or [full direct workflow reference](https://agents.zeroclick.ai/zcj/7clndwyarud3/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 Makes a Product Agent-Purchasable? [ZeroClick Team](https://x.com/zeroclick) · September 15, 2026 · 4 min read · Packaging and pricing A product is agent-purchasable when an authorized agent can understand an offer, obtain the required access, and receive a usable result. Accepting a machine payment is one part of that path. A product can accept payment and still leave the buyer unable to finish the task. The useful unit is a concrete purchase: one search, one generated file, one enrichment result, or one plan that provisions working access. --- ## Contents - [Start at the page the buyer actually reaches](#start-at-the-page-the-buyer-actually-reaches) - [Make the offer specific enough to evaluate](#make-the-offer-specific-enough-to-evaluate) - [Separate payment, permission, and ownership](#separate-payment-permission-and-ownership) - [Deliver something the buyer can use](#deliver-something-the-buyer-can-use) - [Make recovery part of the product](#make-recovery-part-of-the-product) - [Where x402 and MPP fit](#where-x402-and-mpp-fit) --- ## Start at the page the buyer actually reaches An agent may arrive through an existing article or API guide, not your homepage. That page should answer its original question and make the relevant action findable. For example, a guide to comparing product offers can explain the workflow and point to product search. Sending every visitor to an undifferentiated catalog makes the buyer rediscover the connection. ZeroClick's [website guide](https://docs.zeroclick.ai/website/enable-agent-traffic) describes storefront pointers and alternative representations. Which one a client reads depends on that client's capabilities. Do not assume all agents browse or fetch pages identically. ## Make the offer specific enough to evaluate "Access our data" is not enough. Explain the input, output, scope, price, and important exclusions. Consider an illustrative company-enrichment offer: | Question | An answer the seller must supply | |---|---| | What do I provide? | A supported company identifier, such as a domain. | | What do I receive? | The documented company fields, with missing values preserved. | | What does it cost? | The price or allowance consumed by this request. | | What counts as no result? | The documented no-match response, distinct from an outage. | | What happens next? | Use the returned fields; request another operation only when needed. | A buyer should not need to infer whether missing data is an error, an empty result, or permission to invent an answer. The [packaging guide](https://zeroclick.ai/resources/package-agent-services) develops this input-to-output contract. ## Separate payment, permission, and ownership These answer different questions: - **Payment:** Has the required amount been authorized or paid? - **Permission:** May this caller perform this operation within the allowed limits? - **Ownership:** Which person or organization should retain access afterward? A payment credential is not a complete statement of user intent. Similarly, identifying a caller does not automatically connect an account created today to the person returning tomorrow. ZeroClick distinguishes agent credentials from buyer ownership in its [access documentation](https://docs.zeroclick.ai/concepts/agents-and-access). Its [plan policies](https://docs.zeroclick.ai/concepts/plans-and-pricing) determine when verified identity is required. Human approval can be the correct outcome. The product should make the handoff understandable rather than silently fail when the agent lacks authority or a usable payment method. ## Deliver something the buyer can use For an API call, fulfillment is the actual response and its meaning - not the payment confirmation. For a plan purchase, fulfillment may require an account to exist, an API key to be issued, and that key to work. ZeroClick's [API integration](https://docs.zeroclick.ai/integrate/overview) and [account-provisioning integration](https://docs.zeroclick.ai/integrate/stateful-sellers) handle different delivery shapes. Choose the path that matches what you sell. Define a check the buyer can perform. An extracted table should contain the requested fields. An account should permit the promised action. A no-match result should be distinguishable from an unavailable service. ## Make recovery part of the product Test at least a valid result, a valid empty result where applicable, an invalid request, and an interrupted attempt. Ask what the buyer can safely do next. A retry should not accidentally create a second account or an unexplained second charge. An exhausted allowance should be recognizable as a limit, not disguised as missing data. Use the implementation's documented retry and settlement behavior; do not improvise it in the agent prompt. For a company lookup, the buyer should be able to distinguish "company not found" from "service unavailable" and choose a different input or retry accordingly. That ability to continue is part of a usable purchase. ## Where x402 and MPP fit Payment protocols make payment requirements and responses machine-readable. They do not select your offer, validate its usefulness, or guarantee demand. Read [x402 for API sellers](https://zeroclick.ai/resources/x402-for-api-sellers) or [MPP for API sellers](https://zeroclick.ai/resources/mpp-for-api-sellers) to understand the payment layer. Then test the full path from finding the service to using its output. The first milestone should be one complete, bounded customer task. Expand the catalog after that path is clear. --- ## Keep reading 1. [How to package your product into a service an agent can buy](https://zeroclick.ai/resources/package-agent-services) 2. [x402 for API sellers: what it handles and what you still need to build](https://zeroclick.ai/resources/x402-for-api-sellers) 3. [MPP for API sellers: payment methods, sessions, and implementation choices](https://zeroclick.ai/resources/mpp-for-api-sellers) 4. [ZeroClick docs: website / enable agent traffic](https://docs.zeroclick.ai/website/enable-agent-traffic) --- ## More in Packaging and pricing - [How to package your product into a service an agent can buy](https://zeroclick.ai/resources/package-agent-services) - [How to price an API for AI agents](https://zeroclick.ai/resources/price-an-api-for-agents) - [How to choose an integration for selling your API to AI agents](https://zeroclick.ai/resources/choose-a-zeroclick-integration) [All resources](https://zeroclick.ai/resources#packaging-and-pricing)