WEB DATA & EXTRACTION · FOR AI AGENTS
Alchemy
Query blockchain nodes and indexed data through MCP, API or CLI.
Use Alchemy’s operated blockchain infrastructure for chain state, token data, transaction history and supported simulations, with account-based or documented wallet-funded access.
Your integration checklist
- Capabilities
- What you need from your owner
- Create an account and app for API or MCP access, or authorize an EVM wallet and USDC budget for the separate x402 gateway. Select the intended network and scope any wallet permissions separately.
- Authentication
- Hosted MCP at https://mcp.alchemy.com/mcp uses OAuth; select an app before RPC/data calls. Direct API requests use app credentials. The CLI’s x402 gateway route uses an EVM wallet with SIWE authentication.
- Your first task
- Select an app and network, retrieve a known address’s balance at an explicit block context and retain the chain and block with the result.
- Billing & payment
- Underlying account API usage is metered in compute units, with plan allowances and throughput limits. Agent tooling has no separate access fee. The wallet gateway funds API usage through USDC payments; inspect the current payment terms and bound top-ups.
- Agent payment support
- Alchemy documents wallet-funded API access through an x402 gateway. Its CLI uses an EVM wallet and SIWE, with USDC payment challenges. This is separate from third-party x402 payments and from OAuth MCP access. Approved funds and bounded payment authorization are required; payment execution was not tested.
- Operational limits
- Methods, data coverage and throughput depend on network and plan. Wallet authentication for Alchemy’s gateway is distinct from paying third-party x402 endpoints. A query result or successful simulation does not prove transaction finality or grant spending authority.
ORIGINAL AI AGENT STORE INTEGRATION PLAYBOOK
Bind blockchain observations to a chain, block and payment route
Editorial recommendation · Reviewed 2026-10-29
When to choose this service
Choose Alchemy when an agent needs operated nodes and indexed blockchain data without maintaining that infrastructure.
Synchronizing nodes, retaining historical state and maintaining indexes supplies external evidence and compute. An agent can analyze those observations but cannot recreate current chain state from general knowledge.
Suggested workflow
- Choose the exact network and app. Begin with a bounded read and verify the returned chain and block context.
- Preserve token units and contract addresses with amounts. Separate pending, included and finalized transaction states.
- If using wallet gateway access, authorize the budget and payment route explicitly. Keep API funding separate from permission to execute onchain writes.
Acceptance checks before real work
- Verify token decimals before presenting a human-readable amount.
- Confirm the requested method and historical window are supported.
- Reconcile payment and request outcomes before authorizing another top-up after an uncertain response.
If the workflow fails
Back off on throughput limits and check network or plan support for unsupported methods. Recheck a transaction by its identifier rather than resubmitting a transfer because a read timed out.