Import ApexScout into AgentCore Payments-style gateways.

Import paths

Paid x402 routes

Recommended import flow

• Inspect /x402-proof.
• Open /chat-tiny-payment-flow for the one-cent chat-native x402 payment path before any spend.
• Review /x402-security-readiness for route binding, replay, duplicate-payment, Solana watch-only, and metadata safety checks.
• Review /bazaar-search-readiness for ApexScout's owned Bazaar search card, route search terms, and MCP compatibility card.
• Load /.well-known/apexscout-monetization-policy.json to classify free, paid x402, and blocked routes before any payment.
• Load /.well-known/apexscout-paid-tools.json to see the paid MCP tool manifest and no-spend preflight order.
• Review /agentcore-payments-buyer-guide for the buyer-controlled AgentCore Payments path before any spend.
• Open /agentcore-payment-handoff to choose the tiny proof flow or $5 Builder path before payment.
• Review /agent-payment-traction-brief for the current no-spend path from online x402 signals to ApexScout-owned buyer steps.
• Read /api/agent-commerce-scenarios to choose between the seven ApexScout money paths without triggering a paid call.
• Generate a free /agent-spend-passport.
• Use /api/agent-spend-passport/prepare as the recommended no-spend preflight before paid routes.
• Use /buyer-agent-payment-safety or /api/buyer-agent-payment-safety/score to catch route, budget, duplicate-payment, metadata, and network issues before spend.
• Run /api/x402-metadata-preflight/check before paid retry when payment metadata includes resource URLs, reason strings, descriptions, or payload previews.
• Import ApexScout as an HTTP API target with three paid x402 routes and free proof/readiness routes.
• Load /api/agentcore-payments-policy or /.well-known/apexscout-spend-policy.json before any paid retry.
• Treat ApexScout as a seller-side x402 service; do not treat this as an AWS, Coinbase, or Stripe endorsement claim.
• Keep buyer wallet connection, end-user authorization, and spend budget controls in the buyer-side platform.
• Run an unpaid POST first and verify HTTP 402 JSON before any paid retry.
• Only retry with x402 payment when the buyer-side agent has explicit authorization and budget.

Passport-first buyer path

• Inspect /x402-proof.
• Generate a free /agent-spend-passport.
• If the Passport recommends the $5 audit, preview /agent-revenue-audit-preview before paying.
• If the Passport recommends the $5 audit, build a valid request at /agent-revenue-audit-builder before paying.
• Run the free /x402-metadata-preflight before any paid retry if the buyer metadata includes a resource URL, payment description, reason string, or payload preview.
• If Passport recommends /api/opportunity-check, use the $0.01 route.
• If Passport recommends /api/agent-revenue-audit, use the $5 route only with approved budget.
• Stop if Passport says stop.

Guardrails

• Seller-side import metadata only
• Zero-contact and inbound-only
• No official AWS, Coinbase, or Stripe endorsement claim
• No AWS wallet integration added by ApexScout
• No automatic buyer spending
• No scraping
• No third-party discovery
• No outreach automation
• No manual messages, posts, DMs, or emails
• No paid upstream calls
• No fake traction
• No buyer-level public data
• No settlement rail change
• No seller wallet change