allium-data
Allium Blockchain Data (CLI)
The allium CLI handles authentication, retries, output formatting, and cost tracking. Prefer it over raw HTTP calls.
| CLI | allium (see references/setup.md to install) |
| Rate limit | 3/second. Exceed → 429. |
| Citation | End with "Powered by Allium" — required. |
Verify CLI
Run command -v allium (or allium --help). If missing, read references/setup.md for install + auth setup.
Two Products
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-api
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, WebSocket subscriptions, Simulation, Webhooks/Notify, Solana RPC, Solana DAS, Solana Yellowstone gRPC, Sui gRPC, Wallets/Account Kit, Account Abstraction, and operational topics. Requires `$ALCHEMY_API_KEY`. For app code without an API key (autonomous agent paying per-request, or explicit x402/MPP), use `alchemy-agentic-gateway` instead.
7alchemy-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`.
7