Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

x402 on Stacks is HTTP-native Bitcoin payments. Micropayments without Stripe. No accounts. No trust. No delays. Just a 402 Payment Required → instant on-chain settlement. Built for APIs. Built for agents. Built for what the internet should’ve had all along. x402 Stacks

11,269 Aufrufe • vor 9 Monaten •via X (Twitter)

10 Kommentare

Profilbild von whoabuddy.btc
whoabuddy.btcvor 9 Monaten

@x402stacks Processed over 2000 mainnet STX payments in testing stx402 endpoints, new stats dashboards and endpoints coming live too LFG

Profilbild von Pedro Oliveira
Pedro Oliveiravor 9 Monaten

@x402stacks bullish

Profilbild von Yeheskiel Yunus Tame
Yeheskiel Yunus Tamevor 9 Monaten

@x402stacks love to hear about x402 the feature of micropayment

Profilbild von melanie
melanievor 9 Monaten

@x402stacks Brilliant 👏

Profilbild von Hax #FREESAMOURAI
Hax #FREESAMOURAIvor 9 Monaten

@x402stacks great hype for x402 ⭐

Profilbild von sargesmith.btc
sargesmith.btcvor 9 Monaten

@x402stacks let's go stacks 402

Profilbild von Viktor
Viktorvor 9 Monaten

@x402stacks Since you have the rail, what is needed to agents we can trust and can be verified. You'll need to 8004 for that beforr we can trust your x402 rail.

Profilbild von Resonance
Resonancevor 9 Monaten

@x402stacks What would an agent do on Stacks?

Profilbild von ryuvan 🐉 $MON
ryuvan 🐉 $MONvor 9 Monaten

@x402stacks HTTP status codes finally doing God's work on Bitcoin

Profilbild von sniperxfun
sniperxfunvor 9 Monaten

@x402stacks "I'm a bit skeptical about whether it really makes sense for x420 to be built on the BTC network."

Ähnliche Videos

I’ve been watching x402 since Coinbase 🛡️ launched it in May 2025. I did a quick research pass. Here’s the snapshot ↓ Early integrations: • CoinGecko: x402 pay-per-use access for agents (shared by Coinbase Developer Platform🛡️). • Vercel: x402 AI starter template (x402 + modern AI stack demo). • Firecrawl: x402-powered search endpoint (pay per request). • Concordium: x402 + native age verification for agent payments. • Multiversᕽ: “agentic payments” built around x402 support. • AltLayer: building an “x402 Suite” for value exchange between agents. • Solana claims x402 has processed 35M+ transactions and $10M+ volume since launch. TL;DR x402 turns HTTP 402 “Payment Required” into a payment flow. A server returns a price for a request. The client pays in stables like USDC. Then the server returns the result. → Coinbase launched x402 via Coinbase Developer Platform (May 6, 2025). → Coinbase + Cloudflare announced the x402 Foundation (Sep 23, 2025). → Cloudflare added x402 support into its Agents SDK + MCP servers. Why? - AI agents need a clean way to pay for tools. - Data, compute, APIs, services. - No accounts, cards, or subscription screens. x402 is trying to make pay-per-request feel normal. Use cases that already make sense → Paid APIs Pay per call instead of subscriptions. → AI tool calls Pay per query, per inference, per task. → Agent-to-agent payments Software paying software automatically. → Micropaywalls Pay for one endpoint, one action, one piece of content. If this takes off, stablecoins stop being a story. They become how apps and AI agents pay for things online.

Stacy Muur

12,220 Aufrufe • vor 8 Monaten

x402 made payments native to HTTP. I made USDC payments native to sound waves ✨ Not as a gimmick. As a proof. 1/ The setup: Coinbase Developer Platform🛡️'s x402 protocol embeds payments into HTTP. It's brilliant. But I started wondering, if we can pay over HTTP, what else can we use to pay? Spoiler: anything that supports 138 bytes 2/ The realization: x402 is built on EIP-3009 - a 2020 standard that lets you sign payment authorizations offline. Someone else submits it on-chain. The signature just needs to get from A to B. HTTP is one way. Sound is another. 3/ What I built: x402hz: two devices negotiate a payment through 2400Hz audio tones. - Seller beeps "pay me $0.001 USDC" (30 bytes) - Buyer's device decodes, signs the EIP-712 for the transferWithAuthorization locally, beeps back (108 bytes) - Seller settles on-chain Total: 36 seconds of beautiful noise. 4/ The bigger point: If payments can travel over sound, they can travel over: - QR codes - NFC - Bluetooth - Light pulses - Anything that carries 138 bytes The payment primitive is transport-agnostic. x402 picked HTTP. The next protocol might pick something weirder. 5/ What this proves: EIP-3009 separates three things: - Authorization (offline, cryptographic) - Transport (literally anything) - Settlement (on-chain) x402 nailed #1 and #3. x402hz proves #2 is wide open. 6/ Credit: Huge thanks to the Coinbase Developer Platform🛡️ x402 team for building the protocol. I just... took it off-road. 7/ Next steps Code is open source. Go make payments, travel over something ridiculous (repo in the comments). 138bytes. That's all you need.

Vitto Rivabella

40,536 Aufrufe • vor 10 Monaten