Customize a data product
What each Offer and license changes, what a buyer shapes for itself, and what never varies between two buyers of the same records.
The records are the same for every buyer; the Offer decides what a buyer may do with them and how it pays. A buyer shapes its own use with its queries, its schedule and its keys.
What an Offer changes
| An Offer sets | Example | Read |
|---|---|---|
license | internal, display or redistribute | Licensing your data |
| Its Price and unit | $49 a month for 50,000 lookups, then per thousand | Pricing models |
| Its Entitlements | Lookups only, or lookups and bulk export | Lock a feature to a plan |
| What a call past a Limit gets | stop, overage or upgrade | Cap usage on a plan |
| Its uptime terms | 99.9% a month, with credits | Promise uptime on a plan |
Every Offer on a Dataset API starts from the same defaults. Misses are free, the same key twice inside 24 hours counts once, and a test key reads synthetic records.
What a buyer shapes
| A buyer sets | How |
|---|---|
| Which records it reads | A filter or a saved query over the Dataset |
| How it receives them | Lookups, an export on a cadence, or the change feed |
| Where bulk lands | A file in the Portal, or its own warehouse |
| One key per job | A nightly sync key that may only read, a checkout key, an agent's key |
What never varies
Every buyer reads the same value for the same key at the same time. A license changes what a buyer may do with a record, never the record.
What the builder changes
The builder changes the Noun, the Sources, the coverage and the refresh in the product file. Each change builds a new Version, and the Dataset's published facts change with it.