Opsmeter.io logo
Opsmeter.io
AI Cost & Inference Control
Integration docs

Implementation guide for AI cost control

Ship telemetry fast, keep attribution stable, and move from ingest to governance without changing your app network path.

Recommended path

Start with direct ingest, validate one stable payload shape, then harden budgets, retries, and incident workflows.

What this page answers
  • How provider and model names map into Opsmeter.io pricing logic.
  • What to do when model pricing is missing or unknown.
  • How catalog naming keeps cost calculations stable over time.
QuickstartShip a first payload and validate required fields in minutes.Open guide
No-proxy telemetryKeep your app path unchanged while preserving request-level attribution.Review flow
OperationsSet budget posture, retry rules, and escalation checks for production.Harden runtime
Updated for 2026API v1 Read cost playbook npmPyPIGitHub

Implementation rhythm

5 minfirst ingest path
No proxyapp path unchanged
One schemaacross providers

Use quickstart for initial payloads, then operations docs to harden production workflows.

Provider and model catalog

Before sending ingest payload, always fetch GET /v1/public/pricing-models and use the provider/model strings exactly as returned.

Rule: 1) Pull catalog, 2) copy provider/model exactly, 3) send payload.

If provider/model is not found in catalog, ingest falls back to unknown and costUsd = 0 until pricing is added.

OpenAI

ModelInput PriceOutput PriceEffective fromAction
gpt-4o-mini
$0.15/ 1M tokens
$0.6/ 1M tokens
2026-02-06
gpt-4-1
$2/ 1M tokens
$8/ 1M tokens
2026-02-06
gpt-4o
$2.5/ 1M tokens
$10/ 1M tokens
2026-02-06
gpt-4-1-mini
$0.4/ 1M tokens
$1.6/ 1M tokens
2026-02-06
ada
$0.4/ 1M tokens
$0.4/ 1M tokens
2026-02-06
ada-batch
$0.2/ 1M tokens
$0.2/ 1M tokens
2026-02-06
babbage
$0.5/ 1M tokens
$0.5/ 1M tokens
2026-02-06
babbage-batch
$0.25/ 1M tokens
$0.25/ 1M tokens
2026-02-06
Showing 1-8 of 160

Pricing overrides and auditability (enterprise workflow)

Use pricing overrides only when contract-specific rates must differ from the default catalog. Keep overrides versioned by effective date and preserve immutable historical snapshots for reporting integrity.

  • Define override scope clearly (provider, model, effective date, workspace/account scope).
  • Require explicit approval before activation.
  • Track reviewer, approval timestamp, and expiration policy for temporary overrides.
  • Run reconciliation checks after each override release.

See full guidance: Pricing table overrides: enterprise workflows & auditability.