Uniblock: one API key over 55+ RPC providers and 300+ chains (incl. Solana)

Most production multi-chain apps end up with a drawer of API keys: Helius for Solana, Alchemy or Infura for EVM, CoinGecko for prices, Solscan for explorer-shaped queries, and a half-finished failover layer someone wrote at 2 a.m. after a provider outage. Uniblock is the product version of that drawer — one key, one bill, automatic routing across 55+ providers and 300+ chains, including Solana.

Alliance-backed, free to start (up to 40M compute units / month), docs at docs.uniblock.dev. Here is what it actually is for Solana builders, and where it is not a drop-in for a specialist RPC.

Click to zoom

What Uniblock is

A unified blockchain API layer, not another single-provider node host. You integrate api.uniblock.dev once; Uniblock owns provider selection, retries, failover, response normalization, and billing aggregation. The homepage pitch is blunt: stop spending engineering time on provider selection and uptime monitoring.

The stack breaks into a few surfaces:

• Unified APIs — REST under /uni/v1/… for tokens, NFTs, market data, transactions, and explorer-style scans, with normalized response shapes.
• JSON-RPC gateway — POST /uni/v1/json-rpc?chainId=… for chain-native methods (EVM eth_*, Solana getBalance / getSlot / sendTransaction, plus Sui, Bitcoin, Starknet, and many others).
• Direct APIs — provider-specific endpoints when you need methods that are not yet in the unified schema (Helius enhanced transactions, Birdeye trades, Polymarket, etc.).
• Webhooks, websockets, MCP, dedicated nodes — the same account grows into events, streams, agent tooling, and isolated capacity without a new vendor.

Auto-routing is the product

Click to zoom

Auto-routing is on by default for every API key. On each request Uniblock scores available providers for that method, sends the primary call, retries on failure, then failovers to the next provider. Higher plans add routing optimization, dynamic distribution, and optional data consensus (query multiple providers and reject outliers — useful for prices, costs ~100–200ms).

You can pin a provider when you need determinism: pass ?provider=Helius (or Alchemy, QuickNode, Shyft, …) on the JSON-RPC query string. Everything else stays the same key and base URL.

Oku Trade's published case study claims they folded a self-built RPC routing layer into Uniblock and saw roughly 30% lower RPC cost plus less ops overhead. Treat that as marketing-grade evidence, but the shape matches what auto- routing is for.

Solana path: three doors

Click to zoom

Solana is a first-class chainId on the JSON-RPC gateway: solana for mainnet, solana-devnet for devnet. Auth is the same header as everywhere else: X-API-KEY.

# Solana getSlot via Uniblock JSON-RPC
curl -s 'https://api.uniblock.dev/uni/v1/json-rpc?chainId=solana' \
  -H 'content-type: application/json' \
  -H 'X-API-KEY: YOUR_API_KEY' \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "getSlot",
    "params": []
  }'

# Optional: pin Helius for this call
# ...json-rpc?chainId=solana&provider=Helius

The method enum on that endpoint includes the usual Solana surface — accounts, blocks, signatures, tokens, simulateTransaction, sendTransaction, DAS-style getAsset / getAssetsByOwner when the upstream supports them, and more. For explorer and analytics shapes you leave pure JSON-RPC and hit Direct APIs for Solana-heavy providers already wired in: Helius, Solscan, HelloMoon, Shyft, Magic Eden, Birdeye, plus multi-chain shops (Moralis, GoldRush, Covalent) when their Solana coverage is enough.

Events: there is a dedicated Create Solana Address Webhook path in the webhook API, and Helius websockets are documented for Solana streaming. Market data (price, market cap, 24h volume, history, trending) sits under /uni/v1/market-data/… and is chain-agnostic when you pass the right identifier.

Minimal REST call

Unified endpoints look like ordinary REST. Header auth, chainId as a query param (numeric for EVM, string for Solana and other non-EVM nets):

const res = await fetch(
  "https://api.uniblock.dev/uni/v1/token/balance?chainId=1&walletAddress=0x…",
  {
    headers: {
      accept: "application/json",
      "X-API-KEY": process.env.UNIBLOCK_API_KEY!,
    },
  },
)
const { balances } = await res.json()
// balances: [{ contractAddress, balance }, …] + cursor

Dashboard flow is under ten minutes: create a project at dashboard.uniblock.dev, copy the key, exercise endpoints in the built-in API Tester / Explorer, then watch routing and latency under Analytics.

Pricing shape (as of mid-2026)

Public plans are CU-metered (compute units), not per-chain seats:

• Free — $0, up to ~40M CUs/mo, 1k CU/s, 2 projects, basic routing.
• Growth — ~$40–49/mo, ~500M CUs, optimized routing.
• Pro — ~$180–199/mo, ~2B CUs, higher parallelism, premium support.
• Business — ~$500–549/mo, ~5.5B CUs, unlimited projects, max routing automation.
• Enterprise — custom SLAs, dedicated nodes, priority routes.

Annual billing discounts up to ~20%. There is a pricing calculator. Free tier is for prototypes; docs are explicit that production wants Growth+.

Where it sits for Solana builders

Compare layers carefully — Uniblock is not a clone of Helius:

• Use Uniblock when you already span EVM + Solana (or more), hate multi-invoice ops, want failover without writing it, or need market data and webhooks under the same key as RPC.
• Stay on a Solana specialist when you need the absolute deepest DAS, priority fee APIs, Geyser-grade streams, or provider-specific features the day they ship — pin provider=Helius through Uniblock, or go direct.
• Unified token/NFT REST is still more EVM-native in naming (ERC-20/721 shapes, numeric chain IDs). On Solana you will spend more time in json-rpc and Direct APIs than in the ERC-shaped catalog — that is fine, just do not expect one/token/balance call to replace getTokenAccountsByOwner.
• Related reading on this site: Solana RPC providers, Helius webhooks, DAS API.

Resources

• Site: uniblock.dev
• Docs: docs.uniblock.dev · llms.txt
• Dashboard: dashboard.uniblock.dev
• Integrations: provider list (Alchemy, Helius, QuickNode, Solscan, Birdeye, …)
• X: @Uniblock

TL;DR

• Uniblock = multi-provider orchestration API with auto-routing, normalized REST, JSON-RPC, Direct APIs, webhooks, websockets, MCP.
• Solana is real: chainId=solana, Solana-specific webhooks, and Direct access to the Solana provider set you already know.
• One key and one invoice is the win. Deepest Solana edges still live at the specialist — pin or go direct when you need them.