QUAD RPC Endpoints — Free Reads + API-Key Production Access

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.

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

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

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

SeparationCustomer 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 Endpoint Contract Plain Summary Assistant Guide

Endpoint Directory

Start here if you know the chain you need. Customer-ready pages link directly; syncing, degraded, or provider-only lanes stay in the status and contract feeds until they are ready to promote.

Cosmos HubFree public RPC, REST, and gRPC; CU for production throughput. OsmosisFree public RPC and REST; CU for production apps and indexers. AkashFree public Cosmos-SDK endpoint with production CU option. CelestiaFree public Tendermint and REST reads; status feed owns current health. StrideFree public endpoint page for wallets, relayers, and operators. dYdXFree public endpoint page with dedicated CU path when needed. NeutronFree public RPC and REST page; verify tip state in live status. InjectiveEndpoint page for Injective reads; current readiness belongs to status.json. EthereumAPI-key JSON-RPC lane for customer CU access. BitcoinAPI-key Bitcoin Core JSON-RPC lane and full-index boundary. MoneroAPI-key restricted RPC lane; no wallet custody or payment promise implied. SuiAPI-key Sui JSON-RPC lane for customer traffic. StarknetAPI-key Starknet JSON-RPC and websocket posture. BaseAPI-key Base mainnet JSON-RPC and WebSocket lane. Fleet StatusCurrent reachability, sync, quote receipts, payments, and key-state summaries. Endpoint ContractMachine-readable hostnames, access posture, provider lanes, and refused claims. Buy CUQuote-first purchase path for production RPC access.

Free readsEnabled Cosmos chains can be read without an API key until the public rate limit is reached.

Production lanesBase, Ethereum, Bitcoin, Monero, Sui, Starknet, and higher-throughput access require a quote-issued API key and CU allowance.

Not promoted yetAxelar, Polygon PoS, Zephyr, and the Lava provider lane are discoverable in status or contract data, but not presented as customer-ready endpoint pages.

Freshness ruleUse status.json before quoting any specific chain as healthy, synced, degraded, or unavailable.

Developer And Search Paths

These pages are the practical path after endpoint discovery: quickstart examples, status receipts, route contracts, and the customer purchase surface.

QuickstartUse QUAD RPC in five minutes with curl, JavaScript, and Go examples. Status ReceiptsHow to inspect fleet status, quotes, payments, and key state. ContractsHow endpoint contracts define access and refused claims. Machine ContractJSON source for endpoint hostnames, access posture, and customer-readiness boundaries. Plain SummaryStatic crawler-readable description of what the RPC surface is and is not. Assistant GuideQuote rules for AI assistants and search summarizers. Buy CUQuote-first production access path.

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 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 Use the CU product page to name the paying wallet, rail, and amount before sending funds.

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

4. Claim key and allowance 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

CustomQuoted for heavy or unusual use

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

Quote response must include 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 View Pricing Reference 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, or abusive request patterns require a separate quote.

Buy CU Infra Overview

Current Public Posture

The service is live as a free public + paid (CU) gateway: anonymous rate-limited access on enabled chains, self-serve quote creation, private browser key claim for dedicated CU, and public-safe status feeds.

Live

Private endpoint gateway, quote surface, payment rails, claim path, balance check, and status surface.

Quote-first

Access is issued after a customer/quote record exists.

Free + dedicated

Enabled chains have a free rate-limited public tier; production throughput is CU-metered.

Not chain custody

RPC access does not custody, settle, or admit value.

Current snapshot

The fleet status table below is read live from status.json on each page load. Re-read it for authoritative per-chain reachability, height, sync, and peer state.

Customer lanes

One CU balance is for the customer RPC surface as a whole. If a lane is degraded, unavailable, or not customer-ready, status gates the lane; it is not sold as a separate subscription.

RPC Status

Status is part of this RPC product surface. It tracks endpoint access, customer feeds, auth posture, and known blockers without turning observation into admission or custody.

Customer pathQuote, payment rails, CU credit, private key claim, balance check, and endpoint use live under this subdomain.

Auth postureCustomer access is wallet-bound API-key access. Operator static keys are continuity keys, not the customer product.

CU accountingPaid quotes credit CU from actual observed payment amount. Authorized requests debit CU by request class.

Current feedPayment feed is active with observed payments, matched payments, unmatched payments, credited customers, and total CU credited.

Chain	Status	Height	Peers	Access
Loading RPC fleet status...

Fleet status feed not yet loaded.

Fleet status JSONSame-subdomain chain reachability, height, sync, and peer state. Payment railsAccepted payment routes and memo expectations. Quote ledgerAccepted quote metadata and quote-time rates. CU payment feedAggregate CU credit summary; per-customer wallets, balances, and tx hashes withheld. Key statusAggregate CU key-status summary; per-wallet key mapping and tx refs withheld. Buy CUCustomer quote and purchase surface.

Endpoint status is product-local. It does not prove Bridge admission, chain settlement, asset ownership, validator authority, Infra memory work, or broader stack launch state.

Endpoint Fleet

Self-hosted endpoint lanes served over TLS, paired with a public endpoint contract and same-origin fleet status feed. Customer endpoint hostnames require an API key unless explicitly marked otherwise. Monitored payment rails are listed separately from customer raw RPC routes, and quote-issued keys can carry narrower allowed lanes.

Chain	Endpoint	Interfaces	Service state
Cosmos Hub	cosmos.rpc.uquad.org	Tendermint RPC / REST / gRPC	free (rate-limited) · CU for production
Osmosis	osmosis.rpc.uquad.org	Tendermint RPC / REST / gRPC	free (rate-limited) · CU for production
dYdX	dydx.rpc.uquad.org	Tendermint RPC / REST / gRPC	free (rate-limited) · CU for production
Akash	akash.rpc.uquad.org	Tendermint RPC / REST / gRPC	free (rate-limited) · CU for production
Stride	stride.rpc.uquad.org	Tendermint RPC / REST / gRPC	free (rate-limited) · CU for production
Celestia	celestia.rpc.uquad.org	Tendermint RPC / REST / gRPC	free (rate-limited) · CU for production
Injective	injective.rpc.uquad.org	Tendermint RPC / REST / gRPC	free (rate-limited) · CU for production
Neutron	neutron.rpc.uquad.org	Tendermint RPC / REST / gRPC	free (rate-limited) · CU for production
Ethereum	eth.rpc.uquad.org	JSON-RPC (EVM)	API key required
Sui	sui.rpc.uquad.org	Sui JSON-RPC	API key required
Starknet	starknet.rpc.uquad.org	Starknet JSON-RPC / WS	API key required
Monero	monero.rpc.uquad.org	Monero restricted RPC	API key required
Bitcoin	btc.rpc.uquad.org	Bitcoin JSON-RPC	API key required
Lava	lava.rpc.uquad.org	Provider endpoint	provider lane, not customer raw RPC
Zephyr	zephyr.rpc.uquad.org	Monero-style RPC	syncing — coming soon
Polygon PoS	poly.rpc.uquad.org	JSON-RPC (EVM)	syncing — coming soon
Base	base.rpc.uquad.org	JSON-RPC + WebSocket (EVM)	API key + CU
Axelar	axelar.rpc.uquad.org	Tendermint RPC / REST / gRPC	degraded — temporarily unavailable

Live sync and reachability labels belong to the RPC status section on this page. Status is observational; it is not a finality, completeness, or correctness guarantee.

Pricing Reference

Usage is referenced in compute units (CU). The public reference is a starting posture; accepted quotes control actual customer terms.

Reference$2.00 USD-target per 1,000,000 CU unless a quote says otherwise.

SettlementAccepted crypto denom at accepted quote-time value.

AllowancePrepaid or assigned customer allowance by key.

Heavy useArchive-like scans, wide ranges, and high bursts are quote-only.

Free never meteredHolding CU never charges you for free-tier reads. CU is spent only on paid-only chains (ETH/SUI/Starknet/BTC/Monero), writes/broadcasts, or reads beyond the free ~300/min.

CU Weights

Reference weights express handling burden. They are not a promise that every future method always keeps the same weight.

Call class	Examples	CU
Light read	status, block, node info, simple queries	1
Standard query	balances, delegations, params, common REST/LCD	2
Heavy query	tx search, wide ranges, historical scans	10 or quoted
Broadcast	transaction broadcast	quoted or separately weighted

Paying For CU

Payment activates only after the quote path accepts it. Do not send funds without the customer ID, quote ID, invoice ID, payment address, amount, and memo expected for your access record.

Accepted denom	Native chain	Payment posture
BIGHT / Infra-settled assets	Infra	RPC wallet receipt; native BIGHT, Infra-side ATOM, or Infra-side OSMO selected inside the buy flow
XMR (Monero)	Monero	quote-issued subaddress; no memo, no KYC
ZEPH (Zephyr)	Zephyr	quote-issued subaddress; no memo, no KYC
BTC (Bitcoin)	Bitcoin	quote-issued address; no memo, no KYC
SUI	Sui	quote-issued address; no memo, no KYC
ATOM	Cosmos Hub	quote-issued memo required
OSMO	Osmosis	quote-issued memo required
TIA	Celestia	quote-issued memo required
AKT	Akash	quote-issued memo required
STRD	Stride	quote-issued memo required
DYDX	dYdX	quote-issued memo required
LAVA	Lava	quote-issued memo required
INJ / NTRN / AXL / ETH	Quote rails	quote-issued memo required; check the live rail feed before paying

Memo rulePreferred format: rpc:<customer_id>:<quote_id>.

CreditPayment observation credits endpoint access only after the quote path accepts it.

No custody claimCustomer payment does not become reserve value, validator stake, or Infra memory revenue by itself. Only native BIGHT is eligible for the post-intake sink path.

No refund promiseTerms are controlled by the accepted quote and receipt path.

If you want to buy CU, request a quote first. The quote is the purchasing object; the payment is only valid when it matches that quote.

Public Boundary

QUAD RPC is a paid access service to self-hosted public-chain nodes. It is not a token surface and not a substitute for chain truth.

What it is

Free rate-limited public read/query on enabled chains, plus CU-metered dedicated read, query, and broadcast for production. Degraded lanes gated by status.

What it is not

Not a sale, airdrop, staking program, node-earning program, faucet, or reward claim.

Does not create

No token allocation, yield, redemption value, governance right, or future entitlement.

Does not guarantee

No uptime, finality, ordering, completeness, or data-correctness guarantee beyond the accepted quote boundary.

Request Access Buy CU Live Status Infra QUAD Home

Find the endpoint, check live status, then use the right lane.