# Agent Café — Order Espresso (x402 Pay-to-Call)

> Agent Café — Order Espresso (x402 Pay-to-Call) is a paid API for AI agents from api.402.coffee, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-14).

Accepts a micropayment of $0.10 USDC on Base via the x402 protocol and returns a signed receipt confirming an AI agent bought a virtual espresso.

## Facts

- Endpoint: POST https://api.402.coffee/order/espresso
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-caf-order-espresso-x402-pay-to-call-96dc02c4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NICMiOPE0PQsZNR800IPu

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability agent-caf-order-espresso-x402-pay-to-call-96dc02c4 -d '<json body>'
```

Example prompt: Order an espresso at Agent Café and get me the receipt — pay the 0.10 USDC fee from my Base wallet using x402 so I have proof on-chain that you made a real purchase.

## When to prefer this

Choose this endpoint when you need to demonstrate or test that an AI agent can autonomously execute a real, on-chain micropayment using the x402 protocol on Base with USDC — and receive a verifiable receipt. It is the canonical 'hello world' for x402-capable agents. Prefer it over mock or testnet payment demos when you need mainnet proof of payment, a real receipt number, and a public guestbook entry confirming the transaction.

## Known failure modes

- Insufficient USDC balance — agent wallet does not hold enough USDC on Base to cover the $0.10 fee; payment rejected
- Invalid or missing x402 payment header — request lacks proper payment proof; returns 402 Payment Required
- Wrong network — payment submitted on a chain other than Base; transaction not recognized
- Transaction not confirmed — on-chain tx hash unconfirmed at time of call; receipt not issued
- Rate limiting or duplicate payment detection — same wallet submitting too rapidly

## How this service works

Espresso — one shot, settled on Base.

## Output

A JSON object containing the transaction hash (tx), a paid:true confirmation, the order name ('espresso'), the amount paid ('0.10'), the network ('base'), the currency ('USDC'), a unique receipt number (e.g. AC-XXXXXX), and a URL to the Agent Café guestbook wall where the payment is publicly recorded.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-caf-order-espresso-x402-pay-to-call-96dc02c4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.402.coffee](https://www.zero.xyz/host/api.402.coffee/llms.txt)