Model pricing
VeriProof estimates model cost from recorded token counts and the rates in Model pricing. The platform catalog is a reference, not a vendor price guarantee. Confirm the vendor’s current price before using an estimate for a purchasing decision.
Understand pricing sources
VeriProof checks rates in this order and uses the first match:
- Your custom rate, if it applies to the model and event date.
- The catalog rate for that exact model.
- A provider estimate labeled Tier estimate.
When several custom rates apply, an exact model name takes priority over a wildcard pattern. Otherwise, the longest matching pattern applies. If matching patterns are identical, VeriProof uses the latest effective rate for the event date.
The page reports an error when the catalog is unavailable because estimates without an organization override may be inaccurate.
Check the source before comparing models. A Tier estimate is less specific than a rate for the exact model and should remain labeled as an estimate.
Add an organization rate
Confirm the commercial source
Use the current contract, invoice schedule, or approved internal rate. Keep that source outside VeriProof with the pricing owner.
Enter the model pattern
Use an exact model name or one trailing wildcard, such as gpt-4o-*. The most specific matching pattern applies.
Prefer an exact name when the agreement covers one model. A wildcard can affect several model versions, so review the names it will match.
Enter input and output rates
Enter non-negative rates in US dollars per 1,000 tokens. Do not combine input and output charges into one value.
If your source quotes a price per million tokens, divide that price by 1,000 before entering it. For example, a hypothetical rate of $2 per million becomes $0.002 per 1,000 tokens. This is a unit-conversion example, not a vendor quote.
Set the effective date
Choose the date from which the rate applies, then save the override.
Use the agreement’s effective date, not automatically today’s date. The rate applies to eligible sessions recorded on or after that date.
Check the reported cost
Review a cost result for the model and confirm that it shows the intended rate and source.
Check the model name, session date, token counts, and separate input and output rates. A saved override alone does not confirm the reported cost is correct.
An incorrect override changes cost and value reporting. Use a reviewed pricing source and verify the result after every change.
Maintain rates
Edit the rates when the model pattern stays the same. Delete an override when it should no longer apply. The platform catalog is read-only; organization rates are managed separately.
After deleting an override, check which remaining override, catalog rate, or provider estimate applies. Deletion does not mean the model’s cost becomes zero.