Intent handoff

You chose: $0.01 x402 proof path

Next: inspect the unpaid 402 challenge. Only retry payment from your own approved x402 wallet if you choose to spend.

No payment happens from this page.

v2.2.159-proof-retry-decision-strip / no-spend buyer-agent flow

Chat-native tiny x402 payment flow.

ApexScout gives buyer agents a small, clean way to prepare a one-cent paid request from chat: inspect proof, check safety, send the unpaid request, then retry with buyer-controlled x402 payment only when approved.

Score payment safety Generate Spend Passport Read JSON flow

x402-capable agent?

Use this only if your client can handle x402 payment requirements. Normal browsers will just see an unpaid 402 response.

Buyer-controlled retry gate

Buyer-controlled proof retry gate

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

Buyer explicitly approves this exact $0.01 proof.
Client can attach x402 payment on Base mainnet eip155:8453.
Route is exactly GET /api/opportunity-check.
Max amount is exactly 10000 atomic USDC.
Buyer understands only HTTP 200 counts as a paid proof completion.

Stop if: Buyer has not approved spend.

Request GET /api/opportunity-check

Method

GET

Route

/api/opportunity-check

Link

/api/opportunity-check?src=chat-tiny-x402-proof-cta

Price

$0.01

Amount

10000 atomic USDC

Network

eip155:8453

Body

No request body required.

Paid success only after buyer-controlled x402 retry returns HTTP 200.

Paid success requires buyer-controlled x402 retry and HTTP 200.

Use this only if your client can handle x402 payment requirements. Normal browsers will just see an unpaid 402 response.

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 awal@2.8.0 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.

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.

First paid route

`/api/opportunity-check`

$0.01 on eip155:8453. Unpaid request should return HTTP 402 JSON before any paid retry.

URL-native proof

`GET /api/opportunity-check`

No request body. This is the same one-cent Opportunity Check paid resource, exposed as a link-native x402 proof.

Budget cap

10000

Buyer-side clients should cap the tiny payment to the listed amount and stop after one paid response.

Escalation

$5 audit builder

Use Agent Revenue Audit Builder only when the buyer wants deeper monetization guidance.

Expected flow

Start with a clear buyer-agent question.
Run no-spend safety and metadata checks first.
Send the same payload unpaid to /api/opportunity-check and inspect the HTTP 402 JSON.
Retry with a buyer-controlled x402 client only when the buyer approves the spend.
ApexScout verifies and settles on Base mainnet x402, then returns HTTP 200 JSON.
For URL-native clients, GET /api/opportunity-check is the one-cent proof link and requires no request body.
Escalate to the $5 Agent Revenue Audit Builder only when monetization guidance is worth the higher spend.

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"
}'

Buyer-side command shape

Do not run unless the buyer wallet is approved for this spend.
npx awal@2.8.0 x402 pay "https://apexscout.ai/api/opportunity-check" \
  -X POST \
  -h '{"Content-Type":"application/json"}' \
  -d '{
  "subject": "Example API or company",
  "goal": "Decide whether this is worth a deeper review.",
  "buyerType": "buyer-agent",
  "source": "chat-tiny-payment-flow"
}' \
  --max-amount 10000 \
  --json

Link-native proof command shape

Do not run unless the buyer wallet is approved for this one-cent proof.
npx awal@2.8.0 x402 pay "https://apexscout.ai/api/opportunity-check" \
  --max-amount 10000 \
  --json

Guardrails

Free page and API only.
No paid call is made by this builder.
No paid upstream service is called.
No wallet custody or automatic spending is added.
No public buyer prompts, wallet histories, raw paid responses, or raw feedback are exposed.
No outreach, posting, DMs, email, scraping, or third-party discovery is recommended.
No revenue outcome is guaranteed.
No third-party tiny-payment product affiliation or endorsement is claimed.
The link-native tiny proof path uses the existing /api/opportunity-check paid resource and does not add a third paid route.

Metadata Preflight · Search Fit Lab · x402 proof · MCP Tool Pack · Machine-readable docs