What are the HyperSync and HyperRPC endpoints for Somnia Mainnet?

Our HyperSync endpoint for Somnia Mainnet is https://somnia.hypersync.xyz and our HyperRPC endpoint is https://somnia.rpc.hypersync.xyz. Both need an API token. Pass it to the HyperSync client, or add it to the end of the HyperRPC URL.

What is the chain ID for Somnia Mainnet?

Somnia Mainnet uses chain ID 5031. Use it as the chain id in a HyperIndex config.yaml. HyperSync is the data source by default, so you don't need a node or your own RPC endpoint.

What is the RPC URL for Somnia Mainnet?

We run HyperRPC for Somnia Mainnet at https://somnia.rpc.hypersync.xyz, a read-only endpoint built for data-intensive queries. Add your API token to the end of the URL. For a general-purpose public RPC endpoint, Chainlist keeps a live list for Somnia Mainnet at https://chainlist.org/chain/5031.

What is the block explorer for Somnia Mainnet?

The block explorer for Somnia Mainnet is https://mainnet.somnia.w3us.site. Use it to look up individual transactions and addresses. To query Somnia Mainnet data in bulk, index it with HyperIndex and serve it from your own API.

Do I need an API token to use HyperSync or HyperRPC on Somnia Mainnet?

Yes. Requests to https://somnia.hypersync.xyz or https://somnia.rpc.hypersync.xyz without a token are rejected with HTTP 401. Create one in the Envio Dashboard. Indexers deployed to Envio Cloud have their own HyperSync access and don't need one.

What is an alternative to Somnia Mainnet RPC for reading chain data?

HyperSync replaces JSON-RPC for reading Somnia Mainnet data, at https://somnia.hypersync.xyz. You select the logs, transactions and blocks you need and only the fields you want, over any block range. If your code already speaks JSON-RPC, HyperRPC at https://somnia.rpc.hypersync.xyz is a read-only drop-in endpoint. To send transactions you still need a full RPC node.

Can I send Somnia Mainnet transactions through HyperRPC?

No. HyperRPC at https://somnia.rpc.hypersync.xyz is read-only. It serves chain, block, transaction, receipt and log methods such as eth_getLogs, and cannot submit transactions. To send transactions, use a full Somnia Mainnet RPC node.

Does HyperRPC support the MIP-16 query methods on Somnia Mainnet?

Yes. HyperRPC serves eth_queryBlocks, eth_queryTransactions and eth_queryLogs on Somnia Mainnet at https://somnia.rpc.hypersync.xyz. They filter on the server, return only the fields you select, and can join each log to its transaction and block. Traces and transfers are coming soon.

How much does HyperRPC cost on Somnia Mainnet?

HyperRPC is billed monthly at $4 per million JSON-RPC method calls, with a $1 monthly minimum. Each method in a batch request counts as one call.

Can I index Somnia Mainnet and other chains in one indexer?

Yes. List Somnia Mainnet (id: 5031) under chains in config.yaml next to your other chains, and the same handlers process events from all of them. Chains are indexed in parallel, each in its own block order.

How does Envio handle chain reorganisations on Somnia Mainnet?

HyperIndex detects reorgs and rolls back your indexed data automatically. It is on by default and covers reorgs up to max_reorg_depth blocks below the head, 200 on most chains. Detection is guaranteed when HyperSync is the data source.

How fast is Envio at indexing Somnia Mainnet?

HyperIndex runs historical backfill and live events in one pipeline, at 100,000+ events per second. In the open indexer benchmark it is 6–879x faster than other indexers, The Graph included.

What does it cost to index Somnia Mainnet?

Building is free on the development plan, and production plans on Envio Cloud start after that. HyperIndex reads Somnia Mainnet from HyperSync, so there is no RPC provider to pay for the backfill. See envio.dev/pricing for current plans.

Why do HyperSync or HyperRPC requests on Somnia Mainnet return 401?

A 401 with "Your token is malformed" means no API token was sent, or it is not in the expected format. Create a token in the Envio Dashboard and pass it to the HyperSync client, or add it to the end of the HyperRPC URL, as in https://somnia.rpc.hypersync.xyz/ .

Why do I get a 403 from HyperSync or HyperRPC on Somnia Mainnet?

Either the token is unknown or still pending activation, so check it was copied correctly and is active in the Envio Dashboard, or it does not have access to the product you called. Tokens in new paid packages work for one product, HyperSync or HyperRPC.

What does HTTP 429 from HyperSync mean on Somnia Mainnet?

Your token has used its budget for the current 60-second window. The budget is shared across every chain you query with that token. The HyperSync clients wait for the reset and retry, so a stream slows down rather than failing. Lower concurrency or move to a plan with a higher limit for more headroom.

Custom Somnia Mainnet APIs and analytics

Turn your Somnia Mainnet contracts into real-time APIs with HyperIndex, and query historical and live chain data through HyperSync and HyperRPC.

Try it free Read the docs

HyperRPC requires an API tokenGet one →

Chain ID

5031

Native token

SOMI

RPC endpoint

somnia.rpc.hypersync.xyz

Block explorer

mainnet.somnia.w3us.site

Latest block

Binance

Gnosis

Aerodrome

Yield Basis

Chronicle

Curve

Sablier

WLFI

Caldera

Limitless

Gnosis App

Etherspot

0xbow

dRPC

Trusted by industry leaders

Index and query Somnia Mainnet

HyperIndex

Index Somnia Mainnet contract events into a GraphQL API, with backfill and live events in one pipeline.

Create an indexer
Run pnpx envio init to scaffold a HyperIndex project. Give it your Envio API token and it saves it to .env, so local runs can read Somnia Mainnet from HyperSync. Indexers deployed to Envio Cloud don't need one.
$ pnpx envio init

Add Somnia Mainnet to config.yaml

List Somnia Mainnet under chains with your contract and events. HyperSync is the data source by default, so no RPC URL is needed.

config.yaml

name: my-indexer
contracts:
  - name: MyContract
    events:
      - event: "Transfer(address indexed from, address indexed to, uint256 value)"
chains:
  - id: 5031 # Somnia Mainnet
    start_block: 0
    contracts:
      - name: MyContract
        address: "0x0000000000000000000000000000000000000000"

Run it
Start it with pnpm dev, which needs Docker. It opens the local Hasura dashboard with your indexed data.
$ pnpm dev

HyperSync

Read raw Somnia Mainnet logs, transactions and blocks in bulk, selecting only the fields you need.

Every request requires an API token. Get an API token

HyperSync endpoint

https://somnia.hypersync.xyz

TypeScript (npm install @envio-dev/hypersync-client)

import { HypersyncClient } from "@envio-dev/hypersync-client";

const client = new HypersyncClient({
  url: "https://somnia.hypersync.xyz",
  apiToken: process.env.ENVIO_API_TOKEN!,
});

// ERC-20 and ERC-721 Transfer events from the last 10 blocks.
const height = await client.getHeight();
const res = await client.get({
  fromBlock: height - 10,
  logs: [{ topics: [["0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef"]] }],
  fieldSelection: { log: ["BlockNumber", "Address", "Topic1", "Topic2"] },
});
console.log(res.data.logs.length, "Transfer events in the last 10 blocks");

HyperRPC

A read-only endpoint for existing RPC code, with the MIP-16 query methods. Add your token to the end of the URL. It cannot send transactions.

Every request requires an API token. Get an API token

HyperRPC endpoint

https://somnia.rpc.hypersync.xyz

curl

curl https://somnia.rpc.hypersync.xyz/$ENVIO_API_TOKEN \
  -X POST -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

About

An EVM-compatible layer 1 blockchain designed for real-time consumer applications such as games, social apps and metaverses.

Source: docs.somnia.network

Network

Mainnet

See Somnia Testnet

Support

First-class

Block explorer

mainnet.somnia.w3us.site

Official site

somnia.network

Using HyperSync as Your Indexing Data Source HyperRPC: Ultra-Fast Read-Only RPC MIP-16 query methods API Tokens for HyperSync Configuration File (config.yaml)HyperSync Supported Networks MCP Server

Prompt for your AI agent

Build a HyperIndex indexer on Somnia Mainnet (chain ID 5031) that indexes [CONTRACT ADDRESS]'s [EVENTS] into a GraphQL API.

Before writing code, read https://envio.dev/chains/somnia.md and https://envio.dev/llms.txt. If you can add MCP servers, add Envio's docs server at https://docs.envio.dev/mcp.

1. Run pnpx envio init and choose Contract Import with the address above.
2. Put my API token in ENVIO_API_TOKEN in .env (I'll create it at https://envio.dev/app/api-tokens).
3. Shape the entities in schema.graphql and the event handlers, then run pnpm codegen.
4. Start it with pnpm dev (needs Docker) and confirm the entities appear in the local Hasura GraphQL API.
5. Add tests for the handlers and run pnpm test.

FAQs

Somnia Mainnet indexing FAQ

Endpoints, chain IDs, data sources and getting started with Somnia Mainnet on Envio.

Read the supported chains docs

Get support

Discord Telegram

Does Envio support Somnia Mainnet?

Yes. Somnia Mainnet has first-class support across HyperIndex, HyperSync, and HyperRPC. We run dedicated HyperSync and HyperRPC endpoints for Somnia Mainnet so you can stream historical and real-time data straight into a production GraphQL API.

HyperSync supported chains →