OperatePlatform API v1

Migrate from the legacy API

Adopt the Project-centred `/v1` contract deliberately; legacy routes and legacy customer applications remain separate.

Two explicit products

The Platform API uses https://api.autocontentapi.com/v1, scoped Platform keys, Projects, Sources, priced Generations, first-class Assets, and prepaid USD. Legacy routes use their existing contracts and credentials and are not compatibility aliases for /v1.

Migration sequence

Create and confirm a Platform Project for each durable brand/workspace boundary.
Ingest reusable files, text, and URLs as Project Sources.
Replace output-type switches with explicit first-class assets entries.
Preview every Generation, accept under max_cost_usd, and retain an idempotency key.
Consume Asset Artifacts and signed Platform webhooks.
Move recurring jobs to Content Loops only after one-off behavior is correct.

Cut over safely

Run legacy and Platform integrations side by side with distinct credentials and resource IDs. Stop creating new legacy work only after the Platform path is verified for your requests; do not reinterpret legacy credit amounts as Platform USD.