Pricing you can recompute
Plans are billed in standard requests (one read = 1 request, archive = 5, trace/debug = 20), while pay-as-you-go stays in compute units (CU); the two meters never mix. Failed requests and cache hits are free; price versions, weights and billing rules are public so invoices can be recomputed.
Three products, one API key
Wallet sign-in and RPC are priced separately. Approval checks are never metered, so they cost nothing at any volume.
ChainBridge Connect · Platform fee + connections
Multi-wallet connectivity, SIWE/SIWX authentication, and session management. A monthly platform fee plus tiered pricing per successful connection.
ChainBridge Nodes · Pay as you go or subscribe
Distributed RPC and chain data. Plans include a standard-request quota; pay-as-you-go is metered in compute units (CU).
ChainBridge Security
Approval scanning, risk explanations, individual and same-chain batch revocations, multi-chain monitoring, revocation rules, security reports, and read-only sharing.
Node plans
All plans include intelligent routing across providers, node health scoring, failover, and detailed usage records. Quotas, unit prices, and SLAs vary by plan.
Capabilities open chain by chain: HTTP covers every connected network, while WebSocket, archive, trace and MEV-protected submission require that chain to have the matching upstream configured. Pricing and plan features list only capabilities verified live: listed the moment they open, and calls to closed capabilities return a clear error without billing. For what each chain supports right now, see the capability matrix (machine-readable, script-checkable).
Pay as you go
No monthly fee, no commitment. Pay for what you use — no peak estimates, no paying for idle capacity.
Loading currently active plans…
Estimate this period's bill
Estimates use published unit prices and current plan quotas. Your invoice is the source of truth and can be recomputed using each call's weight version.
Enter your projected usage
A reference estimate based on current published rules. Actual charges follow the methods called, pricing versions, and request failures.
Estimated cost
Actual usage this billing period
Billing basis and versions
| Item | Definition | Description |
|---|---|---|
| ChainBridge Security | Free forever | No usage charges; gas for revocation transactions is paid from the user's wallet |
| ChainBridge Connect | Monthly platform fee + successful connections | Failed signature checks, replayed requests, and revoked sessions are not charged |
| HTTP JSON-RPC | Per compute unit (CU) | Method weights include versions and effective dates |
| Batch requests | Metered per item | Each element of a JSON array is metered as its own CU |
| Failed requests | No customer charge | Requests that fail upstream never appear on your bill |
| Cache hits | 0 CU | No customer charge |
| Archive queries | Archive CU weights (5–20x) | Enable per chain in the console |
| WebSocket | 1 CU per connection per minute + subscription messages metered individually | Reconnecting the same session within 5 minutes incurs no second connection fee |
| Solana gRPC | 10 CU per connection + 0.05 CU per message | Metered separately from JSON-RPC; each connection is billed once, and so is each downstream message |
| Data API | Per request (weights differ by endpoint) | Metering and SLA separate from raw RPC |
| Webhook events | Per successfully delivered event | No additional charge for retries |
| Self-hosted gateway and SLA | Priced separately by contract | Includes licensing, support hours, and dedicated upstreams |
Invoices lock the moment they are issued. Discrepancies go through adjustment notes, which need two-person review and record the reason, amount, approvers, and effective date.
Included with every paid plan
Everything above ships today — no roadmap promises. Check every item in ChainBridge Nodes and Developer docs .
What is a compute unit (CU)?
CU puts the cost of different calls on one scale. It is not a request count.
Weights by method
A block header read and a full event-log range cost different amounts, so they carry different weights. Weights are versioned with effective dates, and bills are recomputed against the version live at call time.
No charge for failures
Auth failures, invalid parameters, rate-limited calls, and upstream errors never count toward CU. Batch requests count per item, and failed items are excluded.
Verify every line item
Download the raw details behind every invoice — methods, weights, CU, and pricing versions. Reconcile charges yourself instead of accepting an unexplained total.
The full method weight table lives in Billing Rules. The method dictionary endpoint returns the weights currently in effect.
About billing
Approval scanning, risk explanations, revocations, monitoring, and security reports carry no platform fees and require no payment method. Only onchain transactions initiated from your own wallet require gas, which is charged by the network, not by us.
Failures are not your fault. Requests that fail upstream are never billed, and neither are calls that hit rate limits or exceed quota.
Yes. Compute unit weights and unit prices retain their versions and effective dates, so invoice details can be recalculated using the rules in effect for each call, matching the ledger. Amounts are locked after invoicing; changes require an adjustment note.
Unused subscription fees are refunded pro rata by day; usage fees already incurred are not refunded. Enterprise contracts follow their contract terms.
Set quotas and alerts in the console: at 80% usage a webhook fires usage.quota.warning; overages never quietly turn into a huge bill.
Pricing is agreed separately by contract based on the deployment model, support hours, and SLA level. If the self-hosted gateway uses the ChainBridge public network as a fallback, that traffic is billed at published unit prices.
Validate with real requests first
Create a key and send a few real requests. Approval scanning needs no key and costs nothing.