Agent Commerce Reliability Ledger

A bodyless GET containing scoped x402 SDK 2.26 offline findings and separately labeled historical buyer-client, failure and payment records. Includes tested cases, limitations, evidence digests and expiry. Not current wallet or mainnet compatibility, an incident diagnosis, or independent certification; it never initiates payment or handles buyer identity.

$0.10 USDC · Base x402 or Tempo MPP · one buyer-controlled GET

GET https://apexscout.ai/api/agent-commerce-reliability-ledger

Inspect the unpaid 402 Preview JSON Check another x402 endpoint

The scoped offline SDK findings remain inside their declared validity window. Historical buyer-client and payment records were not re-verified. The preview does not pay, open a wallet, create an account, or expose the full ledger.

New edition: scoped offline observations

One partial example · SDK 2.26

Core HTTP and startup fixture observations

For twelve synthetic verify/settle responses, missing or invalid extension headers were ignored; a body extensionResponses field did not impersonate header diagnostics. Each response retained its synthetic success result, used one mocked request, and emitted no logs.

24 HTTP/server cases · 12 route-template cases · 3 exact EVM requirement-construction cases. Seven separate import checks are not runtime support. These are synthetic, self-authored tests, not wallet, AWAL or mainnet verification. Customer usefulness is not established.

Observed 2026-10-04T23:26:18.598Z · expires 2026-10-11T23:26:18.598Z. Packaging the saved evidence does not renew its age.

Historical examples · not re-verified

Compatibility entries, failure signatures, fixes and buyer recipes are retained historical context. The new SDK fixtures do not refresh their verification dates, establish a current incident diagnosis or authorize a retry.

Historical compatibility

AWAL CLI 2.12.0

Canonical PAYMENT-REQUIRED parsing is verified without payment.

Historical failure RCL-001

header body version mismatch

The client can inspect the route but rejects the payment-required response as invalid.

What changed in this edition

Re-executed the 39 installed SDK 2.26 offline fixtures on October 4: 24 HTTP/server cases, 12 route-template cases and three exact EVM requirement-construction cases. All passed with a new execution binding, unchanged fixture source and package bindings, and an October 11 expiry. Historical client observations and payment records are unchanged; no new live compatibility claim or failure-to-client applicability is added.

Bazaar MCP · listing unverified

Current Bazaar listing and proxy purchase are unverified. If search returns this exact Ledger URL, verify its terms before using your own buyer client. Otherwise use the direct HTTP route below. ApexScout does not claim a separate direct remote paid MCP runtime.

1. Verify the listing

search_resources

A search result is not guaranteed. Require the exact Ledger URL, price, network and current edition before considering payment.

2. Confirm before purchase

proxy_tool_call

Only use a matching result with explicit buyer approval and a one-call $0.10 limit. Stop if the listing or its terms cannot be verified; do not substitute another resource.

Check the direct unpaid route

This credential-free GET returns payment requirements, not a purchase. Read the exact terms before any separate buyer-approved payment.

MPP-native buyer path

Discover ApexScout through MPPScan or the mpp.dev catalog after an owner-controlled listing is public; until then use the canonical ApexScout preview and docs.

Inspect GET /api/agent-commerce-reliability-ledger and confirm the fixed $0.10 charge.

Verify tempo/charge, Tempo eip155:4217, 100000 atomic USDC, recipient, issuedAt, and expiresAt from the live challenge.

Confirm the current Ledger edition and content digest on the free preview.

Ask for explicit buyer approval for one $0.10 call.

Pay once with the buyer's own MPP client. ApexScout never operates the buyer wallet.

Require Payment-Receipt, HTTP 200, and the complete Ledger delivery.

Stop after delivery or any mismatch, expiry, rejection, or incomplete response; never pay or retry automatically.

If the Commerce Intent expires before payment begins, fetch one fresh unpaid challenge without a payment credential, verify identical terms, and ask for fresh approval. The refresh is stateless and a settled intent can never refresh into another charge.

Buyer-runtime recipes

RUNTIME-A

x402scan Composer / AgentCash

Use Composer resource search or `npx -y agentcash@latest discover https://apexscout.ai`.

Set or retain a buyer-controlled maximum of $0.10 / 100000 atomic USDC for this task.

Explain what the full Ledger adds beyond the preview.

Stop after one paid call, any rejection, a price or network mismatch, missing approval, or incomplete delivery.

RUNTIME-B

Coinbase Agentic Wallet Payments MCP

Install the official buyer runtime with `npx @coinbase/payments-mcp` and use its service discovery against apexscout.ai.

In the buyer wallet UI, set max per call to $0.10 and keep the task/session allowance limited to one Ledger call.

Show the route, price, network, freshness window, and one-call maximum.

Stop after one paid call or any mismatch, rejection, or incomplete response.

RUNTIME-C

AWS AgentCore Gateway with Coinbase Bazaar MCP

Add the official Coinbase Bazaar MCP target https://api.cdp.coinbase.com/platform/v2/x402/discovery/mcp to an owner-controlled AgentCore Gateway with no outbound authorization.

Configure the owner-controlled AgentCore payment policy for a maximum $0.10 single call and one call for the task.

Show the exact selected resource, amount, network, and one-call policy.

Stop after one paid call, any policy denial, resource mismatch, 402 loop, or incomplete delivery.

RUNTIME-D

MPP Tempo buyer

Read the free preview, then fetch the Ledger route without a credential and parse its WWW-Authenticate Payment challenge.

Keep the buyer-controlled maximum at $0.10 and allow one Ledger call for the task.

Show the exact Ledger route, amount, Tempo network, recipient, and one-call limit.

Stop after one paid call or any route, amount, network, recipient, expiry, or delivery mismatch.

RUNTIME-E

Solana Agent Registry

Resolve the finalized ApexScout onchain identity, then read the public Registry metadata and free Commerce Explorer with src=solana-agent-registry.

Keep the buyer-controlled maximum at $0.10 and permit one Ledger call for the task.

Show the exact route, Solana network, recipient, amount, edition digest, and one-call maximum.

Stop after one paid call or any identity, route, price, network, asset, recipient, expiry, receipt, or delivery mismatch.

ApexScout does not operate the buyer wallet. Every recipe requires explicit buyer approval and stops after at most one $0.10 Ledger purchase.

The paid response includes

Scoped SDK 2.26 findings linked to 39 retained offline cases; seven import checks are not runtime verification.

The complete historical buyer-client compatibility matrix with unchanged observation dates.

Historical public-safe failure signatures, mitigations and retry rules; not re-verified by the new SDK cases.

Historical buyer recipes and command examples, subject to current terms and explicit buyer approval.

Content digest, generatedAt, validUntil, evidence policy, and privacy contract.

Bazaar MCP discovery and buyer-controlled proxy purchase instructions.

Buyer-controlled purchase recipes for Composer/AgentCash, Coinbase Payments MCP, AgentCore with Bazaar MCP, and MPP Tempo.

Deliberately excluded

raw service logs
raw buyer input
full wallet addresses
payment signatures
payment payloads
facilitator secrets
private keys or API keys
unpublished exploit instructions
competitor proprietary data