alchemy-api
Alchemy API (with API Key)
Reference and integration guide for wiring Alchemy APIs into application code using a standard API key. This file alone is enough to ship a basic integration; the references/ directory contains deeper coverage of every product surface.
When to use this skill
Use alchemy-api when all of the following are true:
- The user is wiring Alchemy into application code (server, backend, dApp, worker, script) that runs outside the current agent session
- They have, or are willing to create, an Alchemy API key (free at dashboard.alchemy.com)
This is the preferred app-integration path for normal server/backend usage.
When to use a different skill
| Situation | Use this skill instead |
|---|---|
Live agent work in this session (queries, admin, on-machine automation) and @alchemy/cli is installed locally — or both CLI and MCP are available |
alchemy-cli |
| Live agent work in this session and only MCP is wired into the client (no CLI) | alchemy-mcp |
| Live agent work and neither is available | install alchemy-cli and use alchemy-cli |
More from allium-labs/skills
allium-onchain-data
>-
48allium-x402
>-
36dune-to-allium
Convert Dune (Trino) SQL queries to Allium (Snowflake) SQL. SQL dialect conversions (Trino → Snowflake) apply to all chains. Comprehensive Solana and EVM chain mappings included.
8alchemy-agentic-gateway
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 Alchemy API key, use `alchemy-api`.
7allium-data
>-
5