Overview
OrbitFlare provides Polygon PoS RPC infrastructure for DeFi protocols, gaming, and production applications. Endpoints are region-pinned and authenticated with the same license key as your other OrbitFlare services. Every plan includes RPC, WebSockets, gRPC access, and archival data. Polygon is EVM-compatible, so the JSON-RPC surface is the standardeth_* API.
Endpoint
The general form matches the rest of the platform:
Polygon endpoints are separate from the Solana endpoints documented in Authentication & Limits. Solana uses
{region}.rpc.orbitflare.com; Polygon uses {region}.poly.orbitflare.com.Authentication
Append your license key as a query parameter, exactly as with the Solana RPC endpoints:Making RPC Calls
Polygon uses the same JSON-RPC 2.0 format as Ethereum. PassContent-Type: application/json with a POST body:
WebSocket Subscriptions
Real-time subscriptions use thewss:// scheme with the same host and the same api_key parameter:
Plans
Throughput scales by plan. RPC, WebSockets, gRPC access, and archival data are included on every tier, and there are no monthly credit or request caps.What happens if I exceed my rate limit?
What happens if I exceed my rate limit?
Requests over your plan’s RPS limit receive an HTTP
429 Too Many Requests response. Implement exponential backoff in your client to handle these gracefully.Are there monthly credit caps?
Are there monthly credit caps?
No. You can send unlimited total requests as long as you stay within your plan’s per-second rate.
Dedicated Instances
For isolated, high-throughput workloads, OrbitFlare also offers dedicated Polygon nodes:Dedicated Polygon infrastructure is quoted per deployment. Contact sales to discuss throughput, region, and SLA requirements.
Supported Methods
Polygon endpoints expose the standard EVM JSON-RPC API, including:Polygon PoS uses
chainId: 137 for mainnet and chainId: 80002 for the Amoy testnet.Rate Limits and Quotas
These limits apply to all OrbitFlare EVM chains (Robinhood, Polygon, BSC). They are enforced per license, and HTTP and WebSocket traffic on the same key share a single rate limit and in-flight budget.
Applies to both tiers: WebSocket connection lifetime of 24 hours; idle timeout of 30 minutes with no data frames; frame size of 4 MiB inbound and 32 MiB outbound; each batch item counts as one request.
Error Codes
-32005 and -32429 are transient. Retry with exponential backoff. If -32005 persists on isolated calls, another client is likely using the same key concurrently, since HTTP and WebSocket share one in-flight budget.Get Started
Authentication & Limits
How API keys work, endpoint formats, rate limits, and error semantics.
Contact Sales
Talk to the OrbitFlare team about dedicated Polygon instances and enterprise terms.