EXECUTION OPERATIONS

Submit asynchronously, then operate against durable Job state.

A production integration treats submission as the beginning of execution tracking—not as a synchronous AI result call.

SUBMISSION

Create execution state safely.

Request

POST /api/marketplace/services/code-gen/execute
x-api-key: dev_...
Idempotency-Key: execution-<unique-id>
Content-Type: application/json

{
  "input": {
    "prompt": "Generate a TypeScript utility for validating execution payloads.",
    "language": "typescript"
  }
}

Persist the returned Job reference and Workflow Run reference. Status and progress describe execution state; they do not replace the final result.

IDEMPOTENCY

Protect network retries from duplicate workload creation.

Reuse the same idempotency key when retrying the same logical submission after a transport interruption. Generate a new key only for a genuinely new execution intent.

JOBS, LOGS & TELEMETRY

Operate the workload after submission.

Job routes

GET /api/developers/jobs
GET /api/developers/jobs/:jobId
GET /api/developers/jobs/:jobId/logs
GET /api/developers/jobs/:jobId/telemetry

Persist jobId

Connect Tenzarch execution with your own application request.

Read status

Handle queued, routing, assigned, running, retrying, completed, and failed states.

Inspect operational detail

Use logs and telemetry for investigation.

Handle terminal outcome

Consume the result on completion or handle failure explicitly.