Prove your agent can pay.

One curl, one payment, one signed receipt. The hello-world of agentic payments: $10 per call, no signup, no API keys.

Your AI agent claims it can pay for things. Prove it. This endpoint speaks the x402 payment protocol: your agent makes a request, receives HTTP 402 Payment Required, pays $10 in USDC, retries with the payment header, and gets back a signed diagnostic report card. It passes, or it tells you exactly which step failed: 402 handling, payment authorization, facilitator verification, on-chain settlement, or delivery.

Try it

# 1. Unauthenticated request returns the 402 challenge with payment requirements
curl -i https://test.sycamore-api.com/api/verify

# 2. Any x402 client handles the rest. Example (Node):
#    npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment } from "@x402/fetch";
const paidFetch = wrapFetchWithPayment(fetch, client);
const res = await paidFetch("https://test.sycamore-api.com/api/verify");
console.log(await res.json());   // your report card

What your ten dollars buy

Field	What it tells you
`steps[]`	Pass/fail for each stage: request received, payment header parsed, payment verified, settlement, response delivered
`latency`	Request-in / response-out timestamps and server processing time
`origin`	Where your request came from (IP geography, approximate distance to server)
`payment`	Payer address, network, amount, nonce echoed from your payment authorization
`headers_echo`	The headers your agent actually sent (sanitized)
`signature`	Ed25519 signature over the report, verify against /pubkey

Settlement proof (the on-chain transaction hash) rides in the base64 X-PAYMENT-RESPONSE header of the same response, per the x402 spec.

Receipts & badge

Crypto payments have no billing email, so receipts are opt-in: append [email protected] (or send an X-Receipt-Email header) and we email you the signed receipt with the transaction hash.

Every verified payment gets a shareable page at /r/<receipt_id> and an embeddable badge, so you can show your agent passed:

Why

Every team building payment-capable agents needs one dumb, reliable, real-money smoke test before pointing their agent at production APIs. This is it. One endpoint, one payment, one definitive answer: your agent is wired correctly, or a precise pointer to the step that broke.