What is the Sui RPC URL?

The Sui Mainnet RPC URL with BoltRPC is https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/sui. Replace YOUR_API_KEY with your API key from dashboard.boltrpc.io and use standard Sui JSON-RPC methods against it.

Is Sui EVM compatible?

No. Sui runs its own Move-based execution with an object-centric data model. Clients use Sui JSON-RPC or the official SDKs, not ethers.js or MetaMask.

Does the official Sui SDK work with BoltRPC?

Yes. Create the client with your BoltRPC endpoint URL and all SDK calls work unchanged.

The object model lets transactions on unrelated objects execute in parallel and the Mysticeti consensus protocol reaches finality in a few hundred milliseconds.

What gas token does Sui use?

SUI, the native token, pays for gas. Part of the fee covers on-chain storage and is partially refunded when objects are deleted.

Why do public Sui fullnodes fail in production?

Public Sui fullnodes rate-limit aggressively per IP because consumer apps generate enormous read volume. Production applications need a dedicated endpoint with predictable throughput.

Sui RPC Endpoint

Sui settles transactions in under half a second on an object-centric Move architecture. Get a dedicated fullnode endpoint that keeps up.

JSON-RPCNative gRPCSynthetic WS

Start free trial Contact sales

LIVE LATENCY

17ms

LIVE

gateway round-trip · sampled every second

IN PRODUCTION AT Chainlink

Your endpoint, ready in one line.

Drop this URL into your RPC client, HTTP library or wallet config. No SDK install required.

HTTPS

https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/sui

WEBSOCKET

wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/sui

NATIVE gRPC

endpoints.boltrpc.io:443

Native gRPC over HTTP/2 with the official generated clients; send your API key in the x-api-key metadata header.

gRPC-WEB

https://endpoints.boltrpc.io/grpc/sui

Replace YOUR_API_KEY with your API key. Get a free key →

Pick your stack.

Copy-paste examples for the libraries you already use. Swap the API key, hit run.

import { SuiJsonRpcClient } from "@mysten/sui/jsonRpc";

const client = new SuiJsonRpcClient({
  url: "https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/sui",
  network: "mainnet",
});

const checkpoint = await client.getLatestCheckpointSequenceNumber();
console.log("Latest checkpoint:", checkpoint);

const url = "https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/sui";

const res = await fetch(url, {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    jsonrpc: "2.0",
    id: 1,
    method: "sui_getLatestCheckpointSequenceNumber",
    params: [],
  }),
});
console.log(await res.json());

curl https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/sui \
  -X POST \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","id":1,"method":"sui_getLatestCheckpointSequenceNumber","params":[]}'

Connect your dApp, bot, or indexer to Sui Mainnet with BoltRPC. Sui is the object-centric Move L1 with sub-second finality and predictable request-unit pricing keeps your RPC costs flat while your application reads one of the fastest-settling chains in production.

Chain at a Glance


Protocol	Move-based Layer 1, object-centric (Sui JSON-RPC)
Finality	Sub-second (Mysticeti consensus)
Data model	Objects with ownership (not accounts)
Gas token	SUI
Smart contracts	Move (Sui flavor)
EVM compatible	No

What Sui is Built For

Sui, built by Mysten Labs, rethinks the blockchain data model: instead of a global account tree, state lives in objects with explicit ownership. Transactions touching unrelated objects execute in parallel and simple transfers can skip full consensus entirely, which is how Sui reaches finality in a few hundred milliseconds. That speed and its object model have made it a home for gaming, consumer apps and increasingly deep DeFi. Clients talk to fullnodes over Sui JSON-RPC (sui_* and suix_* methods): familiar JSON-RPC mechanics with different method names than the EVM. Official SDKs for TypeScript, Rust and Python wrap it. Consumer-scale apps mean consumer-scale read volume and public fullnodes meet that with aggressive rate limits; production teams need a dedicated endpoint.

Sui native gRPC (Beta)

Sui’s official gRPC API (sui.rpc.v2, the interface Mysten is moving Sui nodes to) is served on the same endpoint, with Mysten’s generated clients (TypeScript, Rust, Go, Python) unchanged:

Native gRPC: endpoints.boltrpc.io:443 over HTTP/2, standard method paths such as /sui.rpc.v2.LedgerService/GetCheckpoint.
gRPC-Web for browser dapps, no proxy library needed: https://endpoints.boltrpc.io/grpc/sui.
Auth: your API key in the x-api-key metadata header.
Services: LedgerService (checkpoints, epochs, objects, transactions, batch reads), SubscriptionService (checkpoint, transaction and event streams), TransactionExecutionService (execute and simulate, at-most-once), MovePackageService (package and type introspection) and StateService (balances, owned objects, dynamic fields).

Billing follows the JSON-RPC table: a unary call costs what the matching JSON-RPC method costs, a BatchGetTransactions or BatchGetObjects call bills once (4 RU) whatever the number of items and server streams bill by delivered data at 1 RU per 24 KB, rounded up once per stream, with opening a stream free and five concurrent streams per key. Every weight is on the pricing page. The Beta label covers our endpoint’s coverage and limits, not the protocol.

Common Use Cases on Sui

Games and consumer applications Every player action reads and mutates objects. Backends resolve object state per interaction: sustained concurrent reads where per-IP rate limits are the first production incident.

DeFi backends DEXes and lending markets on Sui poll pool and position objects continuously, the same read-heavy pattern as EVM DeFi with object semantics.

Indexers and analytics Event indexers page through suix_queryEvents around the clock and backfill from checkpoints. Fixed per-method pricing keeps a continuous pipeline predictable on the invoice.

Wallets and portfolio trackers suix_getOwnedObjects and balance lookups run on every wallet open. Read latency here is perceived app speed.

Built for teams that ship on Sui.

Built for consumer-scale read volume

Games and consumer apps on Sui read object state per user, per action. A dedicated endpoint sustains that concurrency without the per-IP throttling public fullnodes apply.

Sub-second finality needs sub-second reads

Sui settles in a few hundred milliseconds; a slow RPC layer hands that advantage straight back. BoltRPC's gateway round-trip is measured continuously against our own nodes.

Official SDKs work unchanged

Point @mysten/sui's client URL at your BoltRPC endpoint and every SDK call works as-is, same for the Rust and Python SDKs. No proxy shims, no method translation.

Move ecosystem coverage from one provider

BoltRPC serves Sui alongside Aptos, the other major Move chain, plus Ethereum, Solana and every other network on the platform behind one dashboard and one key pattern.

Predictable pricing at app scale

Every method has a fixed, published request-unit weight. A viral day in your app changes the request count, not the pricing logic.

WebSocket checkpoint stream included

Sui fullnodes have no WebSocket API of their own, so BoltRPC synthesizes a newHeads stream: the latest checkpoint at sub-second cadence, at 3 request units per message. Indexers and wallets react to the latest checkpoint within about a second instead of polling sui_getLatestCheckpointSequenceNumber.

Full JSON-RPC coverage.

Every standard Sui method you would expect. Archive-only methods are available on request for qualifying plans.

STANDARD7

sui_getLatestCheckpointSequenceNumbersui_getObjectsuix_getBalancesuix_getOwnedObjectssui_getTransactionBlocksui_executeTransactionBlocksuix_queryEvents

Sui, explained.

Common questions about connecting to Sui over BoltRPC.

Ask a question →Read the docs

: The Sui Mainnet RPC URL with BoltRPC is https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/sui. Replace YOUR_API_KEY with your API key from dashboard.boltrpc.io and use standard Sui JSON-RPC methods against it.
: No. Sui runs its own Move-based execution with an object-centric data model. Contracts are written in Sui Move and clients use Sui JSON-RPC (sui_*/suix_* methods) or the official SDKs, not ethers.js or MetaMask.
: Yes. Create the client with your endpoint, new SuiClient({ url: "https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/sui" }) and all SDK calls work unchanged.
: Two things: the object model lets transactions on unrelated objects execute in parallel and the Mysticeti consensus protocol reaches finality in a few hundred milliseconds. Simple owned-object transfers take an even faster path.
: SUI, the native token, pays for gas. Sui also has a storage-fund mechanism: part of the fee covers on-chain storage, partially refunded when objects are deleted.
: Public Sui fullnodes rate-limit aggressively per IP because consumer apps generate enormous read volume. Production applications hit those ceilings quickly and need a dedicated endpoint with predictable throughput.
: Yes, for new checkpoints. Sui fullnodes have no WebSocket API of their own, so the endpoint synthesizes a newHeads stream (the latest checkpoint, sub-second cadence) at wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/sui, subscribed with eth_subscribe or the chain-neutral subscribe; regular JSON-RPC calls relay over the same socket. For event-driven workloads, poll suix_queryEvents with a cursor on each new checkpoint; it is the pattern Sui indexers use in production.

Ship on Sui this week.

An API key in under 60 seconds, Sui plus 35+ other chains, and a team that answers when you write.

Start free trial View pricing