Dashboard

Polygon PoS · Erigon · Bor · JSON-RPC · WebSocket

Polygon mainnet RPC with Bor extensions and realistic log pricing

Erigon 3.x archive at polygon.etox.io — standard JSON-RPC plus bor_* helpers. We publish heavier eth_getLogs CU up front so log-heavy workloads do not crowd out steady traffic, with the same API-key-first paths as Ethereum and Arbitrum.

Get API key Documentation Pricing
HTTPS host polygon.etox.io
Authentication API key as first path segment · /ws/ for WebSocket
Stack Erigon 3.x archive · Bor / heimdall-aware

Honest log pricing

Higher eth_getLogs CU than Ethereum — table on /docs, enforced at the gateway.

bor_* coverage

Validator and analytics calls like bor_getAuthor mapped in Redis weights to match real I/O.

Gateway & health

Per-key limits and GET /health on the host — mint keys in the dashboard and copy ready-made URLs.

Why Polygon eth_getLogs costs more CU

Polygon produces more aggressive block payloads than Ethereum mainnet in many epochs. To keep log-heavy workloads from starving other tenants, etox applies a higher CU weight for eth_getLogs on Polygon than on Ethereum. The numeric table is published on our docs page and enforced consistently at the gateway — no surprise invoices after the fact.

Bor method coverage

Validators and analytics pipelines sometimes rely on bor_getAuthor, bor_getCurrentValidators, and related calls. Our Redis weight map reserves entries for these methods so metered billing matches actual CPU and I/O pressure on the Erigon instance.

Authentication and WebSocket

As with every etox chain, authenticated HTTP calls require an API key from dashboard.etox.io as the first URL path segment. WebSocket RPC uses the same pattern under /ws/ for subscriptions Erigon supports — see /docs for examples mirrored from Ethereum.

Related chains

Pair Polygon with our Ethereum archive RPC for L1 anchor reads, add Arbitrum or Base for L2 traffic on the same control plane.