Mantle RPC Endpoints & API

Mantle RPC Endpoints & API on OnFinality

Mantle is an Ethereum layer-2 scaling solution built with a modular architecture. It combines an EVM-compatible execution layer with Ethereum's security and a decentralized data availability layer (Mantle DA) to deliver low fees and high throughput. Developers building on Mantle need reliable RPC endpoints to interact with the network—reading blockchain data, submitting transactions, and connecting backend services.

OnFinality provides managed Mantle RPC endpoints and API access, so you can focus on building dApps, wallets, DeFi protocols, analytics tools, games, and bots without running your own node infrastructure.

What is a Mantle RPC Endpoint?

A Mantle RPC endpoint is a network URL that applications use to communicate with the Mantle blockchain. It supports standard Ethereum JSON-RPC methods, making it easy to use familiar tools like ethers.js, web3.js, and Hardhat. OnFinality offers both HTTP and WebSocket endpoints for real-time and request-response interactions.

Key Features of OnFinality Mantle RPC

• Mainnet access: Connect to Mantle mainnet with authenticated endpoints.
• Archive support: Access historical state data for analytics and backfilling.
• EVM JSON-RPC: Full compatibility with Ethereum development tools.
• Observability: Request analytics and usage metrics to monitor your application.
• Scalable plans: From shared endpoints to higher-capacity options as your project grows.

How to Connect to Mantle with OnFinality

1. Create or sign in to your OnFinality account.
2. Select Mantle from the supported networks list.
3. Create an API endpoint (or deploy a dedicated node if supported).
4. Test your endpoint using eth_blockNumber.
5. Monitor request usage, errors, and limits before moving production traffic.

Public vs. Private Mantle RPC

Public Mantle RPC endpoints are convenient for quick testing but often have rate limits and no more predictable resource planning. OnFinality's authenticated endpoints provide clearer usage limits, request analytics, and a path to higher-capacity infrastructure—essential for production workloads.

Use Cases for Mantle RPC

• dApps: Read contract state, send transactions, and listen to events.
• Wallets: Fetch balances, transaction history, and submit transfers.
• DeFi: Interact with liquidity pools, oracles, and lending protocols.
• Analytics: Query historical data via archive nodes.
• Backend services: Automate on-chain operations and monitoring.

Why Choose OnFinality for Mantle RPC?

OnFinality offers a developer-friendly platform with managed infrastructure, so you don't have to worry about node maintenance, syncing, or uptime. Our endpoints are designed for teams that need reliable, observable, and scalable access to Mantle.

Get started with Mantle RPC on OnFinality today.

Mantle RPC and developer resources

Mantle RPC access is useful when a product needs dependable chain reads, transaction submission, and a clear path from a first request to production infrastructure.

Best fit: mainnet production workflows for dApps, wallets, DeFi, and backend services.

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 Mantle RPC/API access for dApps, wallets, DeFi, and backend services.
• HTTP and WebSocket support for app, backend, and integration workflows.
• Archive access for historical state, analytics, or compliance-style queries.

Decision notes:

• Environment: mainnet. Protocol family: EVM JSON-RPC.
• HTTP and WebSocket support 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:

• Create or manage RPC endpoints
• Review RPC pricing
• Read the Mantle RPC guide