As checked 2026-10-25: Public pages rarely disclose the exact bill for a large enterprise deployment. This is a dated economics guide, not a permanent price guarantee or a personal hands-on benchmark.
Scope: global English reference; USD list prices where shown; local eligibility, currency, taxes, negotiated terms and model release dates require separate confirmation. Dynamic source-page prices have a check date, not a verified initial effective date.
List price and contracted price are different evidence
Public pages rarely disclose the exact bill for a large enterprise deployment. A customer may purchase named seats, consumption commitments, dedicated instances, priority throughput and professional services under one agreement. Cohere’s public pricing illustrates the contrast between token-metered APIs and dedicated Model Vault instance rates. Google’s enterprise infrastructure lists provisioned-throughput options. Neither figure should be represented as the final price of an account-specific negotiated contract.
Model the whole term
For a twelve-month agreement, distinguish upfront annual licenses, monthly minimum spend, pay-as-you-go overages and prepaid balances that expire. Where the contract allows a shared commitment, track which products draw it down. Record billing currency and invoice terms. A discount on token input does not necessarily lower storage, networking, region premiums or support charges. An early termination obligation can dominate nominal model-inference savings.
A simple scenario
Imagine 80 active seats with a hypothetical $25 monthly list rate: baseline seat spend is 80 × 25 × 12, before tax. Add a variable API bill, staff onboarding, internal compliance reviews, administrative maintenance and output QA. A 20% headline discount on seats reduces only the eligible seat line; it should not be applied to unrelated API or support SKUs. The numeric scenario is an arithmetic teaching aid, not a real vendor quote.
Compare like with like
An enterprise-hosted deployment may include stronger geographic controls and audit guarantees at a higher unit rate; a cloud reseller may bill through existing commitments but have different release timing. Request a line-item quote and a clear statement of uptime, data processing, regional availability, renewal adjustments and reserved capacity. Test the contract against high, medium and low utilization assumptions.
Procurement checklist and alternatives
Ask what happens if usage is below minimum, the service becomes unavailable in a region, a model is retired, or a desired feature is excluded. Record who can view usage and set spending caps. An internal model served on rented compute may appear cheaper on tokens, but shifts hardware operations, patching, security and quality evaluation onto the buyer. Document these costs before declaring a winner.
A negotiation worksheet
Ask the supplier to separate seat price, included usage, token overage, dedicated capacity, region premium, data retention, support, training, administration and termination obligations. For each line, record list price, quoted price, duration, renewal rule and which department pays. If a salesperson mentions a volume discount, request its applicable SKUs and minimum purchase threshold in writing. A discount on compute instance-hours may not extend to speech or image inference. Preserve the original contract currency and do not promise an exchange rate for invoices not yet settled.
Utilization decides dedicated economics
A dedicated endpoint that costs a fixed amount per hour may look efficient under peak traffic, yet waste money overnight. Simulate weekdays, weekends and seasonal peaks, not just aggregate monthly request volume. Calculate delivered accepted outputs per active hour, and account for standby, autoscaling, deployment and incident response. A managed shared API can be cheaper for spiky traffic even when its nominal per-token price looks higher. Conversely, isolation and predictable service levels can justify a capacity premium where contractual requirements demand them.
Decision checklist
- Identify the specific plan or API endpoint, model version, region and currency before pricing a job.
- Measure input, output, caching, generated media and failed-job units separately.
- Check the official pricing page again before procurement, especially if the SKU has no effective-date notice.
- Keep source evidence and a timestamped price ID; do not treat unknowns as zero.
Pricing evidence boundary
This cost discussion concerns Multi-vendor. Reproduce a quote only with its exact model or plan identifier, chargeable unit, billing region, processing mode and timestamp; a changing vendor rate card is not a permanent price guarantee. If any one of these dimensions is missing, keep the associated rate and worked scenario under editorial review instead of filling the gap with an estimate.
Sources & Further Reading
- Cohere dedicated instance pricing distinct from API tokens — official first-party source, accessed 2026-10-25; original effective date not specified in source.
- Claude individual monthly subscription and team purchasing are distinct from API — official first-party source, accessed 2026-10-25; original effective date not specified in source.
- Cloud Gemini and tools are billed on cloud SKU/region with separate charges — official first-party source, accessed 2026-10-25; original effective date not specified in source.
- ChatGPT individual and enterprise plans are distinct from API purchasing — official first-party source, accessed 2026-10-25; original effective date not specified in source.