API
Main.net API: chain IDs, RPC URLs, and wallet config
Use the same lookup fields in scripts: chain IDs, hex IDs, RPC URLs, explorers, EIP-3085 wallet JSON, source links, source snapshot provenance, and CSV snapshots.
Versionv1
Schema1.0.0
Endpoints17
Chain source snapshotJuly 4, 2026
Endpoints
/api/v1/chains.jsonReviewed chain metadata, decimal and hex chain IDs, copy-ready config JSON, canonical status URLs, legacy helper redirects, RPC URLs, explorers, source snapshot provenance, safety notes, and chain ID probe evidence.chains68
/api/v1/chains.csvCSV snapshot of reviewed chain metadata for spreadsheets and lightweight scripts.chains-csv68
/api/v1/launches.jsonReviewed launch records with primary source links and no stage labels.launches2
/api/v1/categories.jsonNetwork category records and the chain IDs grouped under each category.network-categories10
/api/v1/glossary.jsonShort mainnet, RPC endpoint, and chain ID definitions with related guide URLs.glossary9
/api/v1/gas-tokens.jsonGas token groups derived from reviewed chain metadata.gas-tokens45
/api/v1/explorers.jsonBlock explorer hostnames and chain contexts from reviewed chain metadata.explorers68
/api/v1/search-index.jsonStatic discovery index for chain, RPC, guide, launch, glossary, explorer, and gas-token pages.search-index434
/api/v1/review-queue.jsonOperator-facing queue derived from source changes, fetch failures, and chain ID probe failures.review-queue68
/api/v1/sources.jsonDeduplicated public source registry with chain and launch page contexts.sources124
/api/v1/source-hashes.jsonSource URL hash snapshot for deterministic change detection.source-hashes124
/api/v1/source-changes.jsonSource URL changes compared with the previous hash snapshot.source-changes12
/api/v1/rpc-probes.jsoneth_chainId probe snapshot for EVM-style public RPC endpoints.rpc-probes67
/api/v1/ai-source-extractions.jsonReview-only AI source extraction report for changed source URLs. It does not edit reviewed chain metadata.ai-source-extractions8
/api/v1/ai-candidate-drafts.jsonReview-only AI candidate draft report. It does not publish candidate chains.ai-candidate-drafts5
/api/v1/upstream-reconciliation.jsonInternal upstream registry comparison report. Differences are factual observations, not judgments about source quality.upstream-reconciliation68
/api/v1/openapi.jsonOpenAPI 3.1 description for the stable static API surface.openapi1
Use it for lookups
- Main.net API v1 is a static, source-linked reference API for reviewed chain IDs, RPC URLs, explorers, wallet config JSON, and automated source snapshot provenance.
- The API does not publish live uptime, latency, block lag, price, TVL, or investment advice.
- Public RPC endpoints are setup references and should be verified against linked sources before production use.
- Deprecated lastVerified, verifiedAt*, updated, reviewCadence, and needsReviewAfter fields are compatibility aliases for automated source snapshots; they do not prove manual field review.
- Use chain urls.canonical, urls.rpcSection, and urls.chainIdSection for stable page links; urls.legacyRedirects preserves old helper URLs as redirects.
- This API is read-only and does not connect wallets, submit transactions, bridge funds, rank tokens, or recommend investments.
Find the endpoint you need
Use /api/v1/index.json for endpoint discovery,/api/v1/openapi.json for the OpenAPI description, and/llms.txt for public context. Use/api/v1/chains.csv when a spreadsheet-friendly chain snapshot is enough.
Minimal JavaScript lookup
Chain entries include decimal and hex chain IDs, source links, wallet config, and EIP-3085-shaped JSON for MetaMask-style setup on EVM rows. Treat public RPC values as references, not uptime guarantees.
const response = await fetch('https://main.net/api/v1/chains.json')
const payload = await response.json()
const base = payload.chains.find((chain) => chain.id === 'base')
console.log(base.chainId) // "8453"
console.log(base.chainIdHex) // "0x2105"
console.log(base.eip3085Config) // wallet_addEthereumChain-shaped JSON