Metis API, RPC Endpoints & Node Infrastructure

Metis RPC Endpoints on OnFinality

Metis is an Ethereum Layer 2 scaling solution that combines a rollup architecture with a decentralized sequencer to deliver fast, low-cost transactions while maintaining Ethereum-level security. The Metis Andromeda mainnet (Chain ID 1088) supports EVM-compatible smart contracts, making it a popular choice for DeFi, NFTs, and gaming dApps.

What is a Metis RPC Endpoint?

A Metis RPC endpoint is a network URL that allows applications to read blockchain data, submit transactions, and interact with smart contracts on the Metis network. Developers use RPC endpoints to connect wallets, dApps, analytics tools, and backend services to Metis.

Metis RPC on OnFinality

OnFinality provides managed API endpoints for Metis, giving developers access to reliable, scalable RPC infrastructure without the overhead of running their own nodes. Key features include:

• EVM JSON-RPC support: Full compatibility with Ethereum tooling (Web3.js, ethers.js, Hardhat, etc.)
• HTTP and WebSocket transports: Choose between RESTful requests or real-time subscriptions
• Archive and trace data: Access historical state and transaction traces for analytics and debugging
• Production-ready: Suitable for high-traffic dApps, wallets, and backend services

How to Connect to Metis with OnFinality

1. Create or sign in to your OnFinality account.
2. Select Metis from the supported networks list.
3. Create an API endpoint (shared or dedicated, depending on your plan).
4. Test the endpoint using eth_blockNumber or another JSON-RPC method.
5. Monitor usage, errors, and limits via the OnFinality dashboard before moving production traffic.

Why Use OnFinality for Metis RPC?

• No node management: Focus on building, not infrastructure.
• Scalability: Start with shared endpoints and upgrade to dedicated nodes as your project grows.
• Observability: Track request volume, latency, and error rates.
• Global infrastructure: Endpoints served from multiple regions for low latency.

Use Cases

• DeFi protocols: Fetch on-chain data, submit transactions, and monitor events.
• Wallets: Display balances, transaction history, and enable token transfers.
• Analytics platforms: Query historical data via archive nodes.
• Games and NFTs: Interact with smart contracts for minting, trading, and gameplay.

Getting Started

Visit the OnFinality dashboard to create your Metis RPC endpoint today. For detailed documentation, refer to our API guides and network configuration pages.

Metis RPC and developer resources

A useful Metis 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 Metis 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.
• Trace-ready workflows for teams that need to inspect execution paths.

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.
• 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.
• 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 RPC provider selection guide