Cloptima layers customer- or org-scoped contract rates, commitments, and credits on top of provider list pricing, so effective cost matches what you actually pay — previewed and approved before it ever changes a number in production.
Provider list prices are a starting point, not the truth. Negotiated discounts, commitments, credits, and cached-token rates all change what you actually pay, and a spreadsheet beside the platform soon drifts from what it reports.
Contract price sheets are scoped to your organization and forward-dated, layered on the global model catalog without changing it. Before approval, Cloptima previews the dollar effect against real usage. Approved rates apply to new usage within 24 hours.
Create a price sheet for your first contracted customer or business unit, add the rate overrides your contract specifies, run the preview against the last full billing period, and route it through approval before it goes live.
Effective cost follows one explicit order: contract override, commitment, credit, then retail price. Each report stays tied to the pricing rules in force at the time, and rate changes deploy as versioned layers, so an approval never half-applies.
OpenAI-compatible gateway routing vs. full FinOps control plane, attribution, and hot-path team budget limits.
Routing and guardrails vs. pre-flight budget enforcement, finance ledger, and p95 7–9ms end-to-end latency.
Edge proxying vs. enterprise attribution, team quota enforcement, and cost reporting.
LLM observability logs vs. active request-path budget controls, response caching, and unit economics.
Point your SDK at the gateway, bind a policy, and watch the first call land on the ledger.