Corbits

Our team's been working overtime to get this shipped, and we're happy to share that MPP support has entered Developer Preview for @faremeterxyz with support for @solana Machine payments don't stop. Shoutout to the @tempo and @stripe teams for continuing to grow the pie.

@FwazSol @faremeterxyz @solana @tempo @stripe Let us know what you build!

@corbits_dev @faremeterxyz @solana @tempo @stripe Oh this is cool I’ll be playing with this tomorrow

Guess we're shipping support for Token-2022 on @solana too. Big day for @x402! Shippers ship.

@corbits_dev @switchboardxyz @faremeterxyz @solana @tempo @stripe Today was three-for-Thursday: initial MPP support in Faremeter, some Solana Token2022 housekeeping, and a nice new payment mechanism called Flex. All shipping soon. Get in touch if you want to try them early.

@switchboardxyz @faremeterxyz @solana @tempo @stripe Ask @alxndrguy what he's got cooking

@corbits_dev @faremeterxyz @solana @tempo @stripe chefs cook

@DebankinDad Devs just shipped MPP for Faremeter and Solana

@corbits_dev What's the news? 👀

Turned out there was some big news today 👀 bigger news tomorrow

@ampersend_ai @x402intern @stripe @tempo @CoinbaseDev Sounds like you’ve defined @faremeterxyz Protocol agnostic, bring your own definitions. Define your own boundaries.

.@stripe and @tempo just launched the Machine Payments Protocol (MPP). @CoinbaseDev has x402. both are open standards for letting agents pay for things. here's what each one actually does and where they differ. what they share both solve the same core problem: traditional payment infrastructure assumes a human is present. agents need to pay for resources programmatically, at machine speed, without navigating checkout pages, creating accounts, or waiting for settlement. both protocols are open-source and designed to be rail-agnostic. how x402 works x402 is built directly into HTTP. an agent requests a resource. the server responds with HTTP 402 (a status code that's been reserved and unused since the 1990s) and a JSON payload specifying the price, accepted token, and wallet address. the agent signs a payment cryptographically. the payment settles onchain. the server returns the resource. settlement today runs primarily on stablecoins across @base and @solana. 50 million transactions processed since launch. cloudflare is building native support. transaction costs run under $0.0001 on L2s. how MPP works MPP works at the application layer. an agent requests a resource from a service, API, or any HTTP-addressable endpoint. the service responds with a payment request. the agent authorizes payment through stripe's PaymentIntents API. funds settle into the business's existing stripe balance in their default currency on their standard payout schedule. the key difference: MPP supports stablecoins on @tempo (the new stripe/paradigm blockchain that also launched today) and fiat. cards, buy now pay later, and shared payment tokens all work through the same protocol. businesses accepting MPP payments get them through the same stripe infrastructure they already use for human payments, including tax calculation, fraud protection, and refunds. where they diverge x402 is protocol-native. it lives at the HTTP layer, settles onchain, and requires no intermediary accounts. it's optimized for microtransactions and machine-to-machine payments where speed and cost matter most. pay-per-API-call, compute access, data feeds. MPP is payments-infrastructure-native. it runs through stripe, which means businesses get the full stripe stack out of the box. it's optimized for agent-to-business payments where the business already operates on traditional payment rails and wants agent transactions to flow into existing accounting and operations. x402 is closer to how crypto-native builders think about agent payments. MPP is closer to how enterprise businesses want to receive them. visa contributed a card-based MPP spec today. browserbase, postalform, and prospect butcher co are already processing agent payments through MPP. mastercard acquired stablecoin infra startup BVNK for $1.8 billion this week. the infrastructure race is accelerating in real time. what neither one solves both protocols define how an agent pays. neither defines the boundaries of what an agent should be allowed to pay. per-transaction limits, time-based budgets, counterparty restrictions, automatic circuit-breaking when spending exceeds defined thresholds. the payment rails are multiplying. the controls layer remains the gap.

@0xyoussea @x402intern Both x402 and MPP are opinionated. Both work with @faremeterxyz. Makes things simple

An honest comparison of MPP vs. x402 🤖💸 I looked under the hood of both protocols (using the official docs). Both leverage HTTP 402 for payment requests, but their architecture, positioning, and execution are totally different. Here’s the technical breakdown 🧵👇

@takiskakalis @x402Foundation @coinbase This payment logic is possible at scale using the Flex scheme with @faremeterxyz

This article explained how to sell to an agent, but it missed one thing: Freemium. How is an agent supposed to try your product if it’s stuck behind a paywall? Today, that changes. In collaboration with @coinbase, we’ve released AgentKit, which extends x402 with Anonymous Proof of Human. Now your agents can prove to any x402 API that they’re backed by a human. Freemium makes sense again, but only with World ID. @worldnetwork

Discussing Confidential Transactions with SKALE | SKALE School x.com/i/broadcasts/1…

@CoinbaseDev @Autoincentiv3 Devs now have access to eip3009 with both CB and @faremeterxyz ? Pretty slick!

x402 now supports ANY ERC-20 tokens. Developers can accept payments using: → EIP-3009 (Transfer with Authorization) → Permit2 That means tokens like USDC, EURC, or any ERC-20 token via Permit2 (yes, even your fav memecoin) can now be used for onchain payments with x402. Docs: #5-accept-any-erc-20-token-with-permit2-optional-evm" target="_blank" rel="nofollow noopener">docs.cdp.coinbase.com/x402/quickstar…

x402 is heating up 🔥 We’ve been heads-down on your feedback to make agent payments smoother, faster, and more universal. Key updates 👇🧵

CTO @alxndrguy is back with SKALE sharing the latest on Faremeter v0.17.1 As agents are asked to make more transactions, how important are confidentiality and privacy?

x402 week is live 🔥 A full week of partnerships, new integrations, feature drops… and the spotlight on YOU. Tune in on X this Friday for a packed 402-minute (that’s 6.7 hours) event featuring builder spotlights where you can showcase your x402 build. 🧵

@CoinbaseDev Here for a good time, and a long time 💪

Agents are learning about reputation and identity on Solana. Come learn more about what this means for agentic commerce as we join @Quantu_AI and others to dive into agent identity and 8004. x.com/i/spaces/1nxeL…

@solana Happy birthday Solana!

Happy 6th birthday Solana fam. They said quit. The builders stayed. They said it's dead. The code persisted. They said move on. The network's never been stronger. Just one more hard quarter.

@usv @aweissman @uninsightful Nothing is more open than @faremeterxyz

We’re paying close attention to the open architecture emerging around AI agents. MCP, CLIs, skills, and protocols like x402 are becoming the Lego bricks of a new layer where agents can act, pay, and compose across the web. If you're building new native capabilities for agents, we’d love to talk.

x402 Weekly Wrap and Thoughts #19 & #20 It's official. It feels like everyone is an agentic payments company (and that's a not thing) if we look at how it's actually being positioned and deployed. Traditionally -- we saw many companies that lacked PMF hard pivot and chase a narrative with little to no execution. With agentic commerce -- while it is probably is still very much a FOMO situation for many -- the part that I think is feels different is that legitimate companies that are already successful are throwing their hat in the ring with new productions that expand their offering to agents or take existing products that may not have had huge adoption and point them toward the agentic market. The reality though? Agents themselves aren't there yet. I think it's fair to say we (as a technical industry) have mostly cracked the code on agentic coding more or less. It's just important to recognize that most of the "successful" agents you see on the timeline is just outright lies. They still fail consistently, struggle to follow commands, pick tools incorrectly, and just don't work as expected. I'm personally ok with this though because in reality it's been ~2-2.5 months (end of December) where agents really started to feel viable during the Claude Code moment. Some quick updates for the week and then read below for one critical thought on the above. Reminder, none of the below is financial advice; we are talking technology only. > @virtuals_io and @DavideCrapis shared 8183, the conditional payments commerce layer for AI Agents. (I see @SkaleNetwork as an ideal addition to this stack with conditional transactions (CTXs) allowing encryption to easily extend 8183) > @sponge_wallet is now supporting prepaid @Visa cards with x402 on @base with @USDC > @lordOfAFew shipped encrypted @xmtp_ with @daydreamsagents > @framesag rolled out a new CASHBACK feature. So far this is probably the top agentic wallet I've used > @KhalaResearch put out a nice ecosystem map for x402. (Missing @SkaleNetwork blockchain, @relayaisolana @gokobaru @corbits_dev and a dozen+ more facilitators) > @0xPolygon has been driving a significant amount of x402 growth and showcasing some nice developer tools with their new agentic tools > @relayaisolana dropped agent service keys which makes it easier to access the RelAI marketplace (very cool) > @StellarOrg has joined the world of x402 > @synthesis_md is now live! An agentic hackathon for agents (should be interesting) My biggest thought for the week is that too many people are telling me we are in a chicken/egg situation. Merchants want agents. Agents want merchants. Keep building, we are very very early.