Today is probably a good time to check in on things with @privy_io, which became part of @stripe just over a year ago. Our acquisition was predicated on three factors: stablecoin growth, self-custody as a key enabler of broader global coverage, and rapidly increasing demand for programmable financial infrastructure. As we said at the time, "money has to reside somewhere, and Privy builds the world's best programmable vaults." Since then, the Privy team has executed exceptionally well: assets in Privy wallets have grown ~25x, monthly active developers are up ~3x, revenue is up ~9x, and Privy now facilitates nearly $25B of monthly transaction volume. @tryramp, @Deel, @Klarna, @felixpago, @HyperliquidX, and thousands of other businesses are building embedded banking functionality on Privy. At Stripe, we're deeply integrating Privy into Treasury, @Link, and Connect. In each case, it's accelerating our global expansion, and enabling us to build better functionality faster. (Coming soon: @Link balances.) We're also seeing that Privy's wallet infrastructure is the ideal substrate for agents to transact and earn -- live today with @merit_systems, @orthogonal_sh, @Nevermined_ai, @prlnet, and more. Developers prefer programmable financial infrastructure, but agents need it. We expect that the agentic economy will continue to grow extremely quickly. The Privy team has maintained remarkable product velocity, with major launches this year including deposit addresses, earning on Privy balances, digital asset accounts, custodial wallets, and Stripe's own stablecoin cards. It's also been neat to see how Privy has been accelerated by Stripe, with better onramps, @stablecoin payment rails and licenses, Stripe's fiat capabilities and issuing stack, and integration with @Tempo. Together, we're building one API for holding stablecoin balances and earning yield, moving money in and out of fiat, and orchestrating spend with cards. We still have a lot of work to do, not least in integrating everything across Privy, Bridge, and the rest of Stripe -- there's been so much feature and functionality expansion that we haven't yet had much time to reconcile everything. Overall, though, I'm very happy with how things are going, and excited by where these capabilities are headed. If you're interested in working on the future of stablecoins, agentic payments, and crypto's deployment in the real world, you should get in touch with @sternhenri (now leading all of @StripeCrypto) or others on the team.

Introducing Claude Sonnet 5.5, the second model in the Claude 5.5 family. It’s a clear upgrade over Sonnet 5, runs more than 30% faster, and costs up to 30% less for most work.

Agents can now do more than transact. They can help build pipeline. On Circle Agent Marketplace, where agents discover and pay for services in USDC: GTM services that help agents find prospects, enrich contacts, verify emails, and support lead workflows. Featuring: @useapolloio, @cladoai, Findymail, Hunter, and Icypeas, with endpoints provided by @orthogonal_sh and StableEnrich. Building an agent? Browse the marketplace:

Introducing Monad API Hub One place for developers and agents to access data, search, and AI APIs. No API keys. No subscriptions. Pay per request with USDC on Monad. Explore API Hub:

Hermes and Pi Agent led on the average cost per task, while Claude Code cost about 3.7x as much as Pi: - $0.39 Hermes Agent - $0.40 Pi Agent - $0.47 Codex - $0.51 OpenCode - $0.54 Kimi Code - $1.47 Claude Code The median cost tells the same story: $0.29 in Pi Agent and Hermes, $0.35 in OpenCode, $0.38 in Kimi Code, $0.39 in Codex and $0.72 in Claude Code, so the cost gap holds for a typical task and is not driven by a few expensive runs. We calculated these costs using Kimi K3’s list prices: $3/1M input tokens, $0.30/1M cached input tokens, and $15/1M output tokens.