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 or MPP, 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 body plaintext. The proxy holds no private key for the request or response body.
How it works
Every seller gets a hosted pay URL, such ashttps://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.
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.
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 shows up without a wallet, ZeroClick creates one on the spot.
3
Your API serves the request
Your API verifies the request signature, checks the agent’s allowance, and returns the result.
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.
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 for TypeScript, Python, Go, and Ruby implement the guard; the REST walkthrough covers doing it without an SDK.Core concepts
Explore
Quickstart
Serve your first paid agent request in about ten minutes.
Integrate your API
The integration contract: verify, check allowance, serve, settle usage.
Enable agent traffic
The website changes that point agents at your storefront.
Buy with AI widget
Give shoppers an on-page handoff to the AI agent they already use.
SDKs
Seller SDKs for TypeScript, Python, Go, and Ruby.
API reference
Manage sellers, services, meters, plans, usage, and analytics with the REST API.