|
|
|
Hi [First name],
|
|
What is migrating:
|
|
Enrichments and list builds in Riveter are becoming one thing: Datasets. A dataset holds the rows you build or upload and the columns you enrich, and it works the same way in the app, the API, and the MCP server.
Why the migration:
Dataset enrichments will be much more credit efficient, faster, and easier to work with, both via the API and in Claude or ChatGPT.
|
|
|
|
Migration timeline:
|
|
|
|
On October 28th your existing enrichments and list builds will be copied into datasets automatically. Nothing is deleted, and the legacy enrichments keep running.
|
|
|
|
On November 6th your enrichments are available only as datasets, and legacy enrichments and list builds will be closed.
|
|
|
|
You can also migrate now. Open Datasets and click Migrate to Datasets. The copy takes a few minutes and you can keep working while it runs. Your dataset pages and the dataset API endpoints open for your account as soon as it finishes.
|
|
|
The dataset endpoints are already live: create a dataset from rows or from a prompt, add rows, add output columns, and fill them with POST /v1/enrich. They are documented at https://docs.riveterhq.com/. Calls that reference a legacy enrichment id keep working until November 6th.
|
|
|
|
|
|
|
|
|
|
|
