# Stop Task (WithZero Scheduler)

> Stop Task (WithZero Scheduler) is a paid API for AI agents from agents.withzero.xyz, paid per call via MPP, price unknown, status unknown (last checked 2026-09-10).

Stops a scheduled or on-demand task, closing the payment channel and refunding remaining escrow (direct rail) or releasing pending reservations (ZeroClick rail).

## Facts

- Endpoint: DELETE https://agents.withzero.xyz/api/v1/scheduler/tasks/{id}
- Price: price unknown
- Payment: MPP
- Status: unknown
- Last checked: 2026-09-10
- Activations on Zero: 1
- Provider: agents.withzero.xyz
- Website: https://agents.withzero.xyz
- Canonical page: https://www.zero.xyz/c/agents-withzero-xyz-stop-task-withzero-scheduler-28842398
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xuzIg1yleFkYRqZzA4Le9

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability agents-withzero-xyz-stop-task-withzero-scheduler-28842398 -d '<json body>'
```

Example prompt: Please stop the task with ID 3f2a1b4c-5d6e-7f8a-9b0c-1d2e3f4a5b6c on my WithZero scheduler — close the payment channel and refund whatever escrow is left.

## When to prefer this

Use this endpoint when you need to explicitly stop a task you previously created via the WithZero scheduler and want to trigger payment settlement — either to close a direct payment channel and reclaim unused escrow, or to release ZeroClick marketplace reservations. Prefer this over simply abandoning a task when cost recovery or clean resource cleanup matters.

## Known failure modes

- Task ID not found — 404 with error indicating no matching task
- Unauthorized access — task is owner-gated and caller lacks proof
- Task already stopped or in terminal state — may return 409 or idempotent response
- Invalid UUID format for task ID — 400 validation error
- Payment channel closure failure on-chain — may return 500 or partial state

## How this service works

Stop a task. Direct rail closes the payment channel and refunds remaining escrow. ZeroClick rail releases pending reservations and reports no refund because buyer billing is held by the marketplace. 📖 Full guide: https://scheduler.withzero.xyz/llms.txt

## Output

Returns a JSON object with the task ID, updated status, billing rail (direct or zeroclick), a channel close transaction hash (or null for ZeroClick), the amount in micros claimed by the seller, and the amount in micros refunded to the buyer.

## Request schema (JSON Schema)

```json
{
 "type": "object"
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "id",
  "status",
  "billing_rail",
  "channel_close_tx",
  "seller_claimed_micros",
  "buyer_refunded_micros"
 ],
 "properties": {
  "id": {
   "type": "string",
   "format": "uuid",
   "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  },
  "status": {
   "type": "string"
  },
  "billing_rail": {
   "enum": [
    "direct",
    "zeroclick"
   ],
   "type": "string"
  },
  "channel_close_tx": {
   "anyOf": [
    {
     "type": "string"
    },
    {
     "type": "null"
    }
   ]
  },
  "buyer_refunded_micros": {
   "type": "string"
  },
  "seller_claimed_micros": {
   "type": "string"
  }
 },
 "additionalProperties": false
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agents-withzero-xyz-stop-task-withzero-scheduler-28842398/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agents.withzero.xyz](https://www.zero.xyz/host/agents.withzero.xyz/llms.txt)