---
title: "ZeroClick October Product Update: Jev-powered seller agents & more | ZeroClick Blog"
url: https://zeroclick.ai/blog/product-update-october-2026
fetched_at: 2026-11-21T18:24:24.518Z
---

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

# ZeroClick October Product Update: Jev-powered Seller Agents & More

**Brian Luscombe**, Head of Product
October 5, 2026 · 5 min read

---

In the [September product update](https://zeroclick.ai/blog/product-update-september-2026), we covered the optimization work that follows AEO (Answer Engine Optimization). AEO gets agents aware of your service and recommending it in answer engines. After that, a separate body of work drives commercial conversion from the agent actions that follow. That body of work is Agentic Commerce Optimization (ACO).

## 5 Ways Agent Conversions Happen Today

Agent conversion can happen in these ways:

1. A human takes action after seeing a service in an AI answer engine (current state of AEO).
2. Agent-to-human handoff: the agent asks the human to complete a step further down the funnel.
3. The agent asks the human to complete the payment step.
4. The agent asks the human for approval, then makes the purchase itself.
5. The agent fully completes the transaction autonomously.

The first three still look like human transactions, even though cases 2 and 3 are mostly agent-driven. Your agent commerce volume is probably already much higher than you think.

This means any business that sells online needs to answer these questions:

- How many agents are visiting your website?
- What kind of agents are they? (crawlers, bots, chat agents, agents using human browsers, autonomous agents)
- What is their intent?
- If they are trying to complete a task, what tasks are they attempting?
- Do your services or products match their intent?
- Can an agent buy from you?

This looks like a traditional online shopping journey, but it requires a new set of tools to support agent commerce.

## What We Shipped, September 2026

**Support for "Stateful Sellers"** — sellers who offer software more complex than pay-as-you-go tasks can now use ZeroClick. This allows agents to:

- Create stateful accounts attached to an agent identity
- Provision API keys linked to that identity
- Auto-renew subscriptions
- Track stateful balances (for example, how many of 100 monthly credits have been used)

In summary: if a human can sign up and use your SaaS service, agents can now do the same through ZeroClick stateful seller support.

**Agent Discovery portal** — a new section in the ZeroClick dashboard. It shows partners their agent Readiness Score and concrete steps to improve agent commerce readiness.

- Run a free agent readiness report at [zeroclick.ai/readiness](https://zeroclick.ai/readiness).
- Get the full version with competitor analysis by asking your agent to buy it at [agents.zeroclick.ai](https://agents.zeroclick.ai/zcj/z3uyhjgdg0do/).

**Fully revamped Agent Traffic Analytics** — answers the questions above: agent types, agent journeys, intent, and conversion metrics.

**100 Agent Eval Tool** — an internal tool that configures hundreds of agents to fully test any flow on any partner site. For example, you can compare how a Muse agent with Stripe Link Wallet access performs against Claude Code with a crypto wallet, across hundreds of agent variations.

**Upgraded agent storefronts** with new **Jev-powered seller agents**. These turn a buyer agent's goal, budget, and available payment methods into concrete purchasing instructions. By reducing documentation searches and trial-and-error requests, they help buyer agents complete transactions faster, use fewer tokens, and spend less on inference. In testing, they cut up to 27% of token use on Claude Code and 9% on Codex.

Storefronts are also more agent-legible: OpenAPI specs are now split into per-service specs with pagination and fuzzy search, plus a Zero skill update.

## Become a Customer

If you are not yet a ZeroClick partner, ask your agent to "book me a demo at [agents.zeroclick.ai](https://agents.zeroclick.ai/zcj/z3uyhjgdg0do/)" to get started.

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