Lightchain AI RPC, on the same interface as every other chain.
Iteradian provides a managed Lightchain AI RPC endpoint. Requests are sent as JSON-RPC 2.0 with an API key and routed to a pool of managed Lightchain AI nodes, with an enforced rate limit, failover across the candidate list, and per-request usage analytics.
POST https://api.iteradian.com/rpc/v1/lcai-mainnet
- Slug
- lcai-mainnet
- Aliases
- lcai-mainnet, lightchain-mainnet
- Status
- No healthy node right now — see status
- Verified
Why use a managed Lightchain AI endpoint?
Lightchain AI is an AI-integrated blockchain built around its AIVM execution environment. Iteradian exposes it through the same JSON-RPC 2.0 interface, the same API key and the same analytics pipeline as every other network, so you can add it to an existing integration without a second client library.
How do I connect to Lightchain AI?
- 01
Create an API key
Sign up for Iteradian and create a key in the dashboard. Production keys are prefixed
itrd_live_and test keysitrd_test_. The plaintext key is shown exactly once, so store it in a secret manager — never in source control. - 02
Send a JSON-RPC 2.0 request
cURL curl -X POST https://api.iteradian.com/rpc/v1/lcai-mainnet \ -H "Content-Type: application/json" \ -H "X-Api-Key: itrd_live_YOUR_KEY" \ -d '{"jsonrpc":"2.0","id":1,"method":"rpc_methods","params":[]}'TypeScript const res = await fetch("https://api.iteradian.com/rpc/v1/lcai-mainnet", { method: "POST", headers: { "Content-Type": "application/json", "X-Api-Key": process.env.ITERADIAN_API_KEY!, }, body: JSON.stringify({ jsonrpc: "2.0", id: 1, method: "rpc_methods", params: [], }), }); const { result } = await res.json();Python import os, requests res = requests.post( "https://api.iteradian.com/rpc/v1/lcai-mainnet", headers={"X-Api-Key": os.environ["ITERADIAN_API_KEY"]}, json={"jsonrpc": "2.0", "id": 1, "method": "rpc_methods", "params": []}, ) print(res.json()["result"]) - 03
Handle throttling
Requests past your plan’s per-second rate or concurrency ceiling return HTTP 429 with JSON-RPC error code
-32005and aretryAftervalue inerror.data. Past the monthly allowance, requests run as metered overage until the plan’s overage cap, then return 429 with-32007. Throttled requests are recorded in your usage and request log too — nothing is dropped silently.
Common Lightchain AI RPC methods
| Method | Description |
|---|---|
| rpc_methods | Lists the JSON-RPC methods the upstream node exposes. |
Lightchain AI RPC pricing
| Plan | Price | Included |
|---|---|---|
| Free RPC | $0/mo | 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 | $39/mo | 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 | $169/mo | 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 | Custom | Custom requests per second · Custom concurrent connections · Unlimited monthly requests · Unlimited API keys · Dedicated infrastructure |
Lightchain AI RPC FAQ
01How do I get a Lightchain AI RPC endpoint?
Create an Iteradian account, generate an API key, and send JSON-RPC 2.0 requests to https://api.iteradian.com/rpc/v1/lcai-mainnet with the key in an X-Api-Key header (Authorization: Bearer also works). New organizations start with a 7-day free trial.
02What happens if I exceed the Lightchain AI rate limit?
The request receives HTTP 429 with a JSON-RPC error body. Code -32005 means your organization's per-second rate or concurrency limit — retry after `error.data.retryAfter` seconds. Code -32006 means the monthly quota is used up (`error.data.resetsAt` says when it resets) and -32007 means the overage spend cap is reached; retrying either cannot succeed until the period resets or the plan changes. Limits are shared by all of the organization's keys.
03What happens if a Lightchain AI node goes down?
The gateway fails a request over to another healthy Lightchain AI node automatically, across up to 3 nodes. Transaction submissions are sent to one node and never retried or replayed by the gateway, so it cannot broadcast a transaction twice. If every node fails, the response is HTTP 503.
04Which Lightchain AI RPC methods are supported?
Iteradian forwards JSON-RPC 2.0 requests to the Lightchain AI node, so the methods available are the methods that node exposes. Batch requests are supported (a batch of N calls counts as N requests). Subscriptions work over the WebSocket endpoint wss://rpc.iteradian.com/ws/v1/lcai-mainnet with the same API key.