Stripe Link Agent Wallet Readiness

User-approved spend. Base still settles.

A readiness pack for buyer agents that may use Stripe Link's agent wallet for user-approved purchases while Agent Research Desk keeps production settlement on the proven Base x402 rail.

Base x402 remains active No Stripe settlement today No card tokens issued Buyer-side wallet lane
Current settlementBase mainnet

eip155:8453

Link statuswatched buyer-wallet lane

Link can be tracked as a buyer wallet path, not an accepted ARD rail.

Stripe proofNot run

Requires a separate approved design before any card or token acceptance claim.

Credential postureNo raw credentials

ARD never asks for cards, Link OAuth, or buyer payment credentials.

How to use it now

Buyer agents keep control.

  • Use Link on the buyer side if your agent already has a user-approved Link wallet flow.
  • Inspect /docs.json, choose an ARD route, and send the normal unpaid probe first.
  • Only pay ARD through the current x402 route unless a separate Stripe/Link proof flow is designed and approved.
  • Treat Link as a credential-safety and approval model for buyer agents, not as ARD's current settlement method.

Guardrails

No payment switch without proof.

  • Do not add Stripe secret keys, Link OAuth, Checkout Sessions, PaymentIntents, card settlement, shared payment tokens, Tempo streaming payments, or token issuance to the live payment flow.
  • Do not create Link spend requests or approve purchases from this service.
  • Do not claim ARD accepts Link, cards, or shared payment tokens until a separate proof design and settlement test pass.
  • Do not change the working Base mainnet x402 middleware, facilitator, seller wallet, endpoint paths, or route prices.
  • Do not expose buyer prompts, wallet-level request history, raw feedback comments, watched subjects, or paid response contents.

Proof gate before acceptance

Link needs its own design and settlement proof.

not-run Provider fit

Official Link agent wallet provider requirements are reviewed for API-service purchases.

not-run Unpaid challenge compatibility

A Link-controlled buyer agent can still read ARD's normal HTTP 402 challenge without breaking Base.

requires-separate-approval Paid proof design

A separate proof plan defines whether Link pays a card route, an x402 route, or a future protocol bridge.

not-run Settlement proof

Any non-x402 Link proof settles into a seller-controlled account with clear receipts and rollback.

ready Rollback clean

Base remains the default active rail after the proof window is removed.

Source and product links

Wes Roth Posthttps://x.com/WesRoth/status/2049896564961738792 Stripe Bloghttps://stripe.com/blog/giving-agents-the-ability-to-pay Stripe Agentic Commerce Docshttps://docs.stripe.com/agentic-commerce Link Agentshttps://link.com/ae/agents ARD Docs JSONhttps://apexscout.ai/docs.json Instant x402 Testbenchhttps://apexscout.ai/instant-x402 Live Dashboardhttps://apexscout.ai/dashboard