Overview

AU.RO RPC is a multi-chain RPC platform: you register a tenant, create a project, issue an API key, and call any supported blockchain through a single gateway host with that one key.

How a request flows

your app
  │  https://rpc.lab.au.ro/<chain>   (header: apikey)
  ▼
API gateway (Kong) ── key auth · per-plan rate limits · heavy-method guard
  ▼
RPC proxy ── chain routing · response cache · Compute-Unit metering · failover
  ▼
blockchain nodes ── dedicated full nodes across our locations

Three hosts make up the platform:

Host	Purpose
rpc.lab.au.ro	RPC traffic — your application talks to this
api.lab.au.ro	Management API — registration, projects, keys, usage, webhooks
dash.lab.au.ro	Dashboard — the same management actions in a browser

What you get per chain

• A native endpoint — each chain speaks its own protocol (JSON-RPC 2.0 for EVM and bitcoind-family chains, REST for TRON/Aptos/Stellar, ogmios for Cardano, CometBFT for Cosmos). No translation layer to learn.
• Response caching — immutable data (confirmed transactions, old blocks) is cached aggressively; head-of-chain data uses short TTLs (1–10 s); transaction submission is never cached. Every response carries X-Cache: HIT or MISS.
• Failover — multi-node chains are load-balanced at the gateway; a node that stops answering is retried against the next one transparently.
• Metering — every call costs Compute Units (CU) by method weight (see Compute Units). Usage is visible per project in the dashboard and the management API.

Plans

Plans differ by request rate and CU price — the API surface is identical on every plan, including free. Exact numbers live in Rate limits.

Current chain count

17 chains are live today (see Endpoints for the full matrix); TON and Solana are next on the roadmap. Each chain has a dedicated integration page under Chains with executed examples for the ecosystem's native SDK.