# AgentCron — Cron Schedule Status Check

> AgentCron — Cron Schedule Status Check is a paid API for AI agents from cron.memoryapi.org, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Returns the current status of a registered persistent cron schedule, including next run time, execution count, and expiry information.

## Facts

- Endpoint: GET https://cron.memoryapi.org/x402/cron/status
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentcron-cron-schedule-status-check-ddc60002
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uY8UaO6HVVlZ_Ya2wJSRn

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-cron-schedule-status-check-ddc60002
```

Example prompt: Can you check the status of my AgentCron scheduled task — specifically when it's next set to run, how many times it's already executed, and how many days are left before it expires?

## When to prefer this

Use this endpoint when an AI agent needs to verify the health and timing of a previously registered persistent cron schedule without modifying it. Ideal for monitoring whether a scheduled task is still active after session termination, or confirming the next execution time before taking dependent actions.

## Known failure modes

- Schedule ID not found or invalid — returns error with no schedule data
- Payment of $0.001 USDC on Base mainnet not provided or failed — returns 402 Payment Required
- Schedule has expired — may return active: false with zero expires_in_days
- Network or service unavailability — returns 5xx error

## 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 indicating whether the schedule is active, the ISO timestamp of the next scheduled run, the unique schedule UUID, the total number of executions completed so far, and the number of days remaining until the schedule expires.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "example": {
  "success": true,
  "schedules": {
   "active": true,
   "next_run_at": "2026-01-01T02:00:00Z",
   "schedule_id": "uuid",
   "execution_count": 42,
   "expires_in_days": 5
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentcron-cron-schedule-status-check-ddc60002/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)