New

Solana Beta is now live

apechain live
ApeChain

ApeChain RPC Endpoint

NFT mints and game traffic arrive in bursts. A dedicated ApeChain endpoint absorbs the spikes without shared-pool rate limits.

chain id · 33139 json-rpc 2.0 websocket

latency

In production at
Chainlink Enjin Tiingo Gains Network

Quick connect

Your endpoint, ready in one line.

Drop this URL into your RPC client, HTTP library or wallet config. No SDK install required.

HTTPS
https://eu.endpoints.matrixed.link/rpc/apechain?auth=YOUR_API_KEY
WebSocket
wss://eu.endpoints.matrixed.link/ws/apechain?auth=YOUR_API_KEY

Replace YOUR_API_KEY with your API key. Get a free key →

Connect

Pick your stack.

Copy-paste examples for the libraries you already use. Swap the API key, hit run.

import { ethers } from "ethers";

const provider = new ethers.JsonRpcProvider(
  "https://eu.endpoints.matrixed.link/rpc/ape?auth=YOUR_API_KEY"
);

About ApeChain

Connect your dApp, bot, or protocol to ApeChain Mainnet with BoltRPC. NFT and gaming applications generate bursty, unpredictable RPC traffic. Dedicated capacity with predictable request-unit pricing means you are ready for mint events and trading surges without per-request billing or shared infrastructure congestion.

Chain at a Glance

Chain ID33139
ProtocolArbitrum AnyTrust on ETH
Block time~0.25 s
Native tokenAPE
FinalityNear-instant sequencer confirmation
EVM compatibleYes

What ApeChain is Built For

ApeChain is the official blockchain of the ApeCoin ecosystem, built on Arbitrum AnyTrust and designed specifically for NFT trading, gaming, and creator economy applications within the Yuga Labs and ApeCoin community. Bored Ape Yacht Club, Mutant Ape Yacht Club, and the broader Yuga Labs NFT ecosystem use ApeChain as their primary settlement layer. Gaming studios building on ApeCoin issue in-game assets and handle player economy transactions on ApeChain. The chain’s AnyTrust architecture provides low fees and fast finality suitable for the high-transaction-count patterns of gaming and NFT marketplace activity.

RPC Workload Patterns on ApeChain

ApeChain’s 250ms block production, inherited from Arbitrum AnyTrust, directly shapes the RPC patterns that NFT and gaming applications generate. Ownership verification queries run before almost every player action in ApeChain games, not just on transaction submission. When a player attempts to equip an item or enter a gated area, the game backend calls eth_call against the NFT contract to confirm the player’s ownership status. At scale across thousands of concurrent players, this becomes a continuous stream of read calls.

Marketplace backends are particularly read-heavy. A marketplace listing page for a Bored Ape or Mutant Ape collection item pulls ownership data, recent transfer history via eth_getLogs, and token metadata in rapid succession. Aggregators and indexers that process ApeChain data across multiple collections run sustained parallel eth_getLogs queries spanning large block ranges, a workload pattern that would inflate costs significantly on compute-weighted billing models.

The bursty nature of ApeChain traffic is its defining characteristic. Long quiet periods punctuated by sharp spikes during launches, events, and gaming sessions mean infrastructure that handles the peaks without degradation and stays affordable during the quiet periods. Predictable request-unit pricing handles both states predictably.

Why BoltRPC

Built for teams that ship on ApeChain.

NFT and gaming traffic is bursty by nature

ApeChain powers the official ApeCoin ecosystem. NFT marketplaces and games generate bursty RPC traffic: metadata reads, ownership checks, transaction submissions during mints. These spikes are unpredictable and short-lived. BoltRPC handles them without dropped connections or rate limit errors. Shared infrastructure fails exactly when it matters most, during a high-profile mint or a gaming event with thousands of concurrent players.

Dedicated capacity for asset-heavy protocols

Gaming protocols that issue in-game assets on ApeChain make frequent ownership queries and transfer submissions. Dedicated RPC capacity means those queries return consistently, regardless of what else is happening on shared public infrastructure.

Arbitrum AnyTrust architecture support

ApeChain is built on Arbitrum AnyTrust. BoltRPC supports the full AnyTrust JSON-RPC surface alongside Arbitrum One from one provider, one API key.

Predictable RU pricing for NFT and gaming patterns

Gaming backends and NFT marketplace contracts make high volumes of eth_call and eth_getLogs requests. Published per-method request-unit pricing means your RPC costs stay predictable, with a plan sized to your request mix no matter how active your game's economy is.

Full EVM compatibility

Any Ethereum code works on ApeChain with a single endpoint change.

WebSocket for real-time game and marketplace events

Subscribe to ApeChain events in real time via WebSocket. Essential for game backends that need to react to NFT transfers, token grants, and marketplace settlement immediately.

Methods

Full JSON-RPC coverage.

Every standard ApeChain method you'd expect. Archive-only methods are available on request for qualifying plans.

standard

5
eth_call eth_getLogs eth_getBalance eth_blockNumber eth_sendRawTransaction

FAQ

ApeChain, explained.

Common questions about connecting to ApeChain over BoltRPC.

Get started

Pick a chain. Point your client.

One endpoint format, 20+ networks, no SDK. Drop our URL into the client you already use and your integration is done.

https://eu.endpoints.matrixed.link/rpc/ {chain} ?auth= YOUR_API_KEY

No credit card required. · 14-day trial on any tier.