Pay in Monero (XMR), Zephyr (ZEPH), Bitcoin (BTC), or Sui (SUI) — or any of a dozen Cosmos and EVM assets. Compute units credit to the paying wallet after a quote-matched payment; one CU balance works across every customer RPC endpoint. No account — just a wallet.
The paying wallet is the customer identity. A payment becomes CU only when the feeder matches it to an accepted quote.
IdentityPaying wallet address becomes the customer unless the accepted quote says otherwise.
AccessOne CU balance can be spent across the customer RPC surface. Status, abuse controls, and unhealthy lanes still gate actual use.
CreditMatched quote payments credit CU to that wallet and publish the credit state.
UnmatchedWrong memo, wrong rail, wrong address, or missing quote stays unmatched and does not auto-credit.
BoundaryEndpoint revenue is separate from Infra memory, relayer gas, validators, provider payout, and reserve value. BIGHT uses an RPC wallet first, then a BIGHT-only sink sweep.
When CU Is (And Isn't) Spent
Holding CU does not put your wallet on a meter. You are never charged for usage you would get free without a key — a CU balance is spent only on real paid demand.
Free · no CU spentReads on the free-tier chains, within about 300 requests/min. The same free tier applies whether or not your wallet holds CU; a balance is never drawn down for free-tier reads.
Charged · paid-only chainsAny request to a payment-required chain — Ethereum, Avalanche, Sui, Starknet, Bitcoin, Monero. These have no free tier.
Charged · writes & broadcastsSubmitting or broadcasting transactions on any chain spends CU; the free tier is read-only.
Charged · beyond the free limitReads past about 300/min on a free-tier chain spend CU for the overage instead of returning 429 — so a paid key means bursts succeed rather than getting rate-limited.
Buy Flow
The product is direct enough to use, but still refuses sloppy payment. The quote is the thing being bought against.
Choose CU amount.Use 1M, 25M, 100M, or a custom quote for heavy use.
Name the wallet.Use the wallet address that should own the CU allowance and receive the endpoint key.
Pick a rail.Pay through the quote-issued rail below; do not use validator, provider, relayer, reserve, sink, or memory accounts. BIGHT uses its own RPC wallet.
Pay as quoted.Memo-capable rails use rpc:<wallet_address>:<quote_id>. Memo-less rails bind credit to the quoted sender or quote-specific address. Actual CU follows the amount that arrives.
Spend CU.The same wallet-bound CU balance is used across the customer RPC endpoints.
Quote Request
CU is bought against a quote row. The request names the wallet that should own the balance before any payment is sent.
No payable quote yetEnter the wallet that will pay, choose a rail, set the amount, then create a payable quote before sending funds.
API key not issuedThe API key appears here only after the matching payment is observed. It is not written to public feeds.
Payment Matched
The matched payment is ready for claim.
Balance not checkedEnter the wallet and API key to read remaining CU without spending it.
WalletThe wallet that owns the CU balance and appears in the feed.
CU target1M, 25M, 100M, or a custom CU target.
Pay withOne of the dedicated rail accounts listed below.
AmountThe amount estimates CU from the live quote-time price. It does not bind the feeder.
AccessThe credited wallet can spend CU across the customer RPC surface, subject to status, rate limits, and abuse controls.
Quote responseReturns quote id, CU estimate, denom, payment address, memo or sender binding, expiry, customer wallet, and wallet-bound key instructions.
Accepted quote responses use memo format rpc:<wallet_address>:<quote_id> when the selected rail supports memos. Memo-less rails bind credit to the quoted sender address. The amount field estimates CU only; the feeder credits CU from the amount that actually arrives. Keep this browser open until the key is claimed, or save the one-time claim secret somewhere private.
Recent Accepted Quotes
The feeder credits payments against accepted quote rows. This preview shows the latest five; the full ledger stays in data/cu-quotes.json.
Loading recent quotesReading the latest payable quote rows.
Payment Rails
The current rail feed is the authority. The table below lists common rails for orientation; the quote response controls the actual denom, address, memo, and expiry.
Denom
Chain
Dedicated rail account
Payment address
BIGHT / Infra-settled assets
Infra
rpc-pay-bight
infra1ezsgacszcc4uyzz98g0dsrrexu9jfetfxfahxk
ATOM
Cosmos Hub
rpc-pay-atom
cosmos1a7htft9m2yazkfpc9qkx0qtawhjydf0d8s997a
OSMO
Osmosis
rpc-pay-osmo
osmo1szdpdncv84g3ver657s3lexmdqxxg9kx7wv3jp
TIA
Celestia
rpc-pay-tia
celestia1krzmksa2csa5jtjl2xle67ygxlc8r6pvjg00f2
AKT
Akash
rpc-pay-akt
akash1uqttk2he57tjnknqywggcdly9cs3d22drs0a6q
STRD
Stride
rpc-pay-strd
stride1h3p5unyp8j3sy888z254xs9ukzdls5js3rdzsq
DYDX
dYdX
rpc-pay-dydx
dydx1yzpx9apxatkde3lxms6htm82ntsnyhanaj9jyj
LAVA
Lava
rpc-pay-lava
lava@1pstxf67jw4rvlujnelxc4k0fttuqz922g48ene
INJ
Injective
quote rail
inj19x795fyt4zu5t6lq04jlvp77ehxxf4cjchalpr
NTRN
Neutron
quote rail
neutron1f62q8tdn94l2mnuwlv0g3c3607h2sgcu93v0am
AXL
Axelar
quote rail
axelar10xvuwaahwvpvwdxpzhxgr6umpquex9pahtc924
ETH
Ethereum
quote rail
0x39bb1987deb8c91b56e13b8ab0aa79034fcd23d8
Read the live rail feed before sending funds: data/payment-rails.json. The feeder credits CU only when the observed payment matches an accepted quote and lands at the quote-issued rail address. BIGHT is classified after intake so only BIGHT can move to the sink path; non-BIGHT rails do not inherit burn handling. Sending funds without a matching quote is a visible unmatched payment, not automatic endpoint access.
Payment Feed
The website reads the feeder output. When the feeder is live, this surface shows paid quotes and CU credited to wallet addresses.
Loading feedReading data/cu-payments.json.
What This Does Not Do
The rail is a product lane, not a general-purpose treasury or support route.
Not Infra memory
Endpoint revenue is not storage, receipt reissue, upload, or proof-memory revenue until admitted through that path.
Not relayer gas
Customer CU payments do not automatically fund Hermes, host-chain relayers, or provider gas floats.
Not chain authority
RPC access does not prove chain truth, finality, custody, admission, settlement, launch, or governance rights.
Not automatic if wrong
Wrong memo, missing quote, or wrong rail means no automatic CU credit. A different amount only changes credited CU.
Not address-only auth
A wallet address can identify the customer, but it is public and cannot safely spend CU by itself.
Not mixed burn
BIGHT paid for CU enters the RPC BIGHT wallet and is the only denom eligible for a post-intake sink sweep. Other payment denoms stay out of the sink path.
