> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zeroclick.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# What is ZeroClick?

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

<img className="block dark:hidden" src="https://mintcdn.com/zeroclickai/-ZjfEQ9Js9R6tXdO/images/hero.png?fit=max&auto=format&n=-ZjfEQ9Js9R6tXdO&q=85&s=c7d3cd2453ff38cd7cdc51e481e389bb" alt="A dotted globe with agent activity lights converging on ZeroClick storefronts" noZoom width="2400" height="840" data-path="images/hero.png" />

<img className="hidden dark:block" src="https://mintcdn.com/zeroclickai/atVegZNmCW6T8tdU/images/hero-globe-dark.svg?fit=max&auto=format&n=atVegZNmCW6T8tdU&q=85&s=c1c82b88524b0dccf13a02972e7fbe79" alt="A dotted globe with agent activity lights converging on ZeroClick storefronts" noZoom width="1200" height="420" data-path="images/hero-globe-dark.svg" />

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 with [x402](https://www.x402.org) or [MPP](https://mpp.dev), 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.

## How it works

Every seller gets a hosted pay URL, such as `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.

<Steps>
  <Step title="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>

  <Step title="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 shows up without a wallet, ZeroClick creates one on the spot.
  </Step>

  <Step title="Your API serves the request">
    Your API verifies the request signature, checks the agent's allowance, and returns the result.
  </Step>

  <Step title="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.
  </Step>
</Steps>

The [how ZeroClick works](/concepts/how-zeroclick-works) page walks 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](/sdks/overview) for TypeScript, Python, and Go implement the guard; the [REST walkthrough](/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

<Columns cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Serve your first paid agent request in about ten minutes.
  </Card>

  <Card title="Integrate your API" icon="plug" href="/integrate/overview">
    The integration contract: verify, check allowance, serve, settle usage.
  </Card>

  <Card title="Enable agent traffic" icon="magnet" href="/website/enable-agent-traffic">
    The website changes that point agents at your storefront.
  </Card>

  <Card title="SDKs" icon="package" href="/sdks/overview">
    Seller SDKs for TypeScript, Python, and Go.
  </Card>

  <Card title="API reference" icon="code" href="/api-reference/introduction">
    Manage sellers, services, meters, plans, usage, and analytics with the REST API.
  </Card>
</Columns>

Questions? Email [help@zeroclick.ai](mailto:help@zeroclick.ai).