Operations
Credits and limits
Understand what consumes your allowance and how available credits are calculated.
Requests reserved for upstream forwarding count toward usage, including upstream errors and uncertain outcomes. Local validation failures that are not forwarded do not consume request credits. Each supported batch item is charged separately. Internal failover does not add a second customer charge for the same item.
X-Relay-Credits reports the HTTP credit cost for the request or batch.
A reservation is not the same as recorded spending. A verified gRPC cancellation settles the received bytes recorded by Relay; a verified Preprocessed cancellation settles received transaction messages. Both release the unused customer reservation after the stream has stopped and its final counters are verified. Interrupted or expired streams without verified final counters remain awaiting confirmation. Relay tracks unresolved provider accounting separately from finalized customer charges.
Usage shows recorded HTTP and streaming credits for your current paid period. Received streaming data can exceed delivered data, and open-session counters can lag. An unavailable balance is not a zero balance.
Open Usage to compare products, methods, API keys, or HTTP activity by day. The breakdown uses your complete current paid period. Choose HTTP requests or credits spent, filter a product or key, and show the top 10, 20, or all rows.
Seven-day and 30-day views cover HTTP activity within the current paid period. Streaming totals cover the full paid period; reserved credits are listed separately. Request history and its CSV export contain the latest 200 HTTP requests across paid periods.
Usage refreshes every 15 seconds while the page is visible. Requests sent from RPC → Playground use your actual key and consume the same credits as requests from your application. Your subscription dates and queued renewals are in Profile.
Throughput is measured in UTC second windows across all customer keys. RPC and DAS have separate limits. Transaction submission, bundle submission, and program-account limits apply within the RPC limit. Batching does not bypass these limits.
Available credits, throughput, and concurrent-stream allowances are different limits. A request can be rate-limited while credits remain. See current plan limits and your dashboard for purchased terms.