TON RPC API
C1Talk to TON over standard JSON-RPC without running a node. Requests hit nodes we operate directly, so you get honest latency and no reseller throttling — and the same key already carries data, intelligence and AML.
TON JSON-RPC on our own nodes
Standard TON JSON-RPC passthrough served from nodes we run, not a proxy in front of someone else's cluster. Methods, batching and error semantics match the reference client.
One key across the stack
The key you use for TON RPC also reads decoded data, wallet balances, on-chain intelligence and AML — no second vendor, no second bill, metered in credits.
Frequently asked
Do you run your own TON nodes?
Yes — TON RPC is served from nodes we operate, not resold from a third party.
Is there a request rate limit?
Throughput is governed by your plan's credit balance, not an artificial per-second cap layered on by a reseller.
Top up, get a key, ship.
Self-serve. Pay in crypto or card. Metered by credits — heavy primitives cost more, simple ones are cheap.
Get API key