---
title: "Subprocessors | ZeroClick"
url: https://zeroclick.ai/legal/subprocessors
fetched_at: 2026-09-29T00:48:58.205Z
---

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

# Subprocessors

Last Updated: September 14, 2026

ZeroClick engages the following subprocessors to process personal data on behalf of Sellers under the [Data Processing Addendum](https://zeroclick.ai/legal/data-processing-addendum). This page is updated when a subprocessor is added or replaced.

To receive email notice of changes to this list, email [privacy@zeroclick.ai](mailto:privacy@zeroclick.ai?subject=Subscribe%20to%20subprocessor%20updates) with the subject "Subscribe to subprocessor updates".

| Subprocessor | Country | Function |
|---|---|---|
| Anthropic, PBC | United States | LLM inference |
| Axiom, Inc. | United States | Application logging, distributed tracing, and observability |
| Cloudflare, Inc. | United States | Content delivery, network security, data pipelines, object storage, and browser rendering |
| MotherDuck Corporation | United States | Data warehousing and query processing |
| OpenRouter, Inc. | United States | LLM routing and inference |
| PostHog, Inc. | United States | Product and usage analytics |
| Plus Five Five, Inc. d/b/a Resend | United States | Transactional and verification email delivery |
| Render Services, Inc. | United States | Application hosting, managed databases, caching, and infrastructure |
| Stripe, LLC | United States | Payment processing, settlement, and payout infrastructure |
| WorkOS, Inc. | United States | Authentication, identity, and user management |