Coinbase Developer Platform
The serious-builder's entry point to Base. CDP rolls server wallets, embedded wallets, Onramp, Paymaster (gasless), x402 (stablecoin HTTP payments), Agent Kit, Agentic Wallet, Faucets, Data API, and a free Base RPC node into one auth surface. If a GL app needs custody/funding/sponsorship/data on Base, this is the default integration point — not a tangle of provider SDKs.
CDP is what Coinbase shipped to make the "we're all building on Base" story real for indie + enterprise developers. One CDP account, one set of credentials, and the whole product matrix shows up behind it. This page is the orient-and-pick-the-right-surface entry point — official docs at docs.cdp.coinbase.com own the API contracts.
What it is
A unified infrastructure platform from Coinbase for building on Base (and Coinbase's other surfaces). Single account, single API-key surface, every product underneath. The pitch: instead of stitching together Alchemy + Privy + Coinbase Pay + Pimlico, one account covers RPC, wallets, onramp, and sponsored gas.
At a glance
Primary product surfaces (the ones most builds touch)
- Wallets — server wallets (custody-as-a-service), smart wallets (ERC-4337), embedded wallets (email/social/passkey), non-custodial wallets. Pick the custody model per product surface.
- Onramp / Offramp — fiat-to-crypto and crypto-to-fiat with a Coinbase-hosted UI or a headless API. The path for "let the user buy USDC in-app" without standing up your own payment stack.
- Paymaster — sponsor user gas. Combined with smart wallets you get truly gasless UX, the prerequisite for any consumer-grade app on an L2.
- x402 — Coinbase's HTTP-native stablecoin payment standard. Pay per API call, per minute of streaming, per inference run. The most under-talked-about primitive in the matrix right now.
- Agent Kit + Agentic Wallet — give an AI agent a wallet of its own with policy guardrails. Maps directly to the GL playbook for autonomous agents that need to do things on-chain.
- Data API — wallet balances, tx history, portfolio. Cheaper and simpler than running a subgraph for read-only product surfaces.
- Node — free mainnet RPC for Base. Default RPC for any GL Base integration unless we need a specialty provider (event subscriptions, archival, etc.).
- Faucet — Base Sepolia testnet ETH. Standard part of the dev loop.
Secondary surfaces
- Staking API, Advanced Trade API, Custom Stablecoins — stake-as-a-service, programmatic trading on the Coinbase venues, branded stablecoin issuance.
- Coinbase Business / Exchange / Prime / International Exchange / Derivatives — the institutional-trading APIs. Same auth surface, different product line.
How to integrate
Default integration order for a new GL Base app:
- CDP account + API keys, dev environment only.
- Faucet → Base Sepolia for end-to-end testing before mainnet.
- Smart wallet for the user-facing wallet model (passkey-backed, embedded sign-in).
- Paymaster wired up before mainnet — first-time users should not see a "fund your gas" wall.
- Onramp (hosted) for the fiat-in flow until headless makes sense.
- Data API for read-side dashboards instead of indexing.
Wallet model choice is the load-bearing decision: server wallets give you custody (easy UX, regulatory weight), smart wallets give the user custody with sponsored-gas UX (cleaner story, more code), embedded wallets blur the line with email/passkey auth (good for v1, may not be the v2 answer).
Gotchas
- CDP is the user-facing and infra surface, not the contract layer. Capital-bearing contracts still need an audit (Slither + Echidna + invariant tests, then paid audit before mainnet — the
web3-no-prod-capital-without-auditrule doesn't go away because CDP makes wallets easier). - Pick the wallet model per surface, not per app. A read-only dashboard wants embedded sign-in; a custodial automation needs a server wallet; a consumer dApp wants smart wallet + paymaster. Mixing models in one app is fine; reasoning about the auth flow once and forgetting which model you picked is not.
Risks
- Platform dependency. CDP is a single-vendor stack. If Coinbase gates a region or sunsets a surface, the dependent code path needs an exit. Worth knowing which surfaces have credible alternatives (RPC → Alchemy/QuickNode; embedded wallets → Privy/Dynamic; paymaster → Pimlico) before going deep.
- Regulatory exposure travels. Same surface as Base risks — CDP inherits Coinbase's regulatory posture. Not a Day-1 problem; a Year-2 problem if your user base spans jurisdictions.