job_cancel
Cancel a previously accepted BeatBandit job through its native owner. This stops further work where possible; already submitted provider work may still incur costs. Read job_get for terminal status and settled billing.
When to use
- Use when the user explicitly asks to stop an accepted job, using the exact parent job_id returned by Start.
- Reuse the same job_id after a lost response. Native terminal-state checks make a repeated cancellation harmless.
- Cancellation creates no new charge or reservation; it does not promise a refund. Only a settled job_get billing receipt establishes actual charges and released credits.
When not to use
- Use job_get to observe progress or read results without requesting cancellation.
- Use story_revision_run with adaptive_revision and phase=stop for a revision session's native stop operation.
- Do not cancel a child independently of its owning parent or use this to delete saved writing.
Examples
- “Stop the screenplay Writer job I just accepted.”
Anti-examples
- Delete Chapter 3. Use novel_mutate with current revisions and native deletion confirmation.
Backend capabilities
job.cancel
Input schema
job_cancel input
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"required": [
"job_id"
],
"properties": {
"job_id": {
"type": "string",
"format": "uuid"
}
},
"additionalProperties": false
}Output schema
job_cancel output
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"required": [
"job_id",
"status",
"credits_skipped_reason",
"next_actions"
],
"properties": {
"job_id": {
"type": "string",
"format": "uuid"
},
"status": {
"type": "string"
},
"message": {
"type": "string"
},
"credits_skipped_reason": {
"const": "no_op"
},
"next_actions": {
"type": "array",
"items": {
"type": "object"
}
}
},
"additionalProperties": false
}← All toolsv1 · simple_action