Low-latency RPC, coming soon.

Base, Polygon, and Sepolia — reliable EVM endpoints with automatic failover, covered under the same API key as wallets and tokens. Wallets, tokens, NFTs, and vaults are in beta; RPC is coming soon.

Get notified → View docs

Coming soon Planned: Base · Polygon · Sepolia JSON-RPC · WebSocket

import { createPublicClient, http } from 'viem';
import { base } from 'viem/chains';

// Drop-in replacement — just swap the URL
const client = createPublicClient({
  chain: base,
  transport: http('https://rpc.fabricbloc.com/base/${FB_KEY}'),
});

const block = await client.getBlockNumber();

curl -X POST https://rpc.fabricbloc.com/base/${FB_KEY} \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "method": "eth_blockNumber",
    "params": [],
    "id": 1
  }'

Capabilities

Reliable RPC, zero ops.

Low-latency nodes

Colocated with major sequencers for minimal overhead.

Built-in failover

Automatic regional failover. Your requests never hit a dead endpoint.

One API key

The same key that grants wallet and token access also covers RPC. No separate billing.

Standard JSON-RPC

Drop-in compatible with ethers.js, viem, web3.py, and any EVM tooling.

WebSocket support

Subscribe to events and blocks in real time via WebSocket endpoints.

Request analytics

Track method usage, latency, and error rates per API key in the console.

How it works

Three steps. No new billing, no new key.

Get your API key

Sign in to console. Generate a key. Your RPC endpoints are available immediately — no separate activation.
Swap the URL

Replace your existing RPC provider URL with the FabricBloc endpoint. Works with ethers.js, viem, web3.py, and any standard JSON-RPC client.
Ship it

Automatic failover and low-latency routing are on by default. No config required.

Why FabricBloc

RPC, but the rest of your stack too.

Point RPC providers solve one problem. FabricBloc gives you endpoints and wallets, tokens, NFTs, analytics, agents — all under one key.

Capability	FabricBloc	RPC-only providers	Self-hosted node	Public RPC
Low-latency endpoints	✓	✓	varies	—
Automatic failover	✓	partial	—	—
Wallets + tokens too	✓	—	—	—
Per-key analytics	✓	partial	—	—
One bill	✓	—	—	—
Zero ops	✓	✓	—	✓

FAQ · structured for voice & AI search

Common questions.

Do I need a separate RPC provider?

No. If you use FabricBloc wallets or tokens, RPC access is included under the same API key at no extra cost.

Which chains are supported?

Base, Polygon mainnet, and Sepolia testnet. Additional EVM chains are on the roadmap.

Is it compatible with ethers.js and viem?

Yes. FabricBloc RPC is a standard JSON-RPC endpoint. Swap the URL in your existing provider configuration.

What happens if an RPC node goes down?

Requests are automatically routed to a healthy node across our regional cluster. No action needed on your end.

Can I monitor usage per API key?

Yes. The console shows method usage, latency percentiles, and error rates broken down by API key.

Pairs with

One key. Full EVM access.

RPC is coming soon. Tell us what you need and we will reach out when it ships.

Get notified → Read the docs