# Quality terms

URL: /products/data/quality · Id: `page:products/data/quality`

> What a Dataset promises about its own quality: uptime with credits on the Offer, freshness by schedule, published coverage, and corrections that are counted.

A data buyer is promised more than an answer: the answer must be up, fresh and right. Each of the three is stated as a term a buyer can check, never as an adjective.

## Up
An uptime term on the [Offer](/business/nouns/offer) promises how much of each month lookups answer, and what a buyer gets back below it. Credits apply themselves on the next invoice; nobody files a claim. [Promise uptime on a plan](/products/api/promise-uptime) is the guide.

| Monthly uptime | Credit |
| --- | --- |
| Below 99.9% | 10% of the month's fee |
| Below 99.0% | 25% of the month's fee |

## Fresh
Freshness is the `refresh` schedule, published beside the price, and every record's `refreshedAt` shows whether the schedule held. A buyer filters out what is older than it accepts. A credit for a [Source](/business/nouns/source) read late has status `planned`.

## Covered
Coverage is published as a map before any lookup, and a key outside it costs nothing. [Coverage](/products/data/coverage) covers the check.

## Right
A value that was wrong when served is corrected with its reason and its evidence, and every reader hears about it. Corrections per thousand values served is the [Dataset](/business/nouns/dataset)'s own quality number. [Corrections](/products/data/corrections) has status `planned`.