GET /billing/consumption returns the consolidated figure for the current cycle: how much the company has already consumed, what the effective cap is and how much is left.
🤖 Endpoint:GET https://requests.production.judit.io/billing/consumption. The response is synchronous (HTTP 200) and carriesconsumption,max_consumption,remainingand the cycle’s opening and closing dates.
When to use it
Internal dashboards
Show cycle consumption and remaining balance on your own panel, without depending on the Judit dashboard.
Usage alerts
Notify your team when consumption crosses 70%, 80% or 90% of the contracted cap.
Batch pre-flight
Before firing a large volume of queries, check whether
remaining covers the planned operation.Cycle-based reporting
Use
cycle_started_at and cycle_ended_at to align your reports with the real billing window.Step 1: Make the Request (GET)
GET https://requests.production.judit.io/billing/consumption
Authentication
Requiredapi-key header, filled with an admin key for the company. The route takes no parameters — the company is identified from the api-key itself, and company_id comes back in the response.
Plan availability
Available to accounts on the HOMOLOG, PAID and JUDIT plans.Request Examples
Step 2: Read the Response
Response Fields
max_consumption is the effective cap, not the contractual one. If the company has extra post-paid credits released, they are already added into this number — which is why it can change during the cycle even without a plan change.Usage Examples
Alert on threshold
Pre-flight before a batch
Before queueing a large volume of requests, check whetherremaining covers the planned operation. This avoids interrupting a job halfway through because the cap was exceeded.
Next Steps
Consumption History
List the period’s requests and infer the cost of each operation.
Available Credits
Check the remaining balance on pre-paid accounts.