Understand the current flow in three minutes.

Current Public Surface

• POST /v1/executions/extract
• GET /v1/executions/:id
• optional webhook delivery for completion notification

Evaluator Path

1. create an execution with POST /v1/executions/extract
2. receive an accepted-first response
3. poll GET /v1/executions/:id or optionally provide a webhook target
4. reach either succeeded or failed_safe
5. use the receipt viewer and ROI calculator where relevant

Minimal Live Request

curl -X POST https://nurturing-nurturing-production.up.railway.app/v1/executions/extract \
  -H "content-type: application/json" \
  -H "x-api-key: <YOUR_EVAL_API_KEY>" \
  -d '{
    "input": { "text": "phase1-success" },
    "outputContract": "contract:extract.result.v1",
    "budget": { "maximumEu": 1 },
    "idempotencyKey": "phase1-live-eval-1"
  }'

The create response is accepted-first. pollUrl is a relative path and should be resolved against the gateway base URL, for example https://nurturing-nurturing-production.up.railway.app/v1/executions/exec_mmz8xtgp_h5pael2y.

What You Get

• guaranteed / auditable task execution at the workflow boundary
• a workflow safety layer, not just an LLM call
• succeeded or failed_safe, not silent optimistic completion
• polling is a valid evaluator path; webhook is optional

Need Evaluator Review On One Real Payload?

Use the narrow design-partner path when you want to move from "interesting" to one sample payload, one target schema, and either polling or webhook as the return method.

Contact / Next Step