Query blockchain data and manage Alchemy apps across 100+ chains using APIs, CLI, and MCP server, with wallet analytics from Allium and marketplace trading via OpenSea.
Wire Alchemy into application code without an API key, using the x402 or MPP gateway with wallet-based auth (SIWE/SIWS) and per-request payments (USDC via x402, or USDC/credit-card via MPP). Specialized app-integration path. Use when the user is building application code AND no API key is available, or they're an autonomous agent that needs to pay for itself, or they explicitly want x402/MPP. For normal app code with an API key, use `alchemy-api`. For live agent work in this session (querying, admin, automation), use `alchemy-cli` (preferred) or `alchemy-mcp`.
Wire Alchemy into application code (server, backend, dApp, script) using a standard API key. Preferred app-integration path for normal server/backend usage. Covers EVM JSON-RPC, Token API, NFT API, Transfers API, Prices API, Portfolio API, Simulation, Webhooks, Solana RPC, Solana DAS, Solana Yellowstone gRPC, Sui gRPC, Wallets/Account Kit, and operational topics. Requires `$ALCHEMY_API_KEY`. For live agent work in this session (querying, admin, local automation), use `alchemy-cli` (preferred) or `alchemy-mcp` instead. For app code without an API key (autonomous agent paying per-request, or explicit x402/MPP), use `agentic-gateway` instead.
Use the Alchemy CLI (`@alchemy/cli`) for live blockchain data, transaction lookups, NFT/token/portfolio queries, simulation, tracing/debugging, account abstraction (bundler + gas manager), webhook management, Solana RPC/DAS, and Alchemy app administration. Preferred runtime path for live agent work (querying, admin, local automation) when the CLI is installed locally — or when both CLI and MCP are available. If neither is installed, install the CLI with `npm i -g @alchemy/cli`. Use for live agent work in this session, not for building application code that ships to production. For application code, use the `alchemy-api` skill (with API key) or `agentic-gateway` skill (without).
Use the Alchemy MCP server (`https://mcp.alchemy.com/mcp`) for live blockchain data and admin work when MCP is wired into your AI client and the Alchemy CLI is NOT installed locally. Exposes 159 tools across 100+ chains for token prices, NFT metadata, transactions, simulation, tracing, account abstraction, Solana DAS, and app management. Use for live querying, analysis, admin work, or on-machine agent work — not for application code that ships to production. For application code, use the `alchemy-api` skill (with API key) or `agentic-gateway` skill (without). When the CLI is also installed locally, prefer `alchemy-cli` instead.
Query Allium APIs for wallet PnL (current + historical, by-wallet and by-token), holdings timeseries history, Hyperliquid HyperCore trading data (info, fills, orders, orderbook), and custom SQL analytics across 70+ chains. NOT for token prices, token metadata, current wallet balance snapshots, transaction transfer history, or NFT metadata — for those use `alchemy-cli` (live work), `alchemy-mcp`, `alchemy-api` (app code), or `agentic-gateway` (no API key). Requires Allium credentials at `~/.allium/credentials`.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Agent Skills for using Alchemy — both for live agent work done in the current session (one-off queries, admin, automation) and for wiring Alchemy into application code that ships.
Pick the right skill in two questions:
flowchart TD
Start(["Want to use Alchemy"]) --> Q1{"Live agent work<br/>or app code?"}
Q1 -->|"Live work<br/>queries, admin, automation<br/>in this session"| Q2{"Local setup?"}
Q1 -->|"App code<br/>that ships outside<br/>this session"| Q3{"Have an<br/>API key?"}
Q2 -->|"CLI installed<br/>(or both CLI and MCP)"| CLI["<b>alchemy-cli</b><br/>preferred local fallback"]
Q2 -->|"Only MCP wired in,<br/>no CLI"| MCP["<b>alchemy-mcp</b><br/>hosted MCP server"]
Q2 -->|"Neither available"| Install["Install the CLI"] --> CLI
Q3 -->|"Yes, or willing<br/>to create one"| API["<b>alchemy-api</b><br/>preferred app-integration path"]
Q3 -->|"No key, but<br/>@alchemy/cli installed"| Bridge["Use CLI to fetch a key<br/>from the user's account"] --> API
Q3 -->|"No, autonomous agent,<br/>or explicit x402/MPP"| GW["<b>agentic-gateway</b><br/>specialized"]
| What you're doing | Use this skill |
|---|---|
Live agent work + @alchemy/cli is installed locally | alchemy-cli (preferred local fallback) |
Live agent work + both @alchemy/cli and an MCP server are available | alchemy-cli (CLI is preferred when both are available) |
| Live agent work + only an MCP server is wired into the client (no CLI) | alchemy-mcp |
| Live agent work + neither is available | install @alchemy/cli (npm i -g @alchemy/cli), then use alchemy-cli |
| App code + you have or can create an Alchemy API key | alchemy-api (preferred app-integration path) |
App code + no API key in env, but @alchemy/cli is installed locally | alchemy-api after using the CLI to fetch a key (alchemy auth login → alchemy apps select → alchemy --reveal config get api-key) |
| App code + no API key, autonomous agent paying per-request, or you explicitly want x402/MPP | agentic-gateway (specialized) |
Each skill self-routes — its When to use this skill / When to use a different skill sections will redirect you if you land on the wrong one.
The Alchemy CLI is the preferred local fallback runtime path for live agent work. The MCP server is the preferred runtime path for AI clients only when the CLI is not installed.
skills/alchemy-cliLive agent skill for the local @alchemy/cli. Maps every Alchemy product (Node, Token, NFT, Transfers, Prices, Portfolio, Simulation, Solana, Webhooks, Apps) to alchemy <command> invocations with structured JSON output.
npm i -g @alchemy/cli, then alchemy auth loginskills/alchemy-cli/SKILL.mdskills/alchemy-mcpLive agent skill for the hosted Alchemy MCP server (https://mcp.alchemy.com/mcp). Exposes 159 tools across 100+ chains. OAuth flow handled by the client; no API key or local install required.
skills/alchemy-mcp/SKILL.mdskills/alchemy-apiApp-integration skill for wiring Alchemy into application code that ships, using a standard API key. Covers the full Alchemy surface: EVM JSON-RPC, WebSockets, Token, NFT, Transfers, Prices, Portfolio, Simulation, Webhooks, Solana, Solana Yellowstone gRPC, Sui gRPC, Wallets/Account Kit, and operational topics.
skills/alchemy-api/SKILL.mdskills/agentic-gatewaySpecialized app-integration skill for app code without an API key. Uses Alchemy's gateway with wallet-based auth (SIWE for EVM, SIWS for Solana) and per-request payments (USDC via x402, or USDC/credit-card via MPP).
Query blockchain data across 100+ chains and manage Alchemy apps — token balances & prices, NFTs, transfers, transactions, gas, and Solana — directly in Claude Code and Cowork.
npx claudepluginhub alchemyplatform/skillsClaude Code skill pack for Alchemy (18 skills)
Blockchain RPC access for AI agents — 200+ networks via DRPC MCP gateway
Blockchain data and infrastructure via Alchemy — EVM/Solana RPC, NFT API, token prices, portfolio, transfers, webhooks. Supports API key and agentic gateway (x402/MPP) auth flows.
Hive Intelligence — agent-facing crypto intelligence MCP. Market data, DeFi, wallets, token security, DEX flows, NFTs, Solana, network infrastructure, and prediction markets via a hosted MCP server.
Zerion skills and slash commands for AI coding agents — wallet analysis, swaps/bridges, chain reference, agent-token policies.
Claude Code bridge for the existing AgentLayer wallet runtime. Connects to Solana, Bitcoin, and EVM wallets without creating a new one.