Allium: enterprise blockchain data — Explorer, Realtime APIs, MCP, and Beam

Allium: enterprise blockchain data — Explorer, Realtime APIs, warehouse shares, streams, Beam pipelines, and agent surfaces (MCP + machine payments) across 80+ chains, including Solana.

Docs: docs.allium.so (llms.txt). App: app.allium.so. Site: allium.so. Status: status.allium.so. X: @AlliumLabs.

Click to zoom

What problem it owns

Raw chain data is messy, multi-format, and expensive to keep correct through reorgs. Allium sells a full stack so analytics, eng, and accounting teams do not each rebuild indexers: historical schemas you can SQL, low-latency REST for products, and push paths into your bus or warehouse. Marketing cites production use at large wallets and DeFi names (e.g. Phantom, Uniswap, Circle, MetaMask on Beam materials) — treat as positioning; verify SLAs on your plan.

Product map (pick by job)

Full comparison matrix: product comparison. Historical catalog spans raw, decoded, DEX, balances, NFTs, stablecoins, and more under Data Catalog.

Realtime APIs (builder default)

Public signup is open for Realtime. Docs list 20+ chains including Solana for pull REST, with p50 freshness around 3–5 seconds, reorg handling, and high RPS claims for peak load.

Verticals:

• Prices — latest, history, stats from DEX trade feeds
• Tokens — metadata, search, transfers
• Wallets — balances, txs, historical balances
• Holdings — wallet PnL (current + historical, by token)
• DeFi positions — pools, lending, staking-style NAV / health
• Market data — OHLCV, funding, OI, liquidations (where listed)
• Hyperliquid — dedicated fills / orderbook surfaces

Also: Explorer API to run saved SQL programmatically; Datastreams API to manage filters/workflows; account usage endpoints.

Auth quickstart

1. Sign up at app.allium.so/join
2. Settings → API Keys → generate (docs: one key per user — store server-side)
3. Send header X-API-KEY: <key>

# shape only — path/params follow current OpenAPI in docs
curl -s "https://api.allium.so/api/v1/..." \
  -H "X-API-KEY: $ALLIUM_API_KEY" \
  -H "Accept: application/json"

# supported realtime chains (live list)
curl -s "https://api.allium.so/api/v1/supported-chains/realtime-apis"

Walkthrough: Getting Started. Always re-check path versions against docs — Allium iterates API surfaces.

Beam and Datastreams

Datastreams push chain events to Kafka / Google Pub/Sub / Amazon SNS / websockets with optional transforms.

Beam sits on top: pick a stream source → filter / JS transform → sink, aimed at “deploy in ~30s” wallet alerts and contract monitors without standing up a full firehose consumer. Pattern:

Allium Datastream source
        → filter (wallets / programs / mints)
        → transform
        → Kafka | SNS | external Kafka

AI, MCP, and machine payments

Agents get first-class entry points:

• MCP server: https://mcp.allium.so — Explorer SQL, schema introspection, realtime tools. Installer: npx @allium-labs/mcp install (Claude Code, Cursor, VS Code, Windsurf, …).
• In-app Assistant with org memory and docs-aware capabilities.
• Machine payments: x402 (EIP-712 / USDC-style negotiation), Tempo MPP, agent skills (npx skills add allium-labs/skills), early allium-cli installer for agent setup.

That puts Allium in the same agent-data lane as Elfa / Range MCP, but oriented at multi-chain warehouse + SQL rather than pure risk scoring.

Solana builder angles

• Portfolio / PnL apps — Holdings APIs instead of stitching every DEX yourself.
• Wallet activity product — wallet balances + txs at multi-second freshness; Beam filters for push notify.
• Internal analytics — Datashare Solana tables next to Stripe/CRM in Snowflake/BQ.
• Agent research — MCP over Explorer for “who moved what” without writing a new indexer.

Compare with chain-native stacks (Helius DAS/webhooks, Yellowstone gRPC, TopLedger) when you need Solana-only depth or lower-level streams; use Allium when multi-chain sameness and warehouse/SQL matter more than raw Geyser shape.

Org features

App side includes SSO/SAML, MFA, IP allowlists, secrets, compute profiles, usage/billing, parameterized queries, and charting — i.e. data-team packaging, not just a raw API key page.

Practical start

1. Join + create API key.
2. Hit Realtime wallet or token endpoints for a known Solana address; confirm freshness meets your UX.
3. If you need SQL history, run the same question in Explorer and save the query for the Explorer API.
4. For notifications, prototype a Beam filter on transfers to your mint / program set.
5. Point coding agents at MCP with a scoped key; never embed keys in client bundles.

Resources

• Documentation hub
• API getting started · Realtime overview
• Product comparison
• MCP overview · x402
• Beam · Datastreams
• Elfa · Range · TopLedger
• Allium on DevRels

Bottom line

Allium is a full-funnel chain data vendor: warehouse and Explorer for analysts, Realtime REST for products (Solana included), streams/Beam for ops, MCP and x402 for agents. Start with an API key and one Realtime wallet/token call; graduate to Datashares or Beam when SQL or filtered push becomes the bottleneck — and keep a Solana-native indexer in your back pocket when you need Geyser-level control.