> Source: https://vitna.ai/docs/concepts/sku
> Raw Markdown: https://vitna.ai/docs/concepts/sku.md
> Corpus index: https://vitna.ai/llms.txt

# Sku

The unit Vitna prices: one thing, sold by one provider, that you could buy.

`gpt-5-pro` from OpenAI is a sku. The same open-weight model served by three
different providers is three skus, because three sellers are quoting three
prices for it, and the difference between those prices is exactly what the
record exists to show.

## Fields

From `witness.sku`:

| Field | Meaning |
|---|---|
| `id` | Stable internal id |
| `slug` | The public identifier, unique across every class |
| `name` | What it is called |
| `classId` | Its [component class](component-class.md) |
| `providerId` | Who sells it |
| `attrs` | Context window, form factor, tier, and for compute the product row it prints on |
| `succeedsSkuId` | The sku this one replaces, where a provider named one |
| `featured` | Whether it appears in the three-row tape on the homepage |
| `status` | `active` by default |

`slug` is what you pass to the API:

```bash
curl https://vitna.ai/api/v1/skus/gpt-5-pro/history
```

## Sku against product

A sku is a seller's offer. A **product** is the thing several sellers are
offering, and it lives in `attrs` rather than as its own table.

`H100 SXM` is a product. Six providers renting one are six skus grouped on it.
That grouping is what makes a [spread](../api/v1/prices/spreads.md) computable: without
it there is no peer set to take a minimum and a maximum over.

Product slugs are lowercased and dashed, so `H100 SXM` becomes `h100-sxm`.

## Featured is a property of the sku

Which three rows the homepage tape shows is stored on the sku, not chosen in
the page. The marketing surface and the market therefore cannot drift: there is
no slice taken at render time that could disagree with the record.

## How a sku comes to exist

Not by being typed in. The collector reports priced rows it saw that the
registry does not track, as candidates in `witness.sku_candidate`. It counts
sightings and holds `UPDATE` on the counting columns only.

Promoting a candidate into a sku is a person's act, and it is what writes the
`launch` [market event](market-event.md) recording when Vitna first read the
row. Registering a back catalogue that a provider did not just launch uses
`--backfill`, which registers the sku and writes no event, because claiming a
launch that did not happen would put a false statement in the log.
