v2.2.81-brand-asset-integration / readiness-only-no-spend

x402 batch settlement readiness.

ApexScout is batch-settlement aware, but batch settlement is not enabled. Buyers should still start with the free Agent Spend Passport and use the standard buyer-controlled x402 paid retry only when the Passport says it is safe.

Production boundary: ApexScout still uses standard buyer-controlled x402 payment on eip155:8453. Batch settlement is not enabled. Escrow, off-chain vouchers, seller wallet changes, and settlement rail changes are not enabled.

Generate Spend Passport Read JSON Open Agent Payment Alpha Open MCP Tool Pack

Current status

not enabled

Batch settlement is tracked as readiness context only.

Active rail

Base mainnet x402

eip155:8453 remains the live payment network.

First paid route

$0.01

/api/opportunity-check remains the cheapest proof route.

Builder route

$5.00

/api/agent-revenue-audit remains the $5 monetization route.

What changed in x402

x402 batch settlement lets agents use off-chain vouchers and one final settlement instead of settling every API call individually.

CoinbaseDev source and linked detail source

ApexScout interpretation

This is useful future infrastructure for high-volume buyer agents, but ApexScout should not change its live rail until facilitator, seller, privacy, and accounting behavior are explicitly approved.

Publish readiness metadata now, keep the current per-request x402 payment behavior, and use the Agent Spend Passport as the no-spend first step.

Buyer path today

Inspect /x402-proof.
Generate a free /agent-spend-passport.
Use /api/opportunity-check for the $0.01 proof route when the buyer only needs a cheap rail test.
Use /api/agent-revenue-audit for the $5 builder monetization route only with approved budget.
Stop if Passport says stop.

Future evaluation checklist

Confirm the facilitator supports the exact batch settlement shape ApexScout would use.
Define seller-side accounting for vouchers, final settlement, refunds, and failed batch closes.
Keep buyer budget approval outside ApexScout unless explicitly authorized by the buyer.
Keep Cash Register aggregate-only and avoid wallet-level or voucher-level public histories.
Run local and production no-spend checks before any settlement behavior changes.

Guardrails

No paid calls are made by this readiness surface.
No escrow, voucher acceptance, or batch settlement is enabled.
No facilitator-sponsored gas claim is made for ApexScout production traffic.
No settlement rail or seller wallet change is made.
No buyer wallet custody, buyer budget management, or automatic buyer spending is added.
No buyer-level data, full wallet addresses, full payment payloads, voucher histories, or paid response bodies are public.
No revenue, conversion, endorsement, compliance, legal, tax, investment, lending, or trading guarantee is made.
No scraping, posting, DMs, email, outreach, third-party discovery, fake traffic, or fake feedback is added.

Machine-readable snapshot

{
  "name": "ApexScout x402 Batch Settlement Readiness",
  "version": "v2.2.81-brand-asset-integration",
  "mode": "readiness-only-no-spend",
  "liveMode": "zero-contact-inbound-only",
  "sourceSignal": {
    "source": "Coinbase Developer Platform x402 batch settlement update",
    "sourceUrl": "https://x.com/CoinbaseDev/status/2054241284651676074",
    "detailUrl": "https://x.com/Jnix2007/status/2054233052872872194",
    "observedCapability": "x402 batch settlement lets agents use off-chain vouchers and one final settlement instead of settling every API call individually.",
    "apexScoutInterpretation": "This is useful future infrastructure for high-volume buyer agents, but ApexScout should not change its live rail until facilitator, seller, privacy, and accounting behavior are explicitly approved."
  },
  "routes": {
    "page": "https://apexscout.ai/x402-batch-settlement",
    "api": "https://apexscout.ai/api/x402-batch-settlement",
    "agentPaymentAlpha": "https://apexscout.ai/agent-payment-alpha",
    "agentPaymentAlphaApi": "https://apexscout.ai/api/agent-payment-alpha",
    "agentSpendPassport": "https://apexscout.ai/agent-spend-passport",
    "agentSpendPassportPrepareApi": "https://apexscout.ai/api/agent-spend-passport/prepare",
    "mcpToolPack": "https://apexscout.ai/mcp-tool-pack",
    "mcpToolPackApi": "https://apexscout.ai/api/mcp-tool-pack",
    "docsJson": "https://apexscout.ai/docs.json",
    "cashRegister": "https://apexscout.ai/api/cash-register"
  },
  "currentProductionBoundary": {
    "activeRail": "Base mainnet x402",
    "network": "eip155:8453",
    "baseX402Active": true,
    "facilitator": "https://api.cdp.coinbase.com/platform/v2/x402",
    "firstPaidRoute": "/api/opportunity-check",
    "firstPaidRoutePrice": "$0.01",
    "builderMonetizationRoute": "/api/agent-revenue-audit",
    "builderMonetizationRoutePrice": "$5.00",
    "batchSettlementEnabled": false,
    "escrowEnabled": false,
    "offChainVouchersAccepted": false,
    "facilitatorSponsoredGasEnabled": false,
    "settlementRailChanged": false,
    "sellerWalletChanged": false,
    "automaticBuyerSpendingAdded": false,
    "paidCallsMadeByThisSurface": false,
    "paidUpstreamCalls": false
  },
  "readinessFit": {
    "usefulWhen": "A buyer agent starts making repeated high-frequency calls where per-request settlement latency or gas accounting becomes the blocker.",
    "notNeededWhen": "A buyer only needs one $0.01 proof call, one $5 builder audit, or a normal buyer-controlled x402 retry.",
    "currentApexScoutMove": "Publish readiness metadata now, keep the current per-request x402 payment behavior, and use the Agent Spend Passport as the no-spend first step.",
    "futureEvaluationChecklist": [
      "Confirm the facilitator supports the exact batch settlement shape ApexScout would use.",
      "Define seller-side accounting for vouchers, final settlement, refunds, and failed batch closes.",
      "Keep buyer budget approval outside ApexScout unless explicitly authorized by the buyer.",
      "Keep Cash Register aggregate-only and avoid wallet-level or voucher-level public histories.",
      "Run local and production no-spend checks before any settlement behavior changes."
    ]
  },
  "buyerAgentGuidance": {
    "recommendedFirstStep": "/agent-spend-passport",
    "normalLowVolumeFlow": [
      "Inspect /x402-proof.",
      "Generate a free /agent-spend-passport.",
      "Use /api/opportunity-check for the $0.01 proof route when the buyer only needs a cheap rail test.",
      "Use /api/agent-revenue-audit for the $5 builder monetization route only with approved budget.",
      "Stop if Passport says stop."
    ],
    "batchSettlementPosition": "Batch settlement is future compatibility context. Do not assume ApexScout accepts vouchers or escrowed batch payment today."
  },
  "guardrails": [
    "No paid calls are made by this readiness surface.",
    "No escrow, voucher acceptance, or batch settlement is enabled.",
    "No facilitator-sponsored gas claim is made for ApexScout production traffic.",
    "No settlement rail or seller wallet change is made.",
    "No buyer wallet custody, buyer budget management, or automatic buyer spending is added.",
    "No buyer-level data, full wallet addresses, full payment payloads, voucher histories, or paid response bodies are public.",
    "No revenue, conversion, endorsement, compliance, legal, tax, investment, lending, or trading guarantee is made.",
    "No scraping, posting, DMs, email, outreach, third-party discovery, fake traffic, or fake feedback is added."
  ],
  "publicCopy": "ApexScout is batch-settlement aware, but batch settlement is not enabled. Buyers should still start with the free Agent Spend Passport and use the standard buyer-controlled x402 paid retry only when the Passport says it is safe.",
  "nextAction": "Keep the current Base mainnet x402 flow live, monitor official x402 batch-settlement implementation guidance, and only evaluate a settlement change after real repeated buyer-agent usage justifies it."
}