/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Coinbase announces a “Wallet-as-a-Service” product, offering APIs to help companies create customizable wallets for their apps more easily

- Coinbase has announced a product called Wallet-as-a-Service (WaaS), designed to let companies build web3 experiences that have simple wallet onboarding.

The Block James Hunt

Context & Ripple Effects

Wallet-as-a-Service extends a decade-long build-out of Coinbase's wallet stack: the exchange first turned its Toshi browser into Coinbase Wallet in 2018 for consumer access to decentralized apps, then opened institutional-grade storage with Custody. WaaS flips the direction of travel — instead of shipping a wallet to end users, Coinbase now sells the wallet layer itself as APIs that other companies embed in their own apps.

That B2B turn proved durable: the same infrastructure lineage resurfaced as Embedded Wallets in the Wallet SDK two years later, was folded into the Base App consumer play, and by 2026 had evolved into Agentic Wallets on x402 where AI agents transact autonomously. WaaS is the hinge point where Coinbase stopped being only a wallet maker and became wallet infrastructure.

First-order effects

  • Companies building web3 apps can now offer wallet onboarding through Coinbase's APIs rather than building key management and custody themselves — the hard, liability-heavy part of web3 UX becomes a vendor dependency.
  • Coinbase gains a distribution channel beyond its own retail base: every partner app embedding WaaS routes users' onchain activity through Coinbase-controlled infrastructure.

Second-order effects

  • Specialized wallet-infrastructure vendors face an incumbent with exchange-scale resources selling the same embeddable-wallet capability, pressuring them to compete on customization and pricing rather than existence.
  • Cloudflare's later entry with stablecoin-payable Cloudflare Wallets for APIs and content shows where the lane WaaS opened leads: non-crypto-native infrastructure companies bundling wallets into services they already sell.

Third-order effects

  • If the pattern holds, the wallet stops being a product and becomes a permission layer — invisible plumbing embedded in apps, and eventually operated autonomously by AI agents, with whoever runs the infrastructure controlling identity and payment flows across web3.
  • That consolidation around a few infrastructure providers would make wallet provisioning a commodity API business, shifting competitive value from holding assets to routing the transactions they enable.

The trend: Crypto wallets are platformizing from consumer products into embeddable infrastructure APIs, a line Coinbase has pushed from WaaS through Embedded Wallets to agent-operated wallets while adjacent players like Cloudflare follow.