2.18.0
The published package is still the production reference and is not claimed to contain the fix.
v2.2.217-machine-commerce-frontier / public no-spend frontier
ApexScout Machine Commerce Frontier
Pre-payment trust and checkout readiness for machine-native micro-commerce. Five current ecosystem shifts are mapped into one inspectable contract without adding a product, changing a price, or executing payment.
Base production preservedSigner release pendingMPP session modeled onlyWorld and Cloudflare previews only
1 Managed signers
Broader buyer wallets, without handling their keys.
The upstream x402 fix broadens Python EVM signer support beyond local accounts. ApexScout tracks the exact commit and waits for an official package release before claiming production compatibility.
Verified, release pending
Commit aad8e4e39d38 covers BaseAccount-derived AgentKit, custom-custody, and KMS shapes.
No private material
ApexScout accepts no signer, seed phrase, private key, or wallet credential on this surface.
2 Human-backed access
Free evaluation can gain a uniqueness guard.
World AgentKit is modeled as an optional future trust signal beside x402, not as identity collection and not as a discount already in production.
Open Ledger preview
The existing preview remains free for everyone and does not request World authentication.
Unique-human allowance
An illustrative five-request allowance shows how a free trial could resist agent swarms before paid access.
No proof stored
No World proof, identity, demographic field, nullifier, wallet, or buyer-level record is accepted or retained.
3 MPP sessions
Streaming billing is bounded before it is live.
A stateless fixture models per-unit billing, hard caps, explicit approval, and stop conditions. The current fixed-price Ledger charge remains unchanged.
Charge remains active
The current $0.10 Ledger uses its existing one-time contract. No session route was published.
10-unit hard cap
The illustrative fixture has a fixed unit amount and total cap. It cannot settle and accepts no payment credential.
Approval before session
Any future session needs an explicit budget, a unit ceiling, one approved session, and an immediate stop on receipt mismatch.
4 Temporary accounts
Preview before login, claim without custody.
The capsule documents Cloudflare's temporary-account flow for a future builder preview. ApexScout made no account, deployment, claim URL, or Cloudflare write.
Terms and proof of work
A future platform flow would explicitly accept terms and complete the provider challenge.
Temporary Worker
The builder could inspect a deployed preview before establishing a normal Cloudflare account.
Direct owner control
The builder would claim directly with Cloudflare. ApexScout would not receive account credentials or retain access.
5 Commercial category
Machine-native micro-commerce is the lane.
ApexScout sits before small agent purchases: inspect the contract, test compatibility, enforce buyer approval, then measure a real settled response. It is not a card network, wallet, or macro checkout platform.
Trust before payment
Compatibility, privacy, price, scope, and receipt expectations are visible before spend.
Delivery after settlement
Revenue remains tied to a buyer-controlled settlement and HTTP 200 delivery, never to a read or unpaid challenge.
Independent work
No Visa, World, Cloudflare, Coinbase, x402, MPP, or marketplace endorsement is claimed.
Agent discovery
One frontier, exposed in the places agents already inspect.
The same no-spend contract is available through a human page, JSON manifest, well-known metadata, OpenAPI, MCP, llms.txt, and the sitemap.
Manifest
/api/machine-commerce-frontierWell-known metadata
/.well-known/apexscout-machine-commerce.jsonOpenAPI
/openapi.jsonMCP Tool Pack
/api/mcp-tool-packHard boundaries
No automatic paymentNo new paid productNo wallet custodyNo World proof collectionNo Cloudflare mutationNo buyer-level dataNo endorsement claim