Monitor plan usage

HeliumGeek tracks how many distinct gateways each API client touches during the monthly billing cycle. Usage telemetry is returned with every gateway- and radio-related response so you can react before hitting enforcement limits.

Need a different quota or clarification on thresholds? Email info@heliumgeek.com with your use case and we can adjust the plan that backs your API key.

Response headers

Header	Description
X-Gateway-Quota	Monthly distinct-gateway allocation assigned to your API key.
X-Gateway-Usage	Count of unique gateways seen this cycle (including the current call).
X-Gateway-Usage-Percentage	Usage as a percentage of your quota (rounded to two decimals).
X-Gateway-Quota-Status	ok, warning, critical, or exceeded, based on configured thresholds and grace limits.

These headers appear when quota tracking is enabled (monitor or enforce modes). In disabled mode the headers are suppressed.

Thresholds and limits

Configuration values are controlled server-side, but the defaults explained below reflect production settings:

• Quota – base allowance for distinct gateways per month.
• Grace limit – quota + 10%. Requests continue to succeed so normal operations are not disrupted, but the quota status transitions to warning (≥ 80%) or critical (≥ 95%). Treat any grace usage as temporary—we monitor overages and will reach out if you consistently exceed your plan.
• Hard limit – quota + 50%. Surpassing this level blocks all gateway requests to prevent abuse.

The X-Gateway-Quota-Status header follows these rules:

• ok: usage is below the warning threshold.
• warning: usage percentage ≥ warning threshold (default 80%).
• critical: usage percentage ≥ critical threshold (default 95%).
• exceeded: usage is above the grace limit. Future gateway requests may return HTTP 429 Too Many Requests when enforcement is enabled.