What Iteradian does, and what it does not.

Iteradian is a multi-chain RPC gateway and node control plane. You get an API key, point your JSON-RPC 2.0 traffic at an Iteradian endpoint, and requests are routed to a pool of managed nodes with rate limiting, failover and per-request usage analytics.

The catalogue includes Arbitrum One, Avalanche, Base, Bittensor, BNB Smart Chain, Ethereum, Lightchain AI, Optimism, Polygon, Solana, Ethereum Sepolia, Polygon Amoy. A network is served only while it has a healthy node, and when this answer was generated the gateway (GET https://api.iteradian.com/rpc/v1/networks) listed none, so no network was serving traffic. The status page re-checks every network live.

Yes. New organizations start with a 7-day free trial on the Developer RPC plan and can issue API keys immediately. Free RPC is also available at no cost, with no time limit.

Send POST https://api.iteradian.com/rpc/v1/{network} with your API key in an X-Api-Key header. The gateway also accepts Authorization: Bearer <key>, where the value is the same API key. Keys start with itrd_live_ or itrd_test_ (a label for organizing keys, not a network restriction), and the full key is shown once. A request with no key returns HTTP 400; an invalid, revoked or expired key, or one used from an IP outside its allowlist, returns HTTP 403.

Free RPC is free: 25 requests per second, 10 concurrent connections, 3,000,000 requests per month included, 3 api keys, hard cap at the monthly allowance, no overage billed. Developer RPC is $39 per month plus applicable taxes: 250 requests per second, 100 concurrent connections, 25,000,000 requests per month included, 10 api keys, overage $0.005 per 1,000 requests, capped at $150 per billing period. Professional RPC is $169 per month plus applicable taxes: 500 requests per second, 500 concurrent connections, 80,000,000 requests per month included, 25 api keys, overage $0.003 per 1,000 requests, capped at $350 per billing period. Dedicated RPC is priced per contract through sales, with requests per second and concurrency set in the contract and unlimited monthly requests.

Limits belong to the organization and are shared by all its API keys. Requests over the per-second rate or concurrency limit receive HTTP 429 with JSON-RPC error code -32005 and a retryAfter value; retry after that many seconds. Past the monthly allowance, plans with overage keep serving requests and bill them per 1,000 up to the plan's overage cap (Free RPC: 3,000,000 included; Developer RPC: 25,000,000 included; Professional RPC: 80,000,000 included); beyond the cap requests receive HTTP 429 with code -32007, and on a plan without overage the allowance itself returns -32006. Retrying -32006 or -32007 cannot succeed until the period resets or the plan changes. A batch of N calls counts as N requests.

Paid Plans are billed in advance in US dollars, monthly or annually, through Stripe or through Paddle — checkout shows which. With Paddle, Paddle is our reseller and merchant of record: it adds the sales tax or VAT for your address and issues the invoice. Overage (requests above your Plan's allowance, if your Plan allows it) is billed after the period ends, up to your Plan's overage cap. The billing FAQ at /faq/billing covers plan changes, cancelling and refunds. Plans priced per contract cannot be bought online — contact sales.

Yes. The management API at https://api.iteradian.com/api/v1 covers accounts, organizations, API keys, usage, logs, alerts, billing and support, authenticated with an access token. There is no public OpenAPI page; the route reference is on the documentation page. SDKs are published for TypeScript / JavaScript (@iteradian-rpc/sdk on npm), Python (iteradian on PyPI), C# / .NET (Iteradian on NuGet), covering both the management API and RPC calls. Any HTTP client or existing Web3 library also works with the X-Api-Key header.

Yes. Open wss://rpc.iteradian.com/ws/v1/{network} with the same API key, in an X-Api-Key or Authorization: Bearer header, or as ?apiKey= where a browser cannot set headers. eth_subscribe, Solana *Subscribe and other subscription methods work. Every message you send counts as a request, like an HTTP call (a batch of N counts as N); notifications the node pushes are not charged. An organization can hold max(5, a quarter of its concurrency limit) streams open at once.

No. Iteradian publishes no standard service level agreement and no uptime figure. If you need contractual availability terms, raise it with sales before purchase.

No. Iteradian provides RPC access to Bittensor with failover across managed nodes, but TAO rewards depend on many factors beyond infrastructure.