Abstract RPC Endpoints & API

The Blockchain for Consumer Crypto

Chain ID2741

CurrencyETH

Access Abstract RPC endpoints for consumer crypto dApps on Ethereum L2, with archive data for wallets, apps, and backend services.

The Blockchain for Consumer Crypto

Create RPC Endpoint

Abstract RPC Endpoint

The below example uses the public API endpoint*. This endpoint is only suitable for testing. To avoid rate limiting and service interruption, sign up now to get your own API key.

Example CURL

curl -H 'content-type:application/json' -d '{"id": 1, "jsonrpc": "2.0", "method": "eth_blockNumber"}' 'https://abstract.api.onfinality.io/public'

curl -H 'content-type:application/json' -d '{"id": 1, "jsonrpc": "2.0", "method": "eth_blockNumber"}' 'https://abstract.api.onfinality.io/public'

HTTPs

https://abstract.api.onfinality.io/public

https://abstract.api.onfinality.io/public

Websocket

wss://abstract.api.onfinality.io/public-ws

wss://abstract.api.onfinality.io/public-ws

* The public endpoint is rate limited

RPC API Service

RPC API Features

Calculate Your Costs

Only pay for what you need.

Monthly Response Units

Million Standard Requests

0100M200M300M400M

Total Cost

$49/ month

Recommended Plan: GROWTH

Continue with this plan

Abstract RPC Endpoints on OnFinality

OnFinality provides managed API endpoints for Abstract, a Layer 2 (L2) zero-knowledge rollup built on Ethereum using zkSync's ZK Stack. Designed for consumer crypto applications, Abstract offers low fees, fast transactions, and native account abstraction via the Abstract Global Wallet (AGW). Developers can use OnFinality to access Abstract RPC endpoints without running their own node.

What is Abstract?

Abstract is an Ethereum L2 focused on bringing mainstream users to Web3 through intuitive experiences. It combines Ethereum's security with lower costs and faster speeds, making it ideal for consumer-facing dApps, games, and social platforms. Abstract is EVM-compatible, meaning you can deploy Solidity smart contracts and use standard Ethereum tooling.

Why Use OnFinality for Abstract RPC?

OnFinality offers authenticated RPC endpoints for Abstract mainnet, providing:

Reliable access to the Abstract network via HTTP and WebSocket transports.
Archive data support for historical state queries.
Observability with request analytics and usage metrics.
Scalable infrastructure from shared endpoints to dedicated node plans.

How to Connect to Abstract via OnFinality

Create or sign in to your OnFinality account.
Select Abstract from the supported networks list.
Create an API endpoint (shared or dedicated).
Test the endpoint using eth_blockNumber.
Monitor usage and errors before moving production traffic.

Use Cases for Abstract RPC

dApps: Connect wallets, read contract state, submit transactions.
Wallets: Fetch balances, transaction history, and send transactions.
DeFi: Interact with liquidity pools, swaps, and lending protocols.
Analytics: Index blockchain data for dashboards and reporting.
Backend services: Automate on-chain actions and monitor events.

Public vs. OnFinality Abstract RPC

Public RPC endpoints are suitable for testing but often lack reliability and visibility for production workloads. OnFinality endpoints provide authenticated access, clearer rate limits, and request analytics, making them a better choice for team projects and high-volume applications.

Supported Features

Network: Abstract Mainnet (Chain ID: 2741)
Protocol: EVM JSON-RPC
Transports: HTTP and WebSocket
Archive: Available (plan-dependent)
Dedicated nodes: Supported for higher capacity needs

Get Started

Sign up for OnFinality and create your Abstract API endpoint today. Whether you're building a consumer dApp, a wallet, or a backend service, OnFinality provides the infrastructure you need to scale.

Abstract RPC and developer resources

A useful Abstract RPC page should make the connection path, supported capabilities, and production planning trade-offs clear before a developer opens the dashboard.

Best fit: mainnet production workflows for wallet flows, contract apps, and live backends.

What builders usually check first:

Read current chain state for apps, dashboards, wallets, and backend services.
Submit transactions and monitor confirmations from Ethereum-compatible tools.
Query logs, receipts, and historical state when indexers or analytics pipelines need more than the latest block.
Debug contract behaviour with trace data where the network supports it.

Supported capability notes:

Authenticated Abstract RPC/API access for wallet flows, contract apps, and live backends.
Flexible HTTP and WebSocket access for app, backend, and integration workflows.
Archive-capable workflows when the product needs older chain state.

Decision notes:

Environment: mainnet. Protocol family: EVM JSON-RPC.
Flexible HTTP and WebSocket access is listed for supported app and backend workflows.
Archive support is available for historical state or older chain-data queries.

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.
If your product becomes traffic-heavy or operationally sensitive, review the available upgrade path before relying on a single access pattern.

Next steps: