Pricing
One account and one API key for every Olenza product. Each product has its own plan and its own allowance: using up one never touches the other. Limits apply per account, across all of your keys.
Olenza Node — JSON-RPC
Full-node RPC. Units are the sum of method weights — see the method list.
- 5 requests / second (burst 10)
- 20,000 units / day
- 300,000 units / month
- Batch up to 5 calls
- Chains: All
- 15 requests / second (burst 30)
- 200,000 units / day
- 5,000,000 units / month
- Batch up to 20 calls
- Chains: All
- 40 requests / second (burst 80)
- 1,000,000 units / day
- 25,000,000 units / month
- Batch up to 50 calls
- Chains: All
Olenza Explorer API
Blocks, transactions and addresses as JSON, one format for every chain (ZEC, LTC). Each endpoint has a weight in units — see the Explorer API docs.
- 3 requests / second (burst 6)
- 5,000 units / day
- 100,000 units / month
- Chains: All
- 10 requests / second (burst 20)
- 100,000 units / day
- 2,000,000 units / month
- Chains: All
- 30 requests / second (burst 60)
- 500,000 units / day
- 10,000,000 units / month
- Chains: All
Bundles — Node + Explorer API
A Node plan and an Explorer API plan at one price. The two allowances stay separate, exactly as if bought one by one.
- Node: Starter — 15 req/s, 5,000,000 units / month
- Explorer API: Starter — 10 req/s, 2,000,000 units / month
- $34 if bought separately
- Node: Pro — 40 req/s, 25,000,000 units / month
- Explorer API: Pro — 30 req/s, 10,000,000 units / month
- $128 if bought separately
Questions
What is a unit? Each RPC method and each Explorer API endpoint has a weight. Simple calls cost 1 unit; heavier ones, such as a full block or an address history, cost more.
What happens at the limit? Requests get HTTP 429 with a Retry-After header until the next UTC day or month. Only the product you used up is affected.
Do I need two keys? No. One key works for Node and the Explorer API; each product counts against its own plan.