---
title: "ZeroClick - Sell to AI Agents"
url: https://zeroclick.ai/
fetched_at: 2026-10-01T11:59:28.985Z
---

# 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/3aq0qm5pjy31/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/3aq0qm5pjy31/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/3aq0qm5pjy31/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/3aq0qm5pjy31/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/3aq0qm5pjy31/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/3aq0qm5pjy31/SKILL.md) or [full direct workflow reference](https://agents.zeroclick.ai/zcj/3aq0qm5pjy31/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`.

# Sell Your Product to AI Agents

[Get started](https://zeroclick.ai/get-demo) | [Sign In](https://dashboard.zeroclick.io/)

> ZeroClick raises $55M — [Learn more](https://zeroclick.ai/blog/its-time-to-sell-to-agents)

The next visitor to your site will be an AI agent. Make them your next customer.

---

## Agentic Commerce Is Here. Are You Ready?

- **100M+** transactions on x402 and MPP
- **$1.5T** projected agentic commerce volume
- **>57%** of web traffic is now agentic

ZeroClick turns any API or offering into an agent-purchasable service. It includes x402 and MPP support, a machine-readable storefront, and agent transaction analytics.

---

## Everything You Need to Sell to Agents

### Set up your agent storefront. Get discovered.

ZeroClick turns your product into an agent-purchasable service with x402 and MPP support, a machine-readable storefront, agent transaction analytics, and more.

- **Simple implementation.** One SDK that works with your existing API.
- **Stripe Connect enabled.** Money lands directly in your account, with full support for fiat and USDC.
- **You are in control.** Manage pricing, analytics, and more from the ZeroClick dashboard.

[Get started](https://zeroclick.ai/get-demo) | [Read the docs](https://docs.zeroclick.ai)

---

### Agents find and purchase your service.

Agents navigate your storefront, pay via x402 or MPP, and money lands directly in your Stripe account. ZeroClick handles all transaction tracking and verification.

- **Discoverability.** ZeroClick registers your services on all major indexes so agents can find you.
- **Tracking and verification.** Agents are given IDs so you can track customer journeys and prevent abuse.
- **Help agents pay.** If an agent arrives without a wallet, ZeroClick can create one on the spot.

[Get started](https://zeroclick.ai/get-demo) | [Read the docs](https://docs.zeroclick.ai)

---

### Track every agent sale.

Transaction-level tracking shows where agents come from and what they are buying. See agents' preferred payment methods, conversion rates across your services, and more.

- **Agent origins.** See which platforms and models your buyers come from.
- **Payment insights.** Split every sale across x402, MPP, USDC, and fiat.
- **Conversion analytics.** Measure conversion rates for every service you sell.

[Get started](https://zeroclick.ai/get-demo) | [Read the docs](https://docs.zeroclick.ai)

---

### Built for startups and enterprises.

Security, roles, pricing controls, and live analytics for your entire team. Every agent is verified, every call is logged, and revenue lands in your connected Stripe account.

**Sample dashboard figures:**

| Metric | Value | Change vs. prior 30 days |
|---|---|---|
| Agent traffic | 6.8M | +24% |
| Agent transactions | 4.2M | +32% |
| Revenue (USDC) | $182K | +41% |
| Success rate | 99.1% | 4.2M payment attempts |

**How agents paid (wallet source breakdown):**

- New wallet: 840K (20%)
- Zero wallet: 1.3M (31%)
- External wallet: 2.1M (49%)

**Top services by revenue:**

- RelayMail — 2.3M transactions — $96K
- PixelForge — 1.1M transactions — $52K
- SiftLabs — 640K transactions — $21K

Additional features:
- SOC 2 Type II in progress, plus SSO and SAML
- Roles and permissions for your whole team
- Live analytics for every agent, service, and payment

[Get started](https://zeroclick.ai/get-demo) | [Read the docs](https://docs.zeroclick.ai)

---

## Questions Sellers Ask

[Browse all 162 FAQs](https://zeroclick.ai/faq)

### What is ZeroClick?

ZeroClick lets AI agents buy from you. It puts a hosted, machine-readable Agent Storefront in front of your existing API, dataset, or digital service. Agents can find it, pay with x402, MPP, or a card, and use it. ZeroClick forwards each paid request to your API, signed, and revenue settles to your connected Stripe account.

Agents read your storefront's live catalog and prices at a pay URL — either a subdomain you own or the default one ZeroClick hosts — then pay per request or buy a plan. You keep your API, your pricing, and your customer relationship. ZeroClick operates the agent-facing payment, identity, and proxy layer in front of it. You add one thing to your API: a billing guard. The billing guard verifies ZeroClick's signature, checks the agent's allowance, does the work, and reports what was used.

Read the overview at [docs.zeroclick.ai](https://docs.zeroclick.ai/), or [get started](https://zeroclick.ai/get-demo) and the team will build your storefront with you.

---

### Do I need to build a new API or change my existing one?

No. ZeroClick runs as a transparent paid proxy in front of your existing API. An agent sends the same request it would send you. ZeroClick prices it, collects payment, and forwards it signed. The only change on your side is a small billing guard that verifies that signature, checks the buyer's allowance, serves the request, and reports usage.

With an official SDK (TypeScript, Python, Go, or Ruby) the guard is one call plus one usage helper. Without an SDK it is plain HTTP: two API calls, one signature check, and three fixed response bodies. Your endpoint logic, authentication, and human-facing billing stay as they are. Requests forwarded by ZeroClick carry no customer API key, only ZeroClick's signature.

If what you sell is an account, subscription, or API key rather than a per-call API, that is a separate, additive integration documented at [Sell accounts and API keys](https://docs.zeroclick.ai/integrate/stateful-sellers). Today ZeroClick sets it up with you.

---

### How long does it take to go live?

ZeroClick builds your storefront from your API reference and pricing. Most partners finish their own implementation steps in under a day. End-to-end timelines vary when a backend needs rework.

Your side is four dashboard wizard steps: custom domain, billing guard, agent traffic, and Stripe onboarding. Once your guard responds correctly, ZeroClick verifies it and makes the first purchases.

The docs quickstart targets a first paid agent request in about ten minutes once your store is configured. ActionLayer, a live seller, says its side of the integration took a day. Timelines stretch when a backend needs rework, for example unusual routing or products that provision accounts.

The Agent Storefront stays closed to orders until the verification check confirms your guard answers with a priced 402. To begin, [book a walkthrough](https://zeroclick.ai/get-demo).

---

### What can I sell through ZeroClick?

Anything delivered over an API that an agent can pay for per use or per plan: data and enrichment lookups, market and publisher data, image generation and model inference, commerce data, real-world tasks, and features of your software. Each is a service with one or more meters, priced pay-as-you-go, by credit, or by subscription.

A meter is a billable measurement within a service, such as requests or output tokens. If a purchase creates something that lasts — an account, an API key, a subscription, or a credit balance — ZeroClick sells that too. You build one HTTPS endpoint that provisions the account and mints the key. ZeroClick hands the key to the buyer without ever storing it.

Free actions run on the same storefront as $0 transactions served to an identified agent: booking a demo, capturing a lead, delivering a white paper, or registering for a webinar.

Details: [Sell accounts and API keys](https://docs.zeroclick.ai/integrate/stateful-sellers).

---

### How much does ZeroClick cost?

- **Setup fee:** $0
- **Monthly platform fee:** $0
- **Revenue share:** 5% of agent-transaction revenue that runs through your ZeroClick storefront, month to month with 30 days' notice

ZeroClick earns only when AI agents buy from you. You set and keep control of your own prices. Revenue from your existing channels is untouched.

The 5% share applies only to agent purchases made through your storefront. Agent payments settle to your connected Stripe account. ZeroClick invoices the 5% monthly against the agent transaction volume shown in your dashboard, so you can reconcile the fee against your own Stripe records.

Setup is done mostly by ZeroClick: the team builds your Agent Storefront from your API reference and pricing. Your side is a thin billing guard, the website snippets, and Stripe onboarding. Terms are set out in a short agreement signed during onboarding. To talk it through, [get started](https://zeroclick.ai/get-demo).

---

### How do AI agents pay, and how do I get paid?

Agents pay per request, or buy credits or a subscription, using:

- USDC over x402 (on Base)
- MPP, the Machine Payments Protocol (on Tempo)
- Card as shared payment tokens over MPP

You get paid in fiat. Revenue settles to the bank account you add during Stripe onboarding. You never run a crypto wallet.

Each paid call is two round trips. The agent's first request gets one priced HTTP 402 with the exact amount. The agent pays and retries. ZeroClick forwards the signed request to your API. An agent without a payment method can set one up on the spot, or hand its human a checkout page hosted by Stripe. Card charges carry a $0.50 minimum, so cards suit credits and plans.

A failed delivery debits nothing on either rail and refunds a card payment in full automatically. No pre-existing Stripe account is required. Which rails you get depends on where your business is established. See [supported countries](https://docs.zeroclick.ai/resources/supported-countries).

---

### Are AI agents actually buying things today?

Yes, and the numbers are public. ZeroClick's AI Purchase Trends page tracks settled agent payments on the x402 and MPP rails from on-chain data. It shows total USDC settled, settled transactions, and unique buyer wallets over the trailing 30 days against the prior 30. It refreshes daily. Read the current figures at [zeroclick.ai/trends](https://zeroclick.ai/trends).

The same page shows Cloudflare Radar's automated-versus-human traffic split for the last 30 days, refreshed hourly, plus published SparkToro, G2, and Adobe findings on searches ending without a click, B2B buyers using AI during research, and how AI-referred visits convert.

Agents buy small per-call services. Live ZeroClick storefronts sell publisher data, commerce data, market data, B2B data, AI image tools, specialized inference, and real-world tasks, with pay-per-request pricing that starts at one cent.

The market is early. ZeroClick does not guarantee any seller revenue. The case for going live now is that a storefront costs nothing until agents buy, and ZeroClick makes the first purchases itself as your first agent customer.

---

### How do AI agents find my storefront?

AI agents find a ZeroClick storefront three ways:

1. **Your website routes visiting agents to it** through the Agent Magnet: head tags, an agent callout, an entry in your llms.txt, markdown for agent fetchers, a Link header, and a badge.
2. **The storefront publishes machine-readable files** that agents read directly.
3. **ZeroClick lists it on agent indexes** such as x402scan and mppscan.

Agents read your pages as raw HTML without running JavaScript. Each Agent Magnet signal catches an agent class the others cannot reach: raw HTTP clients find llms.txt and the Link header; markdown-converting fetchers see the negotiated markdown and the callout text; DOM-parsing agents read the head tags. Each pointer is stamped so your storefront records which one routed each agent.

ZeroClick handles index listings once your storefront is live: x402scan, mppscan, agentic.market (which indexes services from on-chain activity once payments settle, with no registration step), and zero.xyz. Run the storefront on a subdomain you own, since listings point at its address and agents click through to a domain they recognize.

Full steps: [enable agent traffic](https://docs.zeroclick.ai/website/enable-agent-traffic).

---

## Turn Agent Traffic into Agent Customers

[Get started](https://zeroclick.ai/get-demo) | [Sign In](https://dashboard.zeroclick.io/)

---

**Resources:** [Product](https://zeroclick.ai/#how-it-works) | [About](https://zeroclick.ai/#about) | [Resources](https://zeroclick.ai/resources) | [Blog](https://zeroclick.ai/blog) | [Trends](https://zeroclick.ai/trends) | [FAQ](https://zeroclick.ai/faq) | [Documentation](https://docs.zeroclick.ai)

**Social:** [X](https://x.com/zeroclick) | [LinkedIn](https://www.linkedin.com/company/zeroclick/)

**Tools:** [Trends](https://zeroclick.ai/trends) | [Readiness test](https://zeroclick.ai/readiness) | [Zero marketplace](https://zero.xyz/)

A product of the People's Internet Experiment. © 2026.

[Privacy Policy](https://zeroclick.ai/legal/privacy-policy) | [Terms of Service](https://zeroclick.ai/legal/terms-of-service) | [Legal](https://zeroclick.ai/legal)
