First paid route
/api/opportunity-check
$0.01 on eip155:8453. Unpaid request should return HTTP 402 JSON before any paid retry.
v2.2.107-audit-builder-recommended-first-action / no-spend buyer-agent 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.
First paid route
/api/opportunity-check$0.01 on eip155:8453. Unpaid request should return HTTP 402 JSON before any paid retry.
Budget cap
Buyer-side clients should cap the tiny payment to the listed amount and stop after one paid response.
Escalation
Use Agent Revenue Audit Builder only when the buyer wants deeper monetization guidance.
Expected flow
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://agent-research-brief-api-production.up.railway.app/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@latest x402 pay "https://agent-research-brief-api-production.up.railway.app/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
Guardrails
Metadata Preflight · Search Fit Lab · x402 proof · MCP Tool Pack · Machine-readable docs