Monero RPC Endpoint

Endpoint At A Glance

Monero access is for apps, wallets, indexers, relayers, and operators that need a private authenticated lane rather than anonymous public RPC.

Endpoint

monero.rpc.uquad.org

Interfaces

Monero restricted RPC

Access

Customer requests require X-Wallet-Address and X-API-Key unless a route is explicitly marked otherwise.

Status Rule

Read the live fleet feed before quoting Monero as healthy or synced.

Use this page when the job is reading Monero node status, node info, common REST state, or authenticated endpoint readiness before integration.

Buy or request CU.Use the quote-first CU path before sending traffic. Endpoint use is not a public free RPC lane.
Read live status.Check status.json before treating the endpoint as healthy, synced, or customer-ready.
Send authenticated requests.Include wallet and API-key headers on HTTP requests and gRPC metadata.
Watch the boundary.RPC observation is not chain truth, custody, settlement, ordering, finality, or an uptime guarantee.

The useful claim is not just that a hostname exists. The useful claim is that access, status, and refusal boundaries can be inspected.

Replace the wallet and key placeholders with the values from the quote-matched claim path.

curl \
  -H "X-Wallet-Address: <wallet>" \
  -H "X-API-Key: <api-key>" \
  https://monero.rpc.uquad.org/get_info

curl \
  -H "X-Wallet-Address: <wallet>" \
  -H "X-API-Key: <api-key>" \
  https://monero.rpc.uquad.org/get_height

These pages are designed for search intent and developer onboarding, but the public boundary stays smaller than the infrastructure.

No Free Tier On This Chain

This chain is API-key-gated access, not an anonymous public endpoint.

No Uptime Guarantee

Current status belongs to the live feed and can change.

No Finality Claim

RPC responses do not replace chain consensus, settlement, or independent verification.

No Token Claim

Buying CU does not create allocation, yield, redemption value, reward eligibility, governance right, or future entitlement.