The Brief
Alchemy is the infrastructure layer for blockchain development — providing production-grade Node APIs, indexed Data APIs, Smart Wallet tooling, and rollup deployment frameworks across more than 70 chains. The developer audience ranges from independent Web3 builders hitting their first RPC endpoint to engineering teams at scale deploying custom L2 rollups.
The documentation challenge at this scale is breadth without loss of depth. Alchemy’s platform spans fundamentally different product surfaces — low-level JSON-RPC node access, structured data indexing, account abstraction, and rollup infrastructure — each serving a different builder persona with a different mental model of what they’re trying to accomplish.
What I Built
Documentation across Alchemy’s core platform surfaces:
- Node API Reference — Clear, accurate endpoint documentation for JSON-RPC methods across supported chains, covering standard calls, WebSocket subscriptions, Trace API, Debug API, and Solana gRPC streaming — written so developers can move from the reference to a working integration without ambiguity
- Data API Guides — Developer-facing documentation for Alchemy’s structured blockchain data products: portfolio tracking, transfer histories, real-time token pricing, NFT data, and transaction simulation — framed around the use cases (dashboards, data-heavy applications, high-volume reads) rather than the internal data model
- Smart Wallet Documentation — Conceptual and reference documentation for Alchemy’s account abstraction infrastructure, covering smart contract accounts, bundler services, and gas sponsorship — a technically complex surface where clear conceptual framing matters as much as endpoint accuracy
- Getting Started Flows — Onboarding paths for each product area, structured so a developer new to the platform can reach a successful first API call before encountering the full reference
Approach
Blockchain infrastructure documentation has a specific challenge: the reader often arrives with strong opinions about how things should work — from prior experience with other node providers, from EVM conventions, from chain-specific assumptions. Good documentation meets them where they are and redirects quickly when Alchemy’s behaviour differs from expectation.
The approach across all workstreams was task-first: lead with what the developer is trying to accomplish, not with how the platform is internally structured. For the Data APIs especially, that meant organising around use cases (building a wallet portfolio view, tracking token transfers) rather than around API surface area.
Every code sample was tested against live endpoints. Every error response documented was a real one.
Results
Alchemy’s documentation serves one of the most technically demanding developer audiences in Web3 — builders who will immediately notice if something is wrong, underdocumented, or inconsistent with the actual API behaviour. Accurate, well-structured documentation at this level directly reduces friction for teams evaluating and adopting Alchemy’s infrastructure.