API Reference

Submits a pitch for a validation read and returns a job id to poll. The read is asynchronous, so you get a job back, not the verdict.

This is a quick read, not a live-signal run. The model reasons over the pitch you send and nothing else. It doesn't gather live demand: that heavier path is the full pipeline, not this endpoint.

Request Body

{
  "idea_description": "string (required, max 1000 chars)",
  "target_market": "string (optional)"
}

Response 202 Accepted

{
  "job_id": "val_1718...",
  "status": "processing",
  "estimated_completion_seconds": 60
}

Example

curl -X POST https://your-instance/api/v1/validate \
  -H "Authorization: Bearer ig_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "idea_description": "A booking tool for mobile dog groomers.",
    "target_market": "Independent groomers in the UK"
  }'

Polls a validation run. Call it with the job_id you got back from the POST and check status. Poll every few seconds until it reads completed or failed. The result block is present once the status is completed.

Response 200 OK

{
  "job_id": "val_1718...",
  "status": "processing" | "completed" | "failed",
  "result": {
    "score": 0,          // 0-100
    "verdict": "scale",  // "scale" | "pivot" | "kill"
    "kill_shot": "string",
    "market": 0,         // 0-100
    "feasibility": 0,    // 0-100
    "moat": 0,           // 0-100
    "summary": "string"
  },
  "error": "string"      // only on a failed run
}

While the run is still going, the body is just { "job_id", "status": "processing" }. The result object only appears on a completed run, and error only appears on a failed one.

Example

curl https://your-instance/api/v1/validate/val_1718... \
  -H "Authorization: Bearer ig_live_..."

Turns an idea into a runnable Next.js 15 app: App Router, a typed Drizzle schema, CRUD routes, and Stripe wiring when the idea is a paid product. Point it at a completed validation job that didn't read as a kill, or at a pooled idea by id. By default it returns a downloadable zip. Pass "format": "json" to get the file manifest back instead.

Request Body

{
  "job_id": "val_1718...",   // a completed validate job, not a kill
  "idea_id": "string",       // or a pooled idea, instead of job_id
  "format": "zip",           // "zip" (default) | "json"
  "multi_tenant": false,     // optional: tenant column + Postgres RLS per table
  "brand": {                 // optional white-label: ships under your name
    "name": "Northwind Studio",
    "accent": "#059669"
  }
}

Send a job_id or an idea_id, not both. Scaffolding before the validation job finishes comes back as 409: poll the job until its status is completed first. An unknown job_id or idea_id is 404. An idea that can't be resolved, or one that read as a kill, is 422: scaffolding is for ideas that cleared the read.

Response (zip) 200 OK

Content-Type: application/zip
Content-Disposition: attachment; filename="your-app.zip"

# the response body is the zip itself

Response (json) 200 OK

{
  "slug": "your-app",
  "file_count": 0,
  "spec": { /* the build spec */ },
  "files": [
    { "path": "app/page.tsx", "content": "..." }
  ]
}

Example

# zip (default): write the app straight to disk
curl -X POST https://your-instance/api/v1/scaffold/nextjs \
  -H "Authorization: Bearer ig_live_..." \
  -H "Content-Type: application/json" \
  -d '{ "job_id": "val_1718..." }' \
  -o your-app.zip

# json: get the file manifest instead
curl -X POST https://your-instance/api/v1/scaffold/nextjs \
  -H "Authorization: Bearer ig_live_..." \
  -H "Content-Type: application/json" \
  -d '{ "idea_id": "...", "format": "json" }'