Chat-native tiny x402 payment flow.

Proof retry confidence

HTTP 402 is expected.

HTTP 402 means the proof paywall is reachable and returning x402 payment requirements. It is not a service outage and it is not revenue.

HTTP 200 only counts after a buyer-controlled x402 client retries this route with an approved payment.

• Buyer approves GET /api/opportunity-check as the route.
• Buyer approves the $0.01 maximum spend.
• Buyer approves Base mainnet x402 on eip155:8453.
• Buyer controls the wallet and chooses whether to retry.
• Buyer expects HTTP 200 JSON only after the paid retry succeeds.

Agent note

Unpaid 402 is expected. If the buyer approves a one-cent proof, retry GET /api/opportunity-check with an x402-capable client, max amount 10000 atomic USDC on eip155:8453, and treat only HTTP 200 as completion.

Do not run unless the buyer wallet is approved for this one-cent proof.
npx [email protected] x402 pay "https://apexscout.ai/api/opportunity-check?src=machine-readable-x402-proof" \
  --max-amount 10000 \
  --json

Proof retry decision

Continue only when the buyer can actually pay.

Continue only if buyer approval, x402 wallet capability, exact route, exact amount, and Base mainnet network all match.

• Buyer has not approved spend.
• Client is a normal browser without x402 payment support.
• Route, amount, or network differs from the receipt.
• The buyer is treating unpaid HTTP 402 as revenue or completion.
• The output will not change the buyer's next action.

Expected outcomes

Normal browser: HTTP 402 JSON with x402 payment requirements.

x402-capable client: HTTP 200 JSON only after buyer-controlled paid retry.

Agent execution packet

Exact one-cent proof for wallet-capable agents.

Give wallet-capable buyer agents the exact one-cent x402 proof retry without adding a new paid route, changing price, or requiring buyer data.

Run with buyer-approved x402 wallet

Wallet-capable buyers can use the exact one-cent proof packet now. ApexScout only exposes the packet; the buyer wallet decides whether to pay.

Do not run unless the buyer wallet is approved for this one-cent proof.
npx [email protected] x402 pay "https://apexscout.ai/api/opportunity-check?src=agent-execution-proof-packet" \
  --max-amount 10000 \
  --json

Execution contract

• Buyer approval required: yes
• x402-capable client required: yes
• Route: /api/opportunity-check
• Max amount: 10000 atomic USDC
• Network: eip155:8453

402 readiness receipt

Unsigned no-spend receipt before any retry.

Unpaid HTTP 402 proves the x402 proof route is reachable and returning payment requirements. It does not prove payment, revenue, endorsement, or buyer approval.

This is an unsigned no-spend readiness receipt, not AP2 proof, not a signed mandate, not a legal or payment receipt, not an endorsement claim, and not trading, investment, tax, legal, lending, or compliance advice.

• Route scoped to GET /api/opportunity-check.
• Amount scoped to $0.01 / 10000 atomic USDC.
• Network scoped to Base mainnet eip155:8453.
• HTTP 402 is expected before payment.
• HTTP 200 is required before paid completion is counted.
• No request body, cookies, session, or wallet connection is required to read this receipt.
• No buyer-level data is exposed by this receipt.
• No automatic payment or paid retry is performed by ApexScout.

Agent decision

Pay only if: The buyer explicitly approves the route, max amount, network, and one retry from a wallet-controlled x402 client.

Stop if: The buyer has not approved spend, the client cannot attach x402 payment, the route or network differs, or HTTP 402 is being treated as a paid completion.

Next no-spend step: Stay on ApexScout proof, action-pack, Scope Check, or Builder surfaces until buyer-controlled payment is intentionally approved.

Sample payload

{
  "subject": "Example API or company",
  "goal": "Decide whether this is worth a deeper review.",
  "buyerType": "buyer-agent",
  "source": "chat-tiny-payment-flow"
}

Unpaid probe

curl -i -X POST "https://apexscout.ai/api/opportunity-check" \
  -H "content-type: application/json" \
  --data '{
  "subject": "Example API or company",
  "goal": "Decide whether this is worth a deeper review.",
  "buyerType": "buyer-agent",
  "source": "chat-tiny-payment-flow"
}'