What the first issue establishes
- One offer identity for provider, model route, SKU, unit, mode, tier, resolution, audio, and region.
- A direct provider source and visible check date for every accepted observation.
- A quarantine gate for changes of 40% or more, unit changes, parser changes, and ambiguous mappings.
- Historical observations remain auditable but do not drive current cheapest claims.
What future issues contain
Each verified change will show the exact old and new offer, percentage change, source, check time, configuration, and correction history. New, removed, restored, increased, and decreased offers are separate event types.
Corrections stay visible
A corrected issue links the revised evidence and date. APIDir does not silently rewrite a published price history.
Submit a source correction →Questions developers ask
Did Issue 1 find an AI API price drop?
No. Issue 1 is the fresh baseline, so APIDir has no earlier accepted observation that can support a verified change claim.
What qualifies as a verified price change?
The old and new observations must refer to the same provider offer, model route, billing unit, mode, tier, resolution, audio setting, and region, with direct source evidence.
What happens when a price change looks suspicious?
A change of 40% or more, a unit change, or an ambiguous mapping is quarantined for manual review before it can appear in APIDir Delta.