Legacy task generation

POST /v1/task-generations, POST /v1/tasks/{task_key}/edits and POST /v1/task-generations/{id}/continue-auth are retired. They return HTTP 410 with error_code: "legacy_generation_retired", retryable: false, and no credit charge.

Create a replacement API from the dashboard. Existing APIs can still be discovered with GET /v1/tasks and executed with POST /v1/tasks/{task_key}/runs.

The MCP create_scraper and create_scraper_and_run tools call the retired generation route. Use task discovery and execution for existing APIs.

Read existing generation records

GET /v1/task-generations/{id} retrieves an existing generation record. GET /v1/task-generations/{id}/endpoints lists its published endpoints and supports limit and cursor pagination. GET /v1/task-generations/{id}/evidence retrieves available generation evidence. These read operations require an API key authorized for the team and do not start or resume generation.

See task discovery, task execution and request and error handling.