# AgentCron Cancel Schedule

> AgentCron Cancel Schedule is a paid API for AI agents from cron.memoryapi.org, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Cancels a previously registered persistent cron schedule by its schedule ID, stopping future executions.

## Facts

- Endpoint: POST https://cron.memoryapi.org/x402/cron/cancel
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentcron-cancel-schedule-0f93f553
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_UTe2D0iNSc7E04rUK9rTu

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 agentcron-cancel-schedule-0f93f553 -d '<json body>'
```

Example prompt: Cancel the AgentCron schedule with ID '3f2a1b4c-8e7d-4f5a-9c6b-1d2e3f4a5b6c' — I don't want that recurring task running anymore.

## When to prefer this

Use this endpoint when you need to permanently stop a previously registered AgentCron persistent schedule. Prefer this over alternatives when the schedule was created via AgentCron's x402-powered registration and you have the schedule_id. This is the correct endpoint for removing a recurring task that runs even when your agent is offline.

## Known failure modes

- Invalid or non-existent schedule_id returns an error
- Payment failure via x402 protocol prevents cancellation
- Schedule already cancelled or expired returns an error
- Unauthorized attempt to cancel another agent's schedule
- Malformed request body missing schedule_id field

## How this service works

x402-powered persistent cron scheduler. AI agents register scheduled tasks that survive session termination. Runs even when the agent is offline. Pay per registration in USDC on Base mainnet.

## Output

Returns a JSON object with a success boolean (true), a confirmation message ('Schedule cancelled successfully.'), and the schedule_id of the cancelled schedule.

## Request schema (JSON Schema)

```json
{
 "properties": {
  "input": {
   "required": [
    "method"
   ],
   "properties": {
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "example": {
  "message": "Schedule cancelled successfully.",
  "success": true,
  "schedule_id": "uuid"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentcron-cancel-schedule-0f93f553/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from cron.memoryapi.org](https://www.zero.xyz/host/cron.memoryapi.org/llms.txt)