API Overview

Triport is a single multi-chain RPC platform for every network in the registry — JSON-RPC, a REST product layer, and streaming where mounted, all behind one base URL and one API key.

Network

Any network in the registry

Authentication

x-token header (recommended); see Authentication for all forms

Tier / rate limit

Any tier (free 7-day trial works); see Rate Limits

What Triport is

Triport is a multi-chain RPC platform. You send standard requests to a single base URL; Triport authenticates your key, routes the request to the right network backend, enforces your tier's rate limits, and returns the upstream result unchanged. You integrate against one API surface instead of wiring up a separate provider per chain.

The generated registry summary below is authoritative.

Across the registered networks Triport exposes three kinds of surface:

Base URLs

All requests go to a single base URL:

Each network's canonical JSON-RPC endpoint is listed in the generated table below.

A minimal first request (Solana getBalance against production):

curl https://triport.io/sol \
  -H "x-token: $TRIPORT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "getBalance",
    "params": ["vines1vzrYbzLMRdu58ou5XTby4qAqVRLmqo36NKPTg"]
  }'

If you have never called Triport before, start with Getting Started — it takes you from zero to a verified response in under five minutes.

Method types

Every reference page carries a Type field so you always know what you are calling — a chain method, a Triport add-on, or a Triport product surface:

Console / dashboard-management endpoints are tagged Triport Console API.

For how a request actually flows end-to-end — edge, auth, routing, upstream node, response — and an honest account of what Triport operates versus routes to, see Architecture & trust model.

Authentication, briefly

Send your API key (it looks like tri_live_…). Triport accepts it in several forms, tried in this priority order:

1. x-token: <key> header — preferred.
2. Authorization: Bearer <key> header — standard Bearer scheme.
3. ?api-key=<key> query parameter — legacy.
4. Path form /<chain>/<key> — works only for tri_live_* API keys.

Full details and when to use each are on the Authentication page.

Rate limits, briefly

Triport rate-limits by sustained requests-per-second, scoped to your tier and the request's category, with a global burst multiplier of 2×. There is no daily quota — only the per-second budget. Tiers range from the free 7-day trial through basic, pro, business, and custom enterprise; higher tiers unlock more RPS and multi-region routing.

Rate-limit state is reported on responses via X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, and X-RateLimit-Category. When you exceed your budget you get HTTP 429 with a Retry-After header. See Rate Limits for the per-tier numbers and burst behavior.

Errors, briefly

Every error comes back as a JSON envelope with a machine-readable error code, a human message, and a request_id for support. The codes you will see most:

All of these are plain HTTP errors: the gate decides them before the request reaches the RPC layer, so there is no JSON-RPC error object to branch on — use the HTTP status and the error field. JSON-RPC error objects come from the upstream node (such as -32602 for invalid params). See the Errors page for the full envelope and typed error schemas.

Surface reference — where to go next

Guides

Solana

Ethereum

Polygon

Wallet Identity (cross-chain)

Available from the Business tier (wallet_identity category, 30 rps; Enterprise 150 rps).

Client libraries

Every surface is plain HTTP/WSS. Call it with curl, fetch, or any standard JSON-RPC or WebSocket client pointed at the endpoint, with your key in the x-token header. See Getting Started for copy-paste examples.

Notes

• Every registered network shares one key, one error envelope, and one rate-limit model.
• Raw JSON-RPC results are passed through unchanged from the upstream node, so existing chain tooling and method docs continue to apply.

9 networks are supported today: Solana, Ethereum, Polygon, BNB Smart Chain, Base, Tron, Robinhood Chain, Stellar, and TON.