Q token mark QUADRPC Endpoints

QUAD RPC / Status and receipts

RPC status and receipts.

A practical map of the public feeds that make endpoint access checkable before a developer, operator, or partner depends on it.

Buy CU Live Status JSON Endpoint Contract Developer Quickstart

Status Is The Traffic Hook

Most RPC pages stop at a hostname. This surface makes the hostname less important than the receipts around it: status, freshness, endpoint contract, payment feed, quote ledger, and key state.

Fleet Status

status.json owns current chain reachability, height, sync, peers, and dated generation.

Endpoint Contract

endpoint-contract.json owns hostnames, access posture, provider lanes, and must-not-infer claims.

Payment Feed

data/cu-payments.json exposes an aggregate CU credit summary; per-customer wallets, balances, payment tx hashes, and receiving addresses are withheld.

Quote Ledger

data/cu-quotes.json exposes quote-time terms that control payment matching.

Receipts To Check Before Depending On A Lane

These checks are the practical operator path. They are also the search intent we want to own.

  1. Read fleet status.Confirm the chain row is present, reachable, and synced before quoting current health.
  2. Read the endpoint contract.Confirm the hostname, interface set, access posture, and customer-readiness state.
  3. Check payment posture.If access is being bought, confirm the quote and payment feed rather than relying on a screenshot.
  4. Keep refusals visible.Do not turn endpoint presence into finality, custody, uptime, sale, reward, or launch claims.

Live Surfaces

Use these routes directly in runbooks, integration checks, and status bookmarks.

Status JSONCurrent fleet state and chain row health. Status AliasSame fleet feed through the public alias. Endpoint ContractMachine-readable access and claim boundary. Payment RailsAccepted rails and memo expectations. Quote LedgerAccepted quote rows and quote-time values. Payment FeedAggregate CU credit summary (per-customer detail withheld). Key StatusAggregate key-status summary; per-wallet key mapping and refs withheld. Assistant GuidePublic-safe wording for assistants and crawlers.

Example Status Read

The live feed is public. Free-tier chains accept keyless calls (rate-limited); gated chains and dedicated throughput use an API key.

curl https://rpc.uquad.org/status.json
curl https://rpc.uquad.org/endpoint-contract.json