Cosmos RPC Endpoints — Free Public + Dedicated CU | QUAD RPC

Skip to RPC service details

QUAD RPC / Free + dedicated Cosmos RPC

Cosmos RPC endpoints — free to start, dedicated when you scale.

Public, rate-limited RPC, REST, and gRPC you can hit right now with no key — across Cosmos Hub, Akash, Celestia, Stride, Injective and more. CU-metered dedicated throughput when your app goes to production. Self-hosted nodes, pay in crypto, no accounts.

Try a free endpoint<br>Buy CU<br>Quickstart<br>Endpoints<br>Live Status

Free, no signup — curl it now: curl https://cosmos.rpc.uquad.org/status &middot; public free tier, rate-limited (~60 req/min/IP) &middot; need production throughput? Buy CU.

What This Surface Is

This is the RPC endpoint and proof surface. It gives customers a private lane while giving operators and partners a public-safe way to inspect status, route contracts, payment posture, and the boundary around each claim.

Access Free public tier on enabled chains (rate-limited, no key); a valid X-API-Key unlocks CU-metered dedicated throughput.

Receipts Status, payment feeds, key state, quote ledgers, and endpoint-contract metadata are public where safe.

Contract Endpoint hostnames, customer lanes, provider lanes, current observations, and refused inferences are published as a route contract.

Separation Customer payments, validator income, provider income, and relayer gas remain distinct. RPC access does not imply custody, settlement, admission, or chain truth.

What The Endpoint Layer Proves

The marketing claim is intentionally narrow: queryable access plus public receipts. A route can be listed, degraded, refused, or customer-ready, but the live feed and endpoint contract decide which statement is current.

Live status Reachability, sync posture, chain row count, and dated observations belong to the same-origin status feed.

Endpoint contract Hostnames, interfaces, provider lanes, access posture, payment rules, and must-not-infer claims are published as JSON.

Freshness boundary Dated snapshots are useful receipts, not proof of current health. Current claims should be re-read from live feeds before quoting.

Refusal gates RPC access does not claim token sale, reward eligibility, chain custody, settlement, finality, value admission, validator authority, or launch readiness.

Read Live Status<br>Endpoint Contract<br>Plain Summary<br>Assistant Guide

Developer And Search Pages

These pages answer concrete endpoint questions directly: which hostname, which headers, which status feed, which contract, and which claims are refused.

QuickstartUse QUAD RPC in five minutes with curl, JavaScript, and Go examples.<br>Cosmos RPCCosmos Hub endpoint, interfaces, headers, and receipts.<br>Osmosis RPCStatus-gated Osmosis endpoint access and cautions.<br>Bitcoin RPCBitcoin Core JSON-RPC access and full-index boundary.<br>Status ReceiptsHow to inspect fleet status, quotes, payments, and key state.<br>ContractsHow endpoint contracts define access and refused claims.

How To Buy CU

CU is bought by accepted quote, not by sending funds to a public address. The quote gives the exact denom, address, amount, memo, allowance, and expiry.

1. Pick a starting allowance<br>Choose a reference bundle or ask for a custom quote if your app needs heavy historical queries, broadcast traffic, or high bursts.

2. Create the quote<br>Use the CU product page to name the paying wallet, rail, and amount before sending funds.

3. Pay the quote exactly<br>Use the quote-issued payment address and the exact matching rule. Memo-capable rails use rpc::; memo-less rails bind by sender or quote-specific address.

4. Claim key and allowance<br>After the payment is observed, the private claim path returns the wallet-bound API key once.

1M CU $2 USD-target reference

25M CU $50 USD-target reference

100M CU $200 USD-target reference

Custom Quoted for heavy or unusual use

Quote request must include<br>Paying wallet, accepted rail, send amount, and any heavy-use details that need an operator quote.

Quote response must include<br>Quote ID, invoice ID, payment address, accepted denom amount, memo, expiry, CU estimate, and one-time browser claim ticket.

Buying CU is quote-first. The public page can create a payable quote and later claim the API key, but unsolicited or mismatched payments are still not automatically credited.

Open CU Product Page<br>View Pricing Reference<br>Payment Rules

Provision Access

Private access starts after the quote path exists. The quote names the customer wallet, allowance, settlement denom, matching rule, expiry, and boundary.

Use the customer surface. One wallet-bound CU balance can open every customer endpoint while that lane is healthy and CU remains.

Accept quote. Pricing is a USD-target reference settled in an accepted denom at quote-time.

Pay as quoted. Use the exact address, denom, memo, sender binding, or quote-specific address the quote provides.

Receive key. Send X-API-Key on HTTP requests and gRPC metadata.

Operate inside boundary. Heavy, archive-like,...