New RPC users get 35% off their first monthView the offer
Sonic RPC Endpoint and API
A high-performance EVM Layer 1 with sub-second finality and high throughput for next-generation dApps.
Sonic is a high-performance EVM Layer 1 with sub-second finality and high throughput for next-generation dApps. Its EVM compatibility supports DeFi, wallets, games, and backend services while fast confirmation keeps interactive apps responsive.
Chain ID146
CurrencyS
Create a free API key for 400,000 response units per day and up to 40 response units/second. Method weights apply.
Connect fast-moving EVM app backends to Sonic with OnFinality RPC. Track contract events, read archive state and trace transactions for trading and DeFi tools.
Plan figures checked 8 November 2026. RU are not always raw requests; WebSocket responses also count toward limits. Check the current pricing and this network's method documentation. Node charges and applicable taxes are additional.
NETWORK REFERENCE
Sonic RPC Endpoints
Sonic is a high-performance EVM Layer 1 with sub-second finality and high throughput for the next generation of decentralized applications. Its Ethereum compatibility makes it straightforward to reuse Solidity contracts and familiar tooling.
DeFi, wallets, games, NFTs, analytics, and backends
Quick RPC check
Start with eth_blockNumber, then test contract reads, logs, receipt polling, transaction submission, WebSocket reconnects, and the historical queries your application requires.
What to validate before production
Check read latency, transaction finality, log behavior, retries, WebSocket stability, archive or trace requirements, and whether production traffic needs authenticated or higher-capacity access.
NETWORK REFERENCE
Sonic RPC use cases
Sonic RPC supports DeFi applications, wallets, games, NFT tools, trading systems, analytics pipelines, and backend services that need fast EVM-compatible access.
NETWORK REFERENCE
OnFinality Sonic RPC features
Transport: HTTPS and WebSocket
Advanced access: Archive and trace methods available
Observability: Request analytics and usage visibility
Scaling path: Shared access for integration and higher capacity for production workloads
NETWORK REFERENCE
Sonic production workflow
Validate contracts, wallet flows, logs, receipts, transaction submission, and WebSocket behavior in staging before moving traffic to Sonic Mainnet. Review capacity and monitoring needs before relying on a shared endpoint for sustained production traffic.
NETWORK REFERENCE
Sonic RPC resources
Sonic teams should test both EVM compatibility and fast transaction workflows, especially when a product depends on frequent reads, live updates, or high-throughput backend jobs.
Best fit: mainnet production workflows for DeFi, wallets, games, analytics, and EVM backends.
What builders usually check first:
Read current chain state and contract data with standard Ethereum JSON-RPC methods.
Submit transactions and monitor receipts from wallets, services, and bots.
Query logs and historical state for analytics or operational tooling.
Validate WebSocket reconnects and request visibility before scaling traffic.
Supported capability notes:
Authenticated Sonic RPC/API access for wallets, contract apps, and live backends.
HTTPS and WebSocket connectivity for app, backend, and integration workflows.
Archive-capable workflows for historical state and analytics.
Trace-ready workflows for transaction debugging and execution analysis.
HTTPS and WebSocket connectivity is listed for supported app and backend workflows.
Archive support is available for historical state or older chain-data queries.
Trace support is available for transaction debugging and execution analysis.
A quick connection check usually starts with eth_blockNumber, then moves into the exact methods your wallet, dashboard, bot, indexer, or backend service needs.
Planning the next step:
Shared RPC is a practical starting point for integration, prototypes, dashboards, and many app backends.
Review higher-capacity access when the product becomes traffic-heavy or operationally sensitive.