Alchemy

• Name: Alchemy
• URL: https://www.alchemy.com/
• Category: blockchain developer platform / RPC infrastructure / data APIs / smart-wallet and rollup tooling company
• Tags: ethereum-ecosystem solana-ecosystem
• Summary: Alchemy belongs as an entity note, not a protocol note. The useful cut is that a named company operates a broad developer control plane spanning RPC, data, webhooks, wallet tooling, and rollup-adjacent products. The practical leverage comes from routing, retries, sponsorship, webhook state, and chain-support defaults that developers inherit by integrating the managed stack.
• What it does:
  • Provides blockchain infrastructure and node access for developers building on Ethereum, Solana, and many EVM chains, with the homepage emphasizing reliability and scale rather than only endpoint resale
  • Offers real-time and historical blockchain data products, WebSocket subscriptions, and webhook-based push notifications so teams can track onchain activity without constant polling
  • Ships wallet infrastructure and Account Kit / smart-wallet tooling for gas sponsorship, ERC-20 gas payments, batching, retries, session keys, status tracking, and embedded-wallet integrations
  • Exposes orchestration-style transaction flows such as swaps, staking-oriented flows, and multi-step transaction handling through higher-level wallet APIs
  • Maintains a substantial docs surface organized around Node, Data, Wallets, Webhooks, Rollups, and Chains, plus public SDK repositories that make the developer surface area concrete
• Key claims:
  • The homepage says Alchemy handles $4.2T+inannualtransactions,serves100M+humansusingcrypto,hasprocessed$1B+ in gasless transactions, and delivers 99.99% uptime
  • The docs homepage markets Alchemy as a place to Build anything onchain and highlights real-time webhook delivery across 80+ chains, gas sponsorship, and reliable transaction submission with built-in retries and status tracking
  • The Wallet APIs docs describe support for gas sponsorship, ERC-20 gas payments, Solana sponsorship, transaction batching, automatic retries, session keys, token swaps, and transaction debugging
  • The Wallet APIs supported-chains page says Alchemy provides wallet infrastructure on major EVM chains plus Solana, and that new chains can be added on request
  • The docs llms.txt presents Alchemy’s product surface as Node APIs, Data APIs, Webhooks, Smart Wallets, Rollups, and Chains, which is a strong first-party signal that the company should be cataloged as a broad developer platform rather than only an RPC vendor
• Whitepaper: No classic whitepaper or litepaper was found during this pass. The strongest primary materials were Alchemy’s official site, docs index, wallet docs, webhook docs, supported-chain docs, and public SDK repositories; see ../whitepapers/alchemy-primary-sources-2026-04-26.md.
• Sources:
  • https://www.alchemy.com/
  • https://www.alchemy.com/docs
  • https://www.alchemy.com/docs/llms.txt
  • https://www.alchemy.com/docs/wallets
  • https://www.alchemy.com/docs/wallets/supported-chains
  • https://www.alchemy.com/docs/reference/notify-api-quickstart
  • https://github.com/alchemyplatform
  • https://raw.githubusercontent.com/alchemyplatform/aa-sdk/main/README.md
  • https://raw.githubusercontent.com/alchemyplatform/alchemy-sdk-js/main/README.md

Internal linkages

• Alias / prior project-layer entry: alchemy.
• Keep this note pointed at the strongest operator-platform contrasts: coinbase-developer-platform, safe, and walletconnect.
• Reusable lens: when a team says wallet infra, the real leverage often sits in managed routing, retries, webhook state, sponsorship policy, and chain-support defaults.

Protocol / company boundary

• alchemy is intentionally only an alias because there is not a very useful standalone Alchemy protocol boundary doing separate analytical work here.
• The important surface is the company-run operator shell: RPC routing, webhook delivery, sponsorship policy, wallet and smart-account defaults, supported-chain coverage, and the broader dashboard and API workflow developers inherit.
• That is why the canonical note lives in companies/: the durable dependency is on Alchemy as a named operator, not on a neutral lower-layer primitive.

Control surface

• Practical leverage sits in routing, retries, sponsorship policy, webhook state, supported-chain coverage, and how much of a team’s execution path hardens around Alchemy-specific APIs.

• Read it as managed developer middleware with a lot of room to turn product defaults into operator power.

• Last reviewed: 2026-08-09 UTC