Skip to main content
AgentMeter separates usage reporting from pricing. Your application sends raw usage. AgentMeter applies pricing on the server.

​
Why server-side pricing

Server-side pricing keeps cost accounting consistent when:
  • Providers change rates.
  • Customers have custom contracts.
  • A non-LLM source needs a custom metric price.
  • Historical events need backfill or reconciliation.

​
Pricing sources

AgentMeter can price:
  • LLM token usage by provider and model.
  • Non-LLM usage by metric, such as characters, requests, seconds, or executions.
  • Customer-specific pricing versions for billing workflows.

​
Unknown pricing

If AgentMeter receives usage without a known price, it can accept the event and flag the source for pricing setup. This keeps telemetry flowing while making pricing gaps visible.

​
Customer billing workflow

A typical billing workflow is:
  1. Track customer usage through SDK telemetry.
  2. Configure builder and customer pricing.
  3. Review usage and cost for the billing period.
  4. Generate draft invoices.
  5. Finalize, void, or export invoices based on your billing process.
  6. Share customer-facing portal links when customers need usage visibility.

​
Best practices

  • Review unknown pricing tasks before sending invoices.
  • Keep pricing effective dates explicit.
  • Use stable external customer IDs.
  • Audit pricing changes before billing customers.