Starknet RPC Endpoint

Flat-rate Starknet RPC provider and Starknet RPC node access: free tier, no KYC, HTTP & WebSocket.

Starknet mainnet RPC URL: https://rpc.swiftnodes.io/rpc/starknet?key=YOUR_API_KEY
WebSocket: wss://rpc.swiftnodes.io/ws/starknet?key=YOUR_API_KEY

Starknet is a validity (ZK) rollup on Ethereum that uses STARK proofs to verify state transitions. Contracts are written in Cairo rather than Solidity, and it is non-EVM at the execution layer.

Network: Starknet
Type: Non-EVM
Slug: starknet
Native token: STRK (Starknet Token)
Block time: Variable block production; not a fixed EVM-style interval
Finality: Soft confirmation on Starknet within seconds to minutes; hard finality once the STARK proof is verified on Ethereum L1
Mainnet: 2021 (mainnet); STRK token February 2024
Category: Layer 2 (STARK validity rollup on Ethereum)

Starknet on the SwiftNodes fleet, right now

Status: online
Latency: 63 ms
Latest block: 16,140,228
WebSocket: available

Status and latency from our health checks, refreshed about every 5 minutes. Uptime history. Network status

About Starknet

Starknet launched its mainnet in 2021 and is built by StarkWare. It is a validity rollup: every state update is accompanied by a STARK proof verified on Ethereum, giving cryptographic correctness once proofs settle to L1.

Smart contracts are written in Cairo and run on the Starknet OS, not the EVM. The native STRK token launched in February 2024 and is used for fees and staking. Tooling includes Starkli, scarb, and starknet.js.

Common Use Cases on Starknet

  • Scalable DeFi
  • Account abstraction wallets
  • Gaming
  • Provable computation
  • Low-cost transactions

Starknet Ecosystem

Starknet hosts native DeFi and infrastructure projects such as Ekubo, Nostra, and the Argent and Braavos smart-account wallets.

Starknet Mainnet RPC URL (HTTP)

https://rpc.swiftnodes.io/rpc/starknet?key=YOUR_API_KEY

Starknet WebSocket RPC URL

wss://rpc.swiftnodes.io/ws/starknet?key=YOUR_API_KEY

Quick Start: Connect to Starknet

cURL

curl -X POST https://rpc.swiftnodes.io/rpc/starknet?key=YOUR_API_KEY \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"getHealth","id":1}'

Note: Starknet uses its own RPC methods. Refer to the official Starknet documentation for available methods.

Bridging to Starknet

The StarkGate canonical bridge connects Ethereum and Starknet; third-party bridges including Orbiter and rhino.fi also support transfers.

Features of SwiftNodes for Starknet

  • Load-balanced across multiple upstream nodes wherever a chain has more than one, with automatic failover
  • Health-checked every 2 minutes with automatic failover
  • Free tier available — no credit card or KYC required
  • Flat-rate monthly pricing with no per-request fees
  • HTTP and WebSocket support
  • One API key works across all 75+ supported chains, including Starknet

Rate Limits

PlanPriceHTTP req/sWS msg/s
Free$0/mo21
Starter$49/mo5025
Growth$89/mo15075
Scale$149/mo300150
Pro$249/mo500250

Frequently Asked Questions: Starknet

Does Starknet have an EVM chain ID?

No. Starknet is non-EVM and does not use an EVM chain ID. It identifies networks with its own chain identifiers (for example SN_MAIN for mainnet).

How do I query Starknet?

Starknet exposes a dedicated Starknet JSON-RPC API (distinct from Ethereum JSON-RPC) accessed via libraries like starknet.js and starknet.py; it does not respond to standard Ethereum eth_ methods.

What language are Starknet contracts written in?

Starknet contracts are written in Cairo and run on the Starknet OS rather than the EVM.

Starknet guides from the blog

  • Which Chains Stopped? 43 Days of Block Timestamps Across 110 ChainsBetween August 25 and October 6, 2026, ten of 110 chains we scanned stopped producing blocks for 10 minutes or more. TAC was down 10.6 days, Neutron 77.75 hours, Cosmos Hub 24.8 hours, Cronos 17 hours. The full list, the method, and the raw data.
  • Starknet RPC: JSON-RPC, but Not EVM MethodsStarknet is a non-EVM validity (ZK) rollup where contracts are Cairo, not Solidity. The RPC is JSON-RPC over HTTP — but it's the starknet_* namespace, not eth_*, so viem/ethers/foundry don't connect. Accounts are contracts (native AA, no EOAs), values are felts, and finality comes from STARK proofs with no challenge window. Here's the developer map, including the eth_* → starknet_* method translation.

Related chains

Explore RPC endpoints for other networks on SwiftNodes:

Ready to start building on Starknet? Connect your wallet and get a free API key in 30 seconds. No email or KYC required.