Skip to content

Triton One

Triton One sells metered Solana JSON-RPC on a single pay-as-you-go tier: $10 per million calls plus $0.08/GB of response bandwidth. There are no plan tiers to choose between, but there is a $125 prepaid minimum.

What is the Triton RPC URL?

Triton assigns a pool hostname when you sign up:

https://<your-pool>.rpcpool.com/<API_KEY>

The key is a path segment. The pool name is specific to your account — there is no shared public host.

How do I get a Triton endpoint?

  1. Sign up at triton.one.
  2. Fund the account — Triton requires a $125 initial deposit in stablecoins, which is prepaid, non-refundable, and valid for 12 months.
  3. Copy the pool URL from the dashboard.

That deposit is the main thing separating Triton from the other providers here: there is no credit-card free tier to try it on. Whether a free trial exists is not documented on the pricing page — ask their team before committing.

What Triton costs

Service Per-call Bandwidth
Standard RPC, account and ledger queries, unary gRPC $10/M calls $0.08/GB
Metaplex / DAS API $50/M calls $0.08/GB
Streaming services, Titan Prime API — $0.08/GB only

Shred streaming is priced separately at $1,500/month per IP per data centre. Verified 2026-09-05 against triton.one/pricing.

Bandwidth is the real cost driver

Triton is the only provider here that bills bandwidth as a separate line. For small responses it rounds to nothing — a getAccountInfo reply at ~0.5 KB adds about $0.04 per million calls. For history it dominates: at ~500 KB a block, a million getBlock calls carry roughly $40 of bandwidth on top of the $10 of call charges.

See the provider pricing reference for the modelled totals, including the bandwidth component.

Configure Triton in RPC Plane

[[providers]]
name = "triton"
url  = "https://your-pool.rpcpool.com/${TRITON_API_KEY}"

export TRITON_API_KEY=your_api_key_here
rpc-plane run

Triton's rate and connection limits are negotiated per account rather than published, so set max_rps to whatever your agreement says:

max_rps = 100   # set to your negotiated limit

Bounding the spend

Because billing is metered from the first call rather than drawn against an included quota, a runaway history workload shows up directly on the invoice. Two knobs bound it:

[[providers]]
name    = "triton"
url     = "https://your-pool.rpcpool.com/${TRITON_API_KEY}"
max_rps = 100                                  # ceiling on dispatch rate
methods = ["getAccountInfo", "getBalance",     # keep large-payload history off it
           "getSlot", "sendTransaction"]

methods restricts Triton to the calls you want it to serve, so getBlock and getTransaction — the bandwidth-heavy ones — never reach it. See submission-only providers for how a restricted provider is health-scored.

When to use Triton

  • As a third provider for redundancy alongside Helius and QuickNode — an independent operator with its own infrastructure, which is the point of running more than two.
  • Not as the default home for history calls. getBlock and getTransaction are where the bandwidth charge bites; use methods to keep them on another provider.
  • Only once you are past evaluation. The prepaid minimum makes it a poor choice for a first provider or a CI environment.