Documentation / Getting started

One request.
Your next dataset.

An API-first workflow for realistic synthetic data, streamed to wherever you build.

API contract preview. You can manage your account and keys now. The generation endpoint is not live yet; examples below describe the planned V1 interface.

Quickstart

Create a key, set it in your server environment, then write the response directly to a file.

Get API key ↗

Terminal / contract preview

curl https://api.vctr04ai.com/v1/generate \
  -H "Authorization: Bearer $VCTR04_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"prompt":"US ecommerce transactions",
       "rows":100000,"format":"jsonl"}' \
  --output train.jsonl

Keep your key server-side

Send your VCTR04 key as a Bearer credential in the Authorization header. Never use a Supabase key to call the generation API.

Request header

Authorization: Bearer $VCTR04_API_KEY

Keys begin with vctr_live_. The console reveals a new key once, then displays only its prefix. Store it in a secrets manager—not frontend code, source control, or a URL. Revoke lost or exposed keys and create replacements.

Describe what you need

Planned generation request fields
Field	Purpose
prompt	Describe the domain, relationships, and constraints.
rows	The number of rows to generate.
format	JSONL for independently streamable rows; CSV is planned.
schema	Optional explicit field structure.
seed	Optional generation seed.

Final limits, error codes, and quality controls will be documented alongside the production API. No invented quotas or runtime guarantees.

Consume bytes, not a giant object

Write chunks to your destination as they arrive. Avoid loading an entire response with response.json(), response.text(), or a growing in-memory array. Close the request when cancelling a generation.

The website is not a dataset viewer. Bulk results travel from the generation API to your destination, without passing through this dashboard.

The same interface for every tool

Python, TypeScript, shell scripts, Codex, Claude Code, and CI can use the same REST contract. Keep credentials in the execution environment and stream to a file or storage.

Dedicated vctr04 Python and CLI packages and @vctr04/sdk for TypeScript are planned. They are not required to use REST and are not presented here as released packages.

Generated. Streamed. Gone.

VCTR04 does not persist generated dataset payloads. Your account contains identity, key metadata, plan information, and aggregate usage—not generated rows.

Save the streamed output at your destination. There is no dataset history or later download from this console.

One request.Your next dataset.