The Dwellir Alternative That Doesn’t Punish You for Growing

Dwellir bills one credit per response against a monthly quota, with extra credits or a bigger plan beyond it. SwiftNodes paid plans have no monthly quota: one flat rate by requests per second, card or crypto, 128 chains on one key.

Feature-by-feature: SwiftNodes vs Dwellir

Feature data sourced from Dwellir’s public pricing page and SwiftNodes’ own published rates. Last reviewed 2026-10-13. Pricing changes frequently — verify on the source site before deciding.

What the same traffic costs

• List prices from each provider's public pricing page, checked 2026-10-13, billed monthly (annual discounts not applied).
• Ethereum mainnet, typical dApp mix: 30% eth_call, 20% eth_getBalance, 15% eth_blockNumber, 15% eth_getTransactionReceipt, 15% eth_getLogs, 5% eth_sendRawTransaction.
• SwiftNodes plans cap requests per second, not monthly volume; each row uses the cheapest plan that covers a peak of twice the average rate for that volume.
• Dwellir: one credit per response regardless of method; eth_getLogs scans wider than the plan's block range are split and each part billed, which would raise these figures for log-heavy apps.

Switching from Dwellir: what changes in your code

Standard JSON-RPC and WebSocket calls need only a new URL. Your Dwellir endpoint:

https://api-ethereum-mainnet.n.dwellir.com/<API_KEY>
(or the key in an X-Api-Key header)

becomes:

https://rpc.swiftnodes.io/rpc/<chain>?key=YOUR_API_KEY
wss://rpc.swiftnodes.io/ws/<chain>?key=YOUR_API_KEY
(over HTTP the key can go in an x-api-key header instead; <chain> is eth, base, arbitrum, solana, ... see /docs/supported-chains)

Before

import { createPublicClient, http } from "viem";
import { mainnet } from "viem/chains";

const client = createPublicClient({
  chain: mainnet,
  transport: http("https://api-ethereum-mainnet.n.dwellir.com/YOUR_DWELLIR_KEY"),
});

After

import { createPublicClient, http, webSocket } from "viem";
import { mainnet } from "viem/chains";

const client = createPublicClient({
  chain: mainnet,
  transport: http("https://rpc.swiftnodes.io/rpc/eth?key=YOUR_API_KEY"),
});

// Subscriptions: same key over WebSocket
const ws = createPublicClient({
  chain: mainnet,
  transport: webSocket("wss://rpc.swiftnodes.io/ws/eth?key=YOUR_API_KEY"),
});

Point a staging deployment at SwiftNodes first and compare a few hundred real calls against Dwellir; standard JSON-RPC methods return the same chain data from any provider, so differences point at a real problem worth knowing about before you cut over.

Plans are month to month: you can run both providers side by side during the switch and cancel Dwellir when you are satisfied.

Measured, not claimed

Every week we call each method on every EVM chain through the same endpoint customers use, and publish the result. From the run on 2026-10-11:

• 107EVM chains probed weekly through the customer path
• 98serve debug_traceCall
• 51serve trace_block (Parity traces)
• 93serve archive state with &archive=1
• 82accept JSON-RPC batch requests

Per-chain detail is on the method support matrix and in the method reference, including what each chain actually returns for everyday calls such as eth_estimateGas and eth_subscribe.

Why developers switch from Dwellir to SwiftNodes

Frequently asked questions