Description
Account & Usage endpoints help you monitor Compute Units (CU), quota consumption, and usage breakdowns so you can:- Track spend and remaining quota for the current billing period
- Alert when usage exceeds internal budgets
- Identify which datasets/endpoints drive the most consumption
- Validate that automation is behaving as expected (no runaway queries)
Endpoint Matrix
| Endpoint | Summary |
|---|---|
GET /usage | Retrieve CU consumption, remaining quota, and usage breakdowns |
Key concepts
- Compute Units (CU): BlockDB bills most API calls in compute units.
- Billing period: Usage is tracked within your plan’s billing window.
- Usage by dataset: Responses may include per-dataset usage so you can attribute spend.
Best practices
- Poll
/usageon a schedule (hourly or daily) and alert on unexpected changes. - Prefer tighter filters and smaller ranges to reduce CU costs.
- Use cursor pagination rather than huge limits.
See Also
- Pricing — CU pricing model
- Rate Limiting — RPS limits and quotas
- Authorization — API key usage and auth