Billing and Usage
Usage-metered HRS lookups, report jobs, export volume, webhook activity, and organization-level spend from one enterprise billing surface.
Usage billing remains tied to real operational primitives instead of seat counts or model-tier upsells.
The billing page should make spend concentration obvious before the invoice closes.
Technical and finance owners can see the same usage pressure points from the same page.
Largest cost lane this period, driven by consent-backed lookups and expanded history review.
Healthy test traffic with low spend and clean key hygiene.
Second-largest billing lane, mainly finance and compliance packages.
That keeps the commercial model tied to the operational value customers actually consume instead of forcing everything into a seat count.
Threshold alerts, invoice previews, and per-key consumption stay close to the platform dashboard instead of hiding in a separate finance-only page.
That leads to predictable spend and fewer surprises once an organization moves from sandbox to production volume.
That makes usage billing feel operationally safe instead of mysterious, especially once multiple projects and exports start moving at the same time.
{
"period": "2026-03",
"lookups": 11284,
"expanded_history_calls": 904,
"report_jobs": 37,
"webhook_deliveries": 182114,
"project_breakdown": [
{ "project": "sandbox-workforce-review", "cost_usd": 428.11 },
{ "project": "production-underwriting", "cost_usd": 2984.42 }
]
}Usage billing should stay transparent by project, workload, and period so teams can explain the bill without leaving the workspace.
The billing home should show the live invoice shape before teams open a project lane.
The largest spend driver belongs on the first billing screen.
Threshold pressure should remain visible before finance needs to escalate.
The main unit of value should be visible from the billing surface itself.
Heavy packaging work should stay visible because it shifts spend and operator behavior.
Delivery and operator traffic should be explicit instead of buried in one total.
Usage billing follows the real enterprise primitives: successful HRS lookups, expanded-history retrievals, export jobs, report runs, and webhook volume where policy applies.
That keeps the commercial model tied to the operational value customers actually consume instead of forcing everything into a seat count.
The billing surface breaks usage down by organization, project, environment, report job, and export workload so finance and engineering can see the same truth from different angles.
Threshold alerts, invoice previews, and per-key consumption stay close to the platform dashboard instead of hiding in a separate finance-only page.
The platform also keeps high-cost workflows visible so teams understand when heavier reports, exports, or assisted review flows are driving the bill.
That leads to predictable spend and fewer surprises once an organization moves from sandbox to production volume.
Billing should expose the next invoice shape before the month closes. Threshold alerts, cost concentration by project, and report-heavy usage spikes should all stay visible to both technical and finance owners.
That makes usage billing feel operationally safe instead of mysterious, especially once multiple projects and exports start moving at the same time.