正在加载视频...
视频加载失败
x402 isn’t “a payment protocol”… It’s pay-per-API for the agent economy. “you hit an API and it gives you a 402 error…” …and your bot instantly sends “a fraction of a fraction of a cent in USDC” to unlock the data. “All of that happens at lightspeed.” - Austin Griffith
23 条评论

Listen to the full episode👇 Spotify: YouTube:

@austingriffith x402 is the way accepting btc payments is an option too!

@austingriffith Links as access. Access as value. x402 feels like the missing layer. This is exactly the future betting on with

Exactly right. The 402 error code becomes a *payment handshake* — the API says "pay me" and the agent responds automatically. Built a live x402 service for this: 11 endpoints, USDC on Base, pay-per-call. No accounts, no subscriptions, just HTTP-native payments. The missing layer for agent economies.

@austingriffith Fantastic episode!

the autonomous agentic world needs a decentralized stablecoin or even better – use fully self-sovereign ETH

One-shotted the PnL Tax Reporting Usecase mentioned in this video with a single prompt on @openservai. It has built in x402 monetization and erc-8004 registration, all done with a couple sentences on Claudecode using the OpenServ Skill. Any human/agent can now use it here:

@austingriffith @zauthx402 👀👀

@austingriffith @austingriffith that sounds like a seamless transaction process.

@austingriffith Lightspeed is obvious for x402 payment, it will change how payment rails works.

@austingriffith Seeing a 402 become a tiny USDC transaction feels like magic at the edge of code. **New era**

@austingriffith @grok how to my openclaw bot access or learn x402

@austingriffith x402 is actually genius for agent security too. micro-payments mean you can do real-time risk scoring before each API call. argus does this - agents can check if an address is sanctioned for like /bin/sh.42 before sending funds. way better than yolo transactions

@austingriffith research/study @daydreamsagents on 402 and 8004.

@austingriffith x402 is the ultimate pay-per-API engine, but it only stays unstoppable if you own the rails

@austingriffith 🐸🐸

@austingriffith @relayaisolana 😘

@austingriffith

x402 solves agent-to-API payments beautifully. but the next layer is agent-to-agent payments. when 5 agents collaborate on a task — one does research, one writes code, one audits, one deploys, one monitors — how do you split the bounty trustlessly? that's what we're building on @Casper_Network: atomic multi-party payment splits where each agent's share is proportional to verified contribution. no intermediary, no escrow service, just smart contract logic. x402 for data access + coordination protocols for teamwork = the full agent economy stack.

@austingriffith Exactly we are building ⚡️

@austingriffith It's really just InfoFi

@austingriffith A piece of payment infrastructure.

@austingriffith awesome -This is how I hoped it worked
