Billing Policy
How usage is counted
Xbinodes sells RPC access as monthly plans with request-unit quotas and per-second limits. The goal is simple pricing with a few heavier method classes where needed.
Request units
- Most requests count as 1 request unit.
- eth_getLogs counts as 5 request units.
- debug_* and trace_* methods count as 20 request units.
Current service limits
- eth_getLogs requests are limited to a maximum block range of 10,000 blocks.
- Per-second rate limits are enforced per API key based on your plan.
- Monthly quotas are enforced per billing cycle.
What happens at the limit
- If you hit your RPS limit, requests may be delayed or rejected.
- If you consume your monthly quota, requests may be blocked until the next billing cycle or until you upgrade.
Upgrades and plan changes
- Plan changes may adjust your available quota and rate limits immediately or from the next cycle, depending on the billing flow shown at checkout.
- Public pricing pages and dashboard plan details should always be treated as the current source of truth.
Why heavy methods are weighted
Some RPC calls place much more load on nodes than simple balance or block-number requests. Weighted billing keeps plans readable while protecting shared infrastructure from a small number of very expensive queries.