x402 Exposure Map · evidence, not tips
Map where x402 value might accrue. Test the thesis without a trade.
Follow the settlement, payment unit, facilitator, wallet, discovery, and identity layers that make paid agents work. Every entry names its role, primary source, constraint, and failure condition—never a ranking or price target.
A six-layer mental model
Infrastructure first. Tokens only when they are actually the payment rail.
The map separates protocol adoption from investable-asset stories. A useful product can grow without creating a token, and a protocol signal is not a promise of financial return.
- 1
Read the job
Understand what the layer contributes to one paid request.
- 2
Check the constraint
See the dependency or trust assumption before the opportunity.
- 3
Write the exit
Decide what evidence would change your mind before saving a paper thesis.
Records the EVM payment authorization and settlement used by Botlings' current x402 routes.
- Observable signal
- x402 reference tooling continues to support Base mainnet, while Base continues to publish transaction data to Ethereum for data availability.
- Constraint
- Base currently documents one active sequencer. Inclusion, RPC availability, L1 data costs, and finality remain operational dependencies.
- What would change the thesis
- Botlings' paid routes migrate away from Base, x402 support is withdrawn, or reliable settlement becomes materially worse for small exact payments.
- Evidence reviewed
- 31 Aug 2026
Provides the six-decimal dollar-denominated unit used for Botlings prices, caps, payouts, and receipts.
- Observable signal
- Circle continues to list native USDC on Base and x402 continues to document EIP-3009 authorization for compatible EVM tokens such as USDC.
- Constraint
- USDC depends on its issuer, reserves, redemption access, contract controls, and supported-chain policy. A stable unit is not a risk-free asset.
- What would change the thesis
- Native USDC support on Base is withdrawn, redemption confidence materially weakens, or x402 demand standardizes around a different payment unit.
- Evidence reviewed
- 31 Aug 2026
Defines the HTTP payment challenge, authorization, verification, settlement, and response flow shared by buyers and sellers.
- Observable signal
- The neutral x402 documentation describes a multi-network open standard and continues to publish buyer, seller, facilitator, and extension specifications.
- Constraint
- Protocol compatibility can fragment across versions, schemes, networks, client libraries, and incomplete implementations.
- What would change the thesis
- Interoperability stalls, major clients require proprietary account rails, or real services stop accepting independently generated x402 authorizations.
- Evidence reviewed
- 31 Aug 2026
Verifies payment payloads and submits eligible settlements for supported x402 schemes and networks.
- Observable signal
- Coinbase Developer Platform currently documents Base support for exact, upto, and batch-settlement schemes in its facilitator.
- Constraint
- This is managed infrastructure with credentials, quotas, pricing, availability, and policy dependencies; it is not the x402 protocol itself.
- What would change the thesis
- Base or required schemes lose support, service reliability no longer fits paid APIs, or switching to another compatible facilitator becomes impractical.
- Evidence reviewed
- 31 Aug 2026
Turns a user's wallet authority into explicit transaction and signing boundaries for human-approved or delegated payments.
- Observable signal
- Privy documents cryptographic authorization plus policies for wallet actions, including signature requests, transactions, and export.
- Constraint
- Custody properties depend on the exact owner, signer, quorum, policy, and export configuration. A wallet vendor cannot make an unsafe policy safe.
- What would change the thesis
- Users cannot export or independently authorize their wallets, policy enforcement becomes unverifiable, or Botlings requires broader authority than a task needs.
- Evidence reviewed
- 31 Aug 2026
Lets sellers publish service metadata so buyers can find a paid API before deciding whether it is compatible or trustworthy.
- Observable signal
- x402 V2 documents a Discovery extension intended to synchronize published APIs across facilitators.
- Constraint
- Discovery proves neither quality nor safety. A listing can be stale, incompatible, misleading, or malicious and must remain unapproved by default.
- What would change the thesis
- Listings cannot be independently verified, discovery concentrates behind a closed gate, or published metadata ceases to match live 402 challenges.
- Evidence reviewed
- 31 Aug 2026
Proposes portable onchain agent identity, service endpoints, feedback, and validation links that can advertise x402 support.
- Observable signal
- The published draft defines identity, reputation, and validation registries plus endpoint-domain verification.
- Constraint
- ERC-8004 is a draft. Its own security section says Sybil attacks are possible and identity cannot guarantee advertised capability or safety.
- What would change the thesis
- The draft changes incompatibly, reviewed deployments fail to emerge, or ecosystem clients do not use the records when selecting services.
- Evidence reviewed
- 31 Aug 2026
Private paper portfolio
Allocate attention, not money.
Save a falsifiable view and a simulated amount. Botlings does not buy an asset, connect an exchange, calculate invented returns, or gain wallet authority.
Hard boundary
No trades hide behind the map.
Botlings stores only your private text and simulated allocation. It requests no exchange key, token approval, swap, bridge, transfer, or investment mandate. Research calls remain separate, exactly quoted x402 purchases.