v2.2.107-audit-builder-recommended-first-action / AgentCore payment handoff

Hand off to x402 payment without guessing the next step.

Give AgentCore-style buyers one safe handoff from discovery or OpenAPI import into ApexScout's no-spend x402 preparation steps before any buyer-controlled payment.

This is a free, no-spend guide. It does not execute payment, manage buyer wallets, or make a paid call.

Buyer approval boundary

  • Buyer wallet and approval stay on the buyer side.
  • The $0.01 route needs a cap of at least $0.01.
  • The $5 audit requires currentProblem and a cap of at least $5.00.
  • Stop after a successful paid response unless there is a new approval.

Route handoff cards

$0.01 / eip155:8453

/api/opportunity-check

Use this first when the buyer wants the cheapest proof that ApexScout's x402 loop works.

Cap: 0.01 · Max: 10000

Required: subject

Start no-spend step · Score safety

$5.00 / eip155:8453

/api/agent-revenue-audit

Use this only after the Builder returns ready_to_pay and the buyer cap is at least $5.00.

Cap: 5.00 · Max: 5000000

Required: serviceName, currentOffer, targetBuyer, currentProblem

Start no-spend step · Score safety

AgentCore-style buyer flow

Step 1 / free

Discover or import ApexScout

/api/agentcore-openapi.json

Load ApexScout's OpenAPI or MCP metadata and choose the intended route.

Step 2 / free

Use the no-spend fit step

/chat-tiny-payment-flow or /agent-revenue-audit-builder

Use the tiny flow for a $0.01 proof path, or the Builder for a valid $5 audit payload.

Step 3 / free

Confirm safety before payment

/buyer-agent-payment-safety

Check required fields, wallet cap, buyer approval, duplicate-payment risk, and metadata safety.

Step 4 / free

Run unpaid 402 preflight

/api/opportunity-check or /api/agent-revenue-audit

Send the same payload without payment first and inspect the returned x402 requirements.

Step 5 / free

Approve buyer-side spend

/agentcore-payments-policy

Require explicit operator approval and a wallet cap that matches the selected route.

Step 6 / buyer-controlled

Retry once with x402 payment

/api/opportunity-check or /api/agent-revenue-audit

Only the buyer-side wallet or payment manager creates the payment proof and retries the request.

Step 7 / free

Stop after paid response

/api/cash-register

If PAYMENT-RESPONSE is already present for the same approved attempt, do not retry automatically.

Command shape only

Do not run unless your wallet cap matches the selected route and your operator approves the spend.

Tiny trust route:
POST https://apexscout.ai/api/opportunity-check
Content-Type: application/json
max amount: 10000
payload includes: {"subject":"...","goal":"...","source":"agentcore-payment-handoff"}

$5 audit route:
POST https://apexscout.ai/api/agent-revenue-audit
Content-Type: application/json
max amount: 5000000
payload includes: {"serviceName":"...","currentOffer":"...","targetBuyer":"...","currentProblem":"...","currentPaymentRail":"base-x402","riskTolerance":"medium","source":"agentcore-payment-handoff"}

Guardrails