Home Docs Telegram Status

Billing Model

Nodius uses a prepaid credit system with per-method pricing. No subscriptions, no invoices, no minimums. Deposit USDC, receive credits, spend credits on RPC calls.

How It Works

  1. Activate your account (POST /account/activate)
  2. Deposit USDC to the shared deposit wallet
  3. Credits are applied automatically (~30 seconds after finalization)
  4. Each RPC method deducts credits based on its computational weight
  5. When credits reach 0, requests return 402 Payment Required

Credit Rate

Purchase Credits
1 USDC 10,000 credits

Credits expire after 10 days from the deposit date. Monitor via GET /account/info and the credit_batches field.

Method Costs

READ_CHEAP — 1 Credit

getSlot, getBalance, getAccountInfo, getMultipleAccounts (1 per account), getLatestBlockhash, getEpochInfo, getHealth, getVersion, getTransactionCount, getBlockHeight, getBlockTime, isBlockhashValid, getTokenAccountBalance, getTokenAccountsByOwner, getPriorityFeeEstimate, suggestPriorityFee, and other lightweight reads.

READ_MEDIUM — 5 Credits

simulateTransaction, getEnrichedTransaction, explainTransaction, getAssetsByOwner, and medium-weight account/token owner queries.

ARCHIVE_HISTORY — 5-25 Credits, Profile-Gated

getTransaction, getSignaturesForAddress, getBlock, getBlocks, getBlocksWithLimit, and related retained/archival history methods. These are enabled on archive/history endpoints. The hot-node launch endpoint returns a deterministic no-charge service-gate error when the archive profile is disabled.

READ_HEAVY — 25 Credits, Profile-Gated

getProgramAccounts, getLargestAccounts, simulateBundle, and other large indexed scans. These are enabled on heavy-indexed endpoints. The hot-node launch endpoint returns a deterministic no-charge service-gate error when the heavy-indexed profile is disabled.

SEND — 2 Credits

sendTransaction.

SEND_BUNDLE — 10 Credits

sendBundle (Jito integration).

Jito Endpoints

Endpoint Cost
POST /jito/sendBundle 10 credits
POST /jito/getBundleStatuses 2 credits
GET /jito/getTipAccounts 1 credit
GET /jito/tipFloor 1 credit

WebSocket Billing

Event Cost
Creating a subscription 5 credits (WS_SUBSCRIBE)
Each notification received 1 credit (WS_NOTIFICATION)
Unsubscribing Free
Connection / disconnection Free

Connection requirements: - Minimum 100 credits to connect - Auto-disconnect below 10 credits (close code 4002)

Cost estimates per hour: - slotSubscribe: ~9,000 credits/hour (~2.5 notifications/sec) - accountSubscribe (active): varies by activity - logsSubscribe("all"): 10,000+ credits/hour - programSubscribe (Token Program): 100,000+ credits/hour

Yellowstone gRPC Billing

Usage Cost
Active gRPC connection 60 credits per minute

Yellowstone gRPC connections are billed continuously while connected. The billing is flat-rate per minute — there is no per-notification charge. This makes it cost-effective for high-throughput streaming use cases.

Connection billing: - Charge starts when the gRPC stream is established - Billed every 60 seconds while connected - No charge for the initial connection handshake - Disconnection stops billing immediately

Batch Requests

Batch JSON-RPC requests are supported. Each method in the batch is billed individually by method cost. A batch of 5 getBalance calls costs 5 credits (5 x 1). Batch requests count as 1 request for rate limiting.

Monitoring Your Balance

Every HTTP response includes: X-Credits-Remaining: 84521

When balance drops below 1000: X-Credits-Low: true

At 0 credits: HTTP 402 Payment Required

Refund Policy

Nodius — nodius.xyz · Telegram · Status