Adding pricing data

An optional, manually-curated manifest field. Omit it entirely rather than forcing a value.

The four models

notes and url matter more than the number

A price goes stale the moment a vendor changes plans, but a clear note plus a link to verify stays useful regardless. Verify current pricing against the vendor's own page before writing it — not from memory, since pricing pages change — and record the date you checked in the note itself.

"pricing": {
  "model": "freemium",
  "estimateUsd": 25,
  "notes": "Free tier: 50,000 MAU, 500MB database. Pro $25/mo removes
            project pausing and adds daily backups. Checked 2026-07-14.",
  "url": "https://supabase.com/pricing"
}

Omit it when there is nothing to price

Most modules land in 'no cost data' on purpose. A testing library or a UI feature has no vendor to price, so pricing stays unset rather than forced to a meaningless value.