Skip to content
GigAI

Cancel the running assess batch

POST
/api/postings/assess/cancel
curl --request POST \
  --url http://127.0.0.1:8765/api/postings/assess/cancel \
  --header 'Content-Type: application/json' \
  --data '{}'

Cancel the running assess batch: no further model call; what finished is kept. 0.1.11.5: stops the live assess batch of this project. No further model call starts. THE CALLS IN FLIGHT FINISH and their assessments are stored like any other (at most 4; their tokens are spent already), then the batch ends: batch.status is cancelling until then, and GET /api/postings/assess/status then says last.status cancelled with how many were assessed and how many were never started. Every assessment already stored stays. cancel_requested is how many batches were asked (0: none runs, nothing changed). A batch started in a terminal is cancelled the same way; the command is gigai scout jobs assess --cancel. Stopping the server (gigai scout stop) is different: it ends the model processes the server started, and what they would have answered is lost.

Request Body

Section titled “Request Body”
Media typeapplication/json
object
Example
{}

Responses

Section titled “Responses”

200

Section titled “200”

Success.

Media typeapplication/json
object
schema_version
required
Allowed value: scout-assess-batch:1
key
additional properties
any
Example
{
  "batch": {
    "assessed": 12,
    "estimate_seconds": 1730,
    "failed": 1,
    "here": true,
    "id": "batch_5f0c2d9a41e84b6f9d3f2a7c1b0e6d58",
    "in_flight": 4,
    "pending": [
      "https://boards.greenhouse.io/acme/jobs/101"
    ],
    "profile_id": "prof_1",
    "started_at": "2026-10-06T09:30:00Z",
    "status": "cancelling",
    "total": 50
  },
  "cancel_requested": 1,
  "last": {
    "assessed": 14,
    "error_code": null,
    "failed": 0,
    "failed_codes": [],
    "finished_at": "2026-10-06T09:12:40Z",
    "id": "batch_0d1e7c55a3b94c1e8a6f4b2d9c7e3f10",
    "more_after": 55,
    "not_started": 36,
    "requested": 50,
    "status": "cancelled"
  },
  "running": true,
  "schema_version": "scout-assess-batch:1"
}

403

Section titled “403”

Forbidden / forbidden_origin: loopback peer and Host 127.0.0.1:<port> or localhost:<port> only (Origin too on writes).

Media typeapplication/json
object
error
required
object
allowed_keys
Array<string>
code
required
string
message
required
string
key
additional properties
any
Examplegenerated
{
  "error": {
    "allowed_keys": [
      "example"
    ],
    "code": "example",
    "message": "example"
  }
}

404

Section titled “404”

Target_unavailable

Media typeapplication/json
object
error
required
object
allowed_keys
Array<string>
code
required
string
message
required
string
key
additional properties
any
Example
{
  "error": {
    "code": "target_unavailable",
    "message": "..."
  }
}

415

Section titled “415”

Unsupported_media_type: writes need Content-Type: application/json.

Media typeapplication/json
object
error
required
object
allowed_keys
Array<string>
code
required
string
message
required
string
key
additional properties
any
Examplegenerated
{
  "error": {
    "allowed_keys": [
      "example"
    ],
    "code": "example",
    "message": "example"
  }
}

422

Section titled “422”

Unknown_key

Media typeapplication/json
object
error
required
object
allowed_keys
Array<string>
code
required
string
message
required
string
key
additional properties
any
Example
{
  "error": {
    "code": "unknown_key",
    "message": "..."
  }
}