John Weeks - PipRail @johnweeksdev

@IxsFinance They can with PipRail.com

@injective Great to see x402 agent payments on @injective 🙌 It's also one of the 29 chains @piprail/sdk pays out of the box — name the chain, add a wallet, pay any x402 endpoint in INJ/USDC/USDT. No backend, no facilitator, no fee. #x402 #AIagents

Your AI agent can now pay on TON, the chain behind Telegram. 🛤️ npm i @piprail/sdk, name the chain, add a wallet. It pays any x402 endpoint in USD₮ or Toncoin. No backend, no fee. @ton_blockchain #TON #x402 #AIagents #payments #crypto

@0xPolygon @aifinpay Accepting x402 payments on Polygon is a single line, USDC, straight to your wallet. No backend, no facilitator, no fee. And the same line works on 29 chains, just change `chain`. One SDK, every rail. #Polygon #x402 #AIagents

⚡ Kaia is now live on PipRail. Hand your AI agent a budget-capped wallet to pay x402 APIs on @KaiaChain in native KAIA or Tether-native USD₮. Backendless, no fee, settled straight to your wallet. That's 29 chains now, one chain away #x402 #AiAgents #AiPayments #evm

@solana @fabric_vc @wintermute_t Machines can think. Now they can pay. PipRail hands any AI agent a budget-bound wallet to pay x402 URLs, capped by a policy it can't break. Self-custodial, no facilitator, 28 chains. More to come! The rails for the machine economy → piprail.com

@DTPaymentNews Great recap. One to watch in the electronic exchange of value: machine-to-machine payments, AI agents paying per request, autonomously. Runs on the open x402 standard. We build PipRail, an SDK for it: no backend, no fee. Glad to share more. #payments #x402

@Fetch_ai 100%. 2026 is the year agents start transacting, and an economy runs on payments, not just tokens. That's the piece we build: PipRail gives any agent a budget-bound wallet to pay x402 URLs (or charge one for your API) on @BNBCHAIN + 27 more. #x402 #AIAgents

@IxsFinance @BitGo 100%. And the wallet part is already built; it's exactly what we made PipRail for. It gives any AI agent a budget-bound wallet to pay with: x402 payments, capped so it can't overspend, on 28 chains. The financial rails for machines, today. #x402 #AIAgents

@AIonBase_ @base @virtuals_io @AskVenice @KaitoAI @aeonframework @awenetwork_ai @bankrbot @OpenGradient @Wach_AI @gitlawb @miroshark_ Honestly can't pick, but whichever one you do, it's going to need to pay for things eventually. That's us. PipRail: a budget-bound wallet any agent can use to pay x402 URLs on @base + 27 more chains. The plumbing under the whole list. #x402 #AIAgents

@coinbureau This is the x402 wave, and it won't stay on one chain. PipRail brings the same agentic payments to 28 chains: charge an AI agent for your API in one line, or give yours a budget-bound wallet to pay. USDC, no backend, no fee. #x402 #AIAgents #Base

@solana_daily Wherever the value's flowing, you can already get paid there. x402 is live on 8 of these top 10 chains today, accepting a payment in one line, in USDC, straight to your wallet. No backend, no fee. (Just Plume + Liquid Network left to go.) #x402 #RWA

@IkerNear Thanks, man. I really appreciate that, honestly. Your question sent me down the rabbit hole, so thanks. And if you do find any holes in it, DM me. Coool

Your API can charge for itself. PipRail lets any HTTP endpoint demand a crypto payment before it responds, in one line of code, across 28 chains. No backend. No database. No fees. The money lands straight in your wallet. Open source. Here's how it works. #x402 #AIAgents

Built on the open x402 standard from @coinbase live, self-custodial, no backend, on: @base @solana @SuiNetwork @ton_blockchain @NEARProtocol @Algorand @StellarOrg @arbitrum @0xPolygon @avax @zksync @Aptos @trondao + more. USDC by @circle, almost everywhere.

Someone asked me a great question: if the payer just sends a transfer to your wallet, why do we need x402 at all? Can't it just be a simple transfer? I've been chewing on it, so I dug in, honestly trying to find out if they were right. Here's what I found 🧵 (6 slides)

So… it really is just a transfer. x402 is the thin open standard around it that makes it usable, no backend. Wrote it up, slides, runnable code, and the limits I hit: github.com/piprail/piprail I could be wrong, so if you spot a gap, I'd love to hear it. #AIAgents

My takeaway: you can skip the 402 status code, but probably not the handshake. Rebuild it privately, and you lose the part that matters most: every other client and chain already speaking the same open standard (x402, from @coinbase). #x402

What I realised is that the moment you patch those gaps, a per-request ID, signed terms, a used-set, a verify step, you've basically rebuilt x402. Just a private version, so no other client or wallet speaks it.

Being honest: a careful raw setup actually CAN match most of the on-chain security, verify, replay, signed terms. I'm not going to pretend otherwise. The two it really struggles with are dynamic per-request pricing and open-standard interop.

And a plain transfer leaves a few gaps. I put them in a tiny script you can run yourself: - discovery: nothing at the URL says the price - replay: an old tx hash can unlock again - collision: two identical 0.05 sends, which one paid which request?

The thing I kept coming back to: with a plain transfer, how does your server even know a payment landed? You end up running a backend, watching the chain, matching it to a request, telling the user they're in (via Etherscan/Alchemy). x402 folds that into one verify().