---
title: "Agent readiness"
url: https://zeroclick.ai/readiness
fetched_at: 2026-11-22T14:13:24.511Z
---

# 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/ju6zmbfar53n/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/ju6zmbfar53n/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/ju6zmbfar53n/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/ju6zmbfar53n/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. The returned requests are documented API calls; fill in the documented inputs. Check usage cost AND minimum cash required against the budget. For needs_input, supply only missing facts. Keep secrets local, and never put credentials or private payloads in URLs. Unknown does not mean absent.

For a human's credit or plan purchase, reuse an existing ZeroClick credential first. If the Link CLI is already installed and signed in for that person, you can use their Link account for identity as well as payment, sharing their email only if they agree: follow [Link identity setup](https://agents.zeroclick.ai/zcj/ju6zmbfar53n/auth.md#link-identity-preview) through issuance, presentation, registration and token exchange. Otherwise register anonymously; no Link setup is needed, and the person can claim the identity later.

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/ju6zmbfar53n/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/ju6zmbfar53n/SKILL.md) or [full direct workflow reference](https://agents.zeroclick.ai/zcj/ju6zmbfar53n/llms-full.txt). Confirm missing request details from seller documentation, stay within the existing catalog and what your user asked for, 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`.

# Agent readiness

> Score how ready a storefront or API is to sell to AI agents. Point it at a
> domain and it probes what an agent would actually encounter — then runs a real
> buying agent against the site and grades what happened.

This is a diagnostic, not a product you buy. Every stored report is readable
with no credential at all, as are the rubric, this file and the verification
recipe; starting a scan, minting a share link and listing a domain's runs need
one. The exact boundary and handshake are published at https://zeroclick.ai/readiness/auth.md, which is
readable without one.

## What it measures

Five weighted pillars: can an agent get in (access), understand what is for sale
(legibility), pay and provision without a human (transactability), decide the
site is safe to transact with (trust), and actually finish the job (outcome).

The full rubric — every check, its points, and what it looks for — is published
and generated from the same file the scorer loads, so it cannot drift from the
implementation.

- [The rubric as markdown](https://zeroclick.ai/readiness/spec.md): every scored check, ordered by how much it moves the grade — start here if you want to know what to implement
- [Machine-readable rubric](https://zeroclick.ai/readiness/api/v1/spec): the same content as JSON
- [OpenAPI description](https://zeroclick.ai/readiness/openapi.json): every endpoint below, with its query parameters and response content type
- [How to authenticate](https://zeroclick.ai/readiness/auth.md): the accepted credentials, and everything readable without one
- [How to verify a run](https://zeroclick.ai/readiness/verify.md): the signature and hash-chain mechanics, including the canonicalization rule

## API

Every route below is free. The only route that charges is `POST /api/v1/scans`,
reached through the signed ZeroClick payment proxy (see /auth.md). Slow work
streams as Server-Sent Events.

- `GET /api/v1/scan/stream?url=<domain>` — static probes, streamed as Server-Sent
  Events. Returns a scored report in seconds. Read-only: it fetches published
  surfaces and records payment hints as diagnostics; it never signs or settles
  anything.
- `GET /api/v1/agent?url=<domain>` — the deep scan. Runs a real buying agent
  against the site, grades the transcript into the outcome pillar, asks a
  three-vendor trust panel whether it would proceed, and records a correlated
  402 when the agent selects and probes a documented purchase operation. The
  current arm cannot authorize payment, retry with payment or verify delivery.
  Slow and expensive; streamed. Every scan collects fresh — there is no
  observation cache, so `&refresh=1` is accepted and does nothing.
  `report.provenance` is the authoritative record of what each stage cost.
  The stream's final `report` event carries `runId` and `reportUrl`:
  **use `reportUrl`** — it is the public, shareable permalink. A scan is
  started on the operator surface (a tailnet host), so a URL built from
  wherever you connected is one only the tailnet can open.
- `GET /api/v1/spec` — the published rubric as JSON. Public.
- `GET /api/v1/rubric` — the rubric version, config hash and pillar weights. Public.
- `GET /api/v1/runs/<id>` — a stored report, immutable, with the rubric version
  and config hash that produced it, plus `reportUrl`: the public permalink to
  share. Public, as are its `/events`, `/session`, `/judge`, `/frames` and
  `/peers`: the id is the capability.
- `GET /api/v1/runs/<id>/markdown` (also `/r/<id>.md`) — the report as portable
  Markdown, with the evidence chain root. Public.
- `GET /api/v1/domains/<domain>/runs` — the append-only, hash-linked index of
  every stored run for a domain. Credentialed: this one enumerates.

## Reading a score

Scores compare only within one config hash. Changing a weight, a point value or
the set of checks produces a new hash and a new ruler, and two numbers from two
hashes are two different measurements.

Points normalise within a pillar before weighting, so do not sum the points
column across pillars — the heaviest pillar carries the fewest raw points.

A check that could not be evaluated shrinks the denominator rather than scoring
zero. A site is never marked down for evidence the scanner failed to gather.

Reused evidence is still re-scored under today's rubric: a replayed static
report carries the current `rubricVersion` with the ruler it was collected
under beside it as `originRubricVersion`. Evidence is cached; interpretation
never is.
