# AgentCron — Persistent Cron Scheduler for AI Agents

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

Registers a persistent scheduled task that calls a target URL at a specified interval for a set duration, surviving agent session termination

## Facts

- Endpoint: GET https://cron.memoryapi.org/x402/cron/register
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentcron-persistent-cron-scheduler-for-ai-agents-d18537c0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yU6rn5R3DDDxXBNFfydJB

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-persistent-cron-scheduler-for-ai-agents-d18537c0
```

Example prompt: Set up a persistent cron job that calls https://my-service.example.com/hourly-check every 60 minutes for 7 days, starting now — I need it to keep running even after this session ends.

## When to prefer this

Use this endpoint when an AI agent needs to schedule recurring tasks that must persist beyond the current session, especially when the agent may go offline between executions. Ideal for polling, periodic callbacks, or time-based automation that requires guaranteed execution without the agent being active. Prefer over in-process timers or local cron when reliability across sessions and agent restarts is required.

## Known failure modes

- Payment failure — insufficient USDC balance or x402 payment not accepted, returns 402
- Invalid callback URL — malformed or unreachable target URL rejected
- Invalid interval or duration parameters — out-of-range values rejected
- Duplicate registration — same URL/interval combination may be rejected or create a new schedule
- Service unavailable — cron.memoryapi.org unreachable returns 5xx

## How this service works

Register a persistent cron schedule that survives session termination. Agent specifies URL, HTTP method, interval, and duration. Runs even when the agent is offline.

## Output

Returns a JSON object confirming the schedule was registered, including a unique schedule_id (UUID), the first_run_at timestamp, expires_at date, interval_minutes, duration_days, and executions_expected count (e.g. 168 for 60-minute interval over 7 days).

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "example": {
  "message": "Schedule registered. Will call your URL every 60 minutes for 7 days.",
  "success": true,
  "expires_at": "2026-01-08T00:00:00Z",
  "schedule_id": "uuid",
  "first_run_at": "2026-01-01T01:00:00Z",
  "duration_days": 7,
  "interval_minutes": 60,
  "executions_expected": 168
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentcron-persistent-cron-scheduler-for-ai-agents-d18537c0/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)