---
title: "How to choose an integration for selling your API to AI agents | ZeroClick"
url: https://zeroclick.ai/resources/choose-a-zeroclick-integration
fetched_at: 2026-09-28T01:10:16.818Z
---

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

# How to Choose an Integration for Selling Your API to AI Agents

*ZeroClick Team · September 15, 2026 · 5 min read · Packaging and pricing*

[Resources](https://zeroclick.ai/resources)

---

Start with what the buyer must have after paying. One response, a job result, and a reusable API key require different implementations, even when all three use the same payment method.

For example, a company-data API might sell a single company lookup, a million-row enrichment job, or a monthly account. Calling all three "API access" hides the decisions that determine account ownership, billing, and failure recovery.

## Contents

- [Pick the delivery path before the payment protocol](#pick-the-delivery-path-before-the-payment-protocol)
- [A lookup: keep the contract small](#a-lookup-keep-the-contract-small)
- [A variable response: make the maximum enforceable](#a-variable-response-make-the-maximum-enforceable)
- [A long-running job: separate acceptance from completion](#a-long-running-job-separate-acceptance-from-completion)
- [A standing account: provision access, then issue the key](#a-standing-account-provision-access-then-issue-the-key)
- [Write a one-page integration decision](#write-a-one-page-integration-decision)

## Pick the Delivery Path Before the Payment Protocol

| What the buyer receives | Starting path | The decision you must make |
|---|---|---|
| One bounded API response | Proxied request with a fixed usage quantity | What counts as a delivered result? |
| A response whose size becomes known during execution | Proxied request with a maximum quantity | What bound can your backend actually enforce? |
| A result that finishes after the first response | Asynchronous work and usage reporting | How will the buyer retrieve the result, and how will you reconcile billing? |
| A durable account, subscription, or API key | Stateful seller integration | Which account is updated, and when is it genuinely usable? |
| A demo or negotiated engagement | Explicit human handoff | What can be offered now without implying instant fulfillment? |

For a demo or negotiated engagement, make the next action a contact or approval step. Instant checkout fits an offer that can be fulfilled once the buyer completes its stated requirements.

## A Lookup: Keep the Contract Small

Suppose a buyer supplies a company domain and receives a structured company record. Your offer should state the accepted input, returned fields, geographic coverage, freshness, and behavior when no match exists. Decide whether you charge for an attempted lookup or a returned record; those are different products.

The request integration has four responsibilities: verify the forwarded request, check the allowance, perform the work, and report usage. A signature alone does not mean the request is paid: an unpaid pricing probe can also be signed. Your backend must wait for the allowance decision before doing billable work.

Use the [service-packaging guide](https://zeroclick.ai/resources/package-agent-services) to write the offer and the [integration overview](https://docs.zeroclick.ai/integrate/overview) to implement it. Keep your existing direct API route if you need it; distinguish the ZeroClick trust boundary from the authentication used by your existing customers.

## A Variable Response: Make the Maximum Enforceable

A document extractor cannot always know the number of processed pages before opening a file. A declared maximum is useful only if the service can stop, reject, or return a defined partial result at that bound.

Choose a maximum quantity, check the corresponding allowance, and settle the actual quantity. Do not use the maximum as a fixed charge. ZeroClick documents reserve-and-settle payment paths for ceiling-priced calls; a client that can pay a fixed price may not support the required reserve path.

The [pricing guide](https://zeroclick.ai/resources/price-an-api-for-agents) helps define the unit and the customer-facing policy. The [ceiling-charge documentation](https://docs.zeroclick.ai/integrate/charge-up-to-a-maximum) supplies the wire contract.

## A Long-Running Job: Separate Acceptance from Completion

An enrichment job that returns a job ID has acknowledged work, not necessarily delivered enriched data. Specify how the buyer polls or receives completion, when results expire, and what cancellation means. An HTTP `202` alone cannot communicate all of that.

ZeroClick supports asynchronous usage reports for work that outlives the response. Reports need deterministic idempotency keys and seller-managed retries. This does not remove the need for a durable job record in your product, and does not guarantee that a later report will succeed after an access period or balance changes.

Before choosing this path, walk through a worker restart, a completed job whose usage report fails, and a buyer retry after a timeout. See [failure and retry design](https://zeroclick.ai/resources/handle-agent-purchase-failures).

## A Standing Account: Provision Access, Then Issue the Key

If the buyer needs a key to use your service repeatedly, treat the purchase as an account update. The stateful integration sends the desired account state to your backend and separately requests a seller-issued API key. The buyer then calls your API directly.

Arrange the storefront-level setup with ZeroClick and select a non-pay-as-you-go plan. Map the purchased access to your customer records, including existing users who may already hold a subscription.

The [account-provisioning guide](https://zeroclick.ai/resources/sell-accounts-and-api-keys) works through duplicates, delayed setup, and renewals. Read [identity and access](https://zeroclick.ai/resources/identity-and-access-for-agents) before choosing which identifier owns the account.

## Write a One-Page Integration Decision

For the company-data product, the same underlying dataset can support these three illustrative decisions:

| Offer | Delivery and billing decision | Check before implementation |
|---|---|---|
| Look up one company | Proxied response; fixed price for one completed lookup | A valid no-match response is included in the stated lookup price |
| Enrich a large file | Durable job and result retrieval; report completed usage | A retry finds the same job; the balance and access model covers delayed work |
| Buy recurring API access | Stateful account and seller-issued key | The key works, renewal updates the same account, and expired access is refused |

Select one row, write the input and output limits, and name the system that owns the request, job, or account. Those decisions give engineering a delivery contract rather than just a protocol preference.

Only then choose the buyer payment paths. The seller guides to [x402](https://zeroclick.ai/resources/x402-for-api-sellers) and [MPP](https://zeroclick.ai/resources/mpp-for-api-sellers) explain those choices without treating the protocol as a replacement for delivery design.

Once a complete purchase can be delivered and reconciled, use the [pilot measurement guide](https://zeroclick.ai/resources/measure-an-agent-commerce-pilot) to decide what to learn from real buyers.

## Keep Reading

1. [How to package your product into a service an agent can buy](https://zeroclick.ai/resources/package-agent-services)
2. [How to price an API for AI agents](https://zeroclick.ai/resources/price-an-api-for-agents)
3. [How to handle failed AI agent purchases and retries](https://zeroclick.ai/resources/handle-agent-purchase-failures)
4. [How to sell accounts and API keys to AI agents](https://zeroclick.ai/resources/sell-accounts-and-api-keys)
5. [ZeroClick docs: integrate / overview](https://docs.zeroclick.ai/integrate/overview)

---

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