---
title: "Tempo × ZeroClick: Integrating MPP to help businesses sell to agents | ZeroClick Blog"
url: https://zeroclick.ai/blog/tempo-partnering-to-help-businesses-sell-to-agents-with-mpp
fetched_at: 2026-11-18T06:16:15.158Z
---

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

# Tempo × ZeroClick: Integrating MPP to Help Businesses Sell to Agents

**Published:** September 21, 2026 · 6 min read · Collaboration
**Author:** [Michael Ludden](https://x.com/michael_ludden), Head of Marketing

---

ZeroClick is announcing a collaboration with [Tempo](https://tempo.xyz), the payments-first blockchain that co-authored MPP with Stripe. Together, they are bringing the next wave of businesses online to sell to AI agents.

The Machine Payments Protocol (MPP) gives AI agents a way to pay for web services, APIs, and digital resources without human intervention or traditional checkouts. Businesses are now selling to those agents through Agent Storefronts powered by ZeroClick: market data, image tools, GTM enrichment, specialized inference, and more, priced per request and settled in under a second. Every storefront accepts MPP. Every MPP payment settles on Tempo.

Agents are already visiting websites. Give them a way to pay, and agent traffic becomes agent customers. That is the core of this collaboration.

---

## The Protocol and the Rail

[MPP](https://mpp.dev) is an open standard for machine-to-machine payments. Stripe and Tempo co-authored it and released it in March 2026.

How a payment works:

1. An agent requests a paid resource.
2. The service responds with a 402 and a payment challenge.
3. The agent signs a credential with its wallet and retries with the credential attached.
4. The service verifies the credential and returns the result.

The Payment authentication scheme has been submitted to the IETF standards track. The protocol is agnostic about how money moves. Visa, Stripe, and Lightspark have each extended it to their own rails.

MPP defines two payment types:

- **Charge:** A one-time payment. This is the shape of a standard API call.
- **Session:** Opens once, meters usage through signed vouchers exchanged off-chain, and settles once at the end.

Tempo is where MPP's stablecoin payments settle. It is a Layer 1 blockchain built for payments:

- Blocks finalize in about 0.6 seconds with no re-orgs.
- Fees are paid in USD stablecoins, not a volatile gas token.
- A standard transfer costs under one cent.
- Dedicated payment lanes keep fees flat under load.

Tempo Mainnet went live in March 2026, with design input from Visa, Mastercard, Deutsche Bank, Shopify, Nubank, and Revolut. Its validators include Stripe, Visa, MoneyGram, and Zodia Custody by Standard Chartered. Every Agent Storefront powered by ZeroClick settles MPP payments on Tempo.

---

## What the Collaboration Does

Stripe and Tempo wrote the protocol. ZeroClick helps businesses use it.

Every Agent Storefront ZeroClick builds supports MPP from day one:

- A machine-readable catalog with live per-request prices
- A priced 402 response on every unpaid call
- Settlement on Tempo
- Revenue that lands directly in the seller's Stripe account in fiat or USDC

Card payments also arrive over MPP via Shared Payment Tokens (SPTs).

Every business ZeroClick brings online is another service that agents can pay for over MPP. ZeroClick and Tempo are working together to grow the set of businesses that can sell to agents over MPP.

For sellers, the practical meaning is this: the rail under your storefront was authored by two experienced names in payments, has been validated by companies like Visa and MoneyGram, and is becoming a standard for agentic payments.

---

## Charging Up to a Maximum, on Sessions

Most of what agents buy has a fixed price. A fixed price is a one-shot MPP charge.

Some work cannot be priced before it runs. A model call metered on output tokens is one example. ZeroClick lets sellers price that work as a ceiling. That is where MPP sessions on Tempo are useful.

How a session works:

1. The agent funds a session up to the ceiling and signs a single voucher.
2. ZeroClick closes the session at the actual amount once the work is delivered.
3. The escrow refunds the difference.

If the close fails, the agent can force-close the session after the on-chain grace period. Escrowed funds are never stranded. A failed delivery debits nothing.

Agents get certainty when buying work of unknown size. Sellers get paid for exactly what they delivered.

---

## What Agents Are Buying over MPP Today

Agents are already making purchases on ZeroClick-powered storefronts. They are buying:

- Market data
- Image generations
- GTM enrichment
- Specialized inference
- Publisher content
- Commerce data

Most purchases are priced in cents and settle near-instantly. These storefronts are listed on agent indexes including [zero.xyz](https://zero.xyz/), and on each seller's own domain, with live prices and catalogs at `/llms.txt`.

---

## How Selling over MPP Works

If you run a business with something agents may want to buy, the process is:

1. Contact ZeroClick to build your Agent Storefront. The storefront includes machine-readable listings of your services, documentation, and live prices.
2. Agents discover your storefront through your existing domain or an agent index.
3. An agent calls a service, receives a 402 with the price, pays over MPP, and gets the result.

On your side, you add one thing: a billing guard on your API. It verifies each request came through ZeroClick, checks the buyer's allowance, does the work, and reports usage. There are no keys to issue and no auth model to change. Revenue settles directly in your Stripe account.

ZeroClick registers your storefront across major agent indexes including [mppscan](https://mppscan.xyz) and [zero.xyz](https://zero.xyz/), so your services appear wherever agents search.

---

## Get Started

- Learn more about Tempo: [tempo.xyz](https://tempo.xyz/)
- Learn more about the Machine Payments Protocol: [mpp.dev](https://mpp.dev)
- Get a demo to sell your product to AI agents: [zeroclick.ai](https://zeroclick.ai/getlisted?utm_source=blog)
- Read the docs: [docs.zeroclick.ai](https://docs.zeroclick.ai)
- Background on why ZeroClick was built: [It's time to sell to agents](https://zeroclick.ai/blog/its-time-to-sell-to-agents)
