Hey team,
The current x402/ samples show Stripe's own demo seller end-to-end, which is great as a baseline. Wondering if there'd be appetite for a PR adding a small buyer-side example that points at a real production x402 seller — i.e., showing your x402 client paying a live MIT-licensed third-party endpoint over real USDC on Base.
Concrete scope I'd offer:
- Add
x402/examples/anchor-x402/ (Python and/or TypeScript)
- ~30-50 lines, calls one of my live endpoints (e.g.,
/v1/screen at $0.001)
- Uses the standard
@x402/fetch / x402 client already vendored in the repo
- Live seller:
api.anchor-x402.com — 15 standard x402 v2 endpoints, my project, MIT, solo
- No Stripe seller-side code added; just demonstrates the client buying from an arbitrary v2 resource server in the wild
Goal would be giving readers a runnable reference for "what does it look like when the seller isn't running Stripe's sample?"
Totally fine if you'd rather keep the samples scoped to Stripe-as-seller only — just want to check before opening anything.
Thanks,
Chris
github.com/hypeprinter007-stack/anchor-x402
Hey team,
The current
x402/samples show Stripe's own demo seller end-to-end, which is great as a baseline. Wondering if there'd be appetite for a PR adding a small buyer-side example that points at a real production x402 seller — i.e., showing your x402 client paying a live MIT-licensed third-party endpoint over real USDC on Base.Concrete scope I'd offer:
x402/examples/anchor-x402/(Python and/or TypeScript)/v1/screenat $0.001)@x402/fetch/x402client already vendored in the repoapi.anchor-x402.com— 15 standard x402 v2 endpoints, my project, MIT, soloGoal would be giving readers a runnable reference for "what does it look like when the seller isn't running Stripe's sample?"
Totally fine if you'd rather keep the samples scoped to Stripe-as-seller only — just want to check before opening anything.
Thanks,
Chris
github.com/hypeprinter007-stack/anchor-x402