Tetherline — Blockchain API and RPC infrastructure for developers

What you get

Node access is the easy part. The index is the work.

Renting a machine and syncing a chain is straightforward. Keeping transfer history queryable and correct through chain reorganizations is the part that takes months.

Reads

Account state and history in one call

Request an address and get its token balances plus paginated transfer history across both chains — no log scraping, no block-range loops.

Writes

Relay signed transactions

You sign locally; we relay the payload to the network. Tron energy and Ethereum gas estimates are returned with the request.

Streams

Webhooks that survive reorgs

Subscribe to an address and get a callback on every inbound transfer, with a correction event if a block is later orphaned.

Depth

Full archive, no surcharge

Historical state queries hit the same endpoint. Reconcile old records without provisioning a separate archive plan.

Routing

Requests go to a healthy node

Regional routing and health checks keep traffic off degraded nodes. Live latency and uptime are published on the status page.

Control

Keys you can scope

Restrict a key by method, chain, origin, or IP range. Rotate without downtime and see per-key usage in the dashboard.

Quickstart

One endpoint, both chains.

Change the chain parameter to move between networks. Same auth, same response shape, same pagination. SDKs for TypeScript, Python, and Go, plus plain HTTP for everything else.

# Account state and recent transfers
curl https://api.tetherline.io/v1/account \
  -H "Authorization: Bearer $TETHERLINE_KEY" \
  -d '{
    "chain": "tron",
    "address": "TQ4n...9xKd",
    "include": ["transfers"],
    "limit": 25
  }'

# → 200 OK
{
  "balance": "48210.442100",
  "decimals": 6,
  "block": 71204488,
  "transfers": [ ... ]
}

Questions

Before you write the integration.

Do you hold funds or private keys?

No. Tetherline is read and relay infrastructure only. We take no custody of assets, store no private keys, and sign nothing on your behalf. There is no wallet, no exchange, and no trading feature. You sign locally and we pass the signed payload to the network.

How do you handle chain reorganizations?

Transfers are marked pending until they reach your configured confirmation depth. If a block is orphaned before then, the webhook fires a correction event with the original event ID so you can reverse your side.

What counts as a request?

One HTTP call or one WebSocket message. An account lookup that also returns 25 transfers counts once. Webhook deliveries are not counted.

Which networks are supported?

Tron and Ethereum mainnet and public testnets, covering native and standard token contracts. Additional networks are in private beta — ask if you need early access.

Can I migrate from a self-hosted node?

Yes. The endpoint accepts standard JSON-RPC alongside our REST API, so most teams change a URL and an auth header. The extended endpoints are opt-in.