ErgOpsDocs

Usage and contract capacity

ErgOps Embedded is licensed through B2B agreements, usually annual. Your agreement includes a number of customer-attributed calculations for a contract period. This page explains what counts and how to follow your usage.

What counts as usage#

One unit is one successful emissions calculation attributed to one of your customers. A unit is recorded when:

  • a Live Developer API calculation succeeds, or
  • an already-calculated transport activity is linked to a customer in the panel.

Each calculation is counted once, however many times it is read, reported or reused.

What does not count#

Not counted Why
Test API calculations Test is for integration work
Retries with the same Idempotency-Key Same logical calculation
Failed or rejected calculations No result was produced
API reads (GET) Reading is free
Webhooks, portal views, customer reports Distribution, not calculation
Reuse in Scope 3 or product footprints Same underlying calculation
API keys and customer accounts Capacities, not usage units

Contract period and capacity policy#

Usage is summed across your contract period — monthly, annual or a custom term such as 15 March to 14 March. Dates are evaluated in UTC. Renewals and amendments are added as new terms; past usage is never deleted.

Your agreement sets one of three policies:

Policy When included capacity is used up
Soft Calculations continue; usage status becomes Over limit.
Hard New Live API calculations are rejected until capacity is extended.
Unlimited No ceiling; usage is still measured.

Check your usage#

Open ErgOps Embedded → Usage (Organization Managers). The Contract Usage page shows:

  • the contract period and plan
  • included calculations (∞ when unlimited)
  • used and remaining calculations
  • a status: Normal, Approaching limit (80% or more), Over limit or Unlimited
  • a monthly breakdown

Note The small usage strip on the Customers page shows the current month. The Usage page shows the whole contract period. Use the Usage page for contract decisions.

Rate limits are separate#

Rate limits control how fast API requests may arrive. They protect the service and are not billing units. See Rate limits.