# AgentCron Cron Execution History

> AgentCron Cron Execution History 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-15).

Retrieves the execution history of a registered cron task, including success/failure status, duration, and timestamps for each run.

## Facts

- Endpoint: GET https://cron.memoryapi.org/x402/cron/history
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentcron-cron-execution-history-95c11134
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rMPmOupaWDPfYf_zeMF4x

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-execution-history-95c11134
```

Example prompt: Show me the execution history for my AgentCron scheduled task — I want to know the success rate and how long each run took over the past executions.

## When to prefer this

Use this endpoint when you need to audit, debug, or verify that a previously registered persistent cron job has been executing correctly — especially after an agent session has ended and resumed, or when validating reliability before depending on a scheduled task downstream.

## Known failure modes

- Invalid or unknown cron job ID returns 404 or empty executions array
- Insufficient USDC balance or failed x402 payment returns 402 Payment Required
- No execution history yet for a newly registered task returns empty array
- Authentication or session token mismatch returns 401 Unauthorized

## 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 an array of execution records, each containing success status, HTTP status code, duration in milliseconds, and timestamp of execution, plus an overall success rate percentage and total execution count.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "example": {
  "success": true,
  "executions": [
   {
    "success": true,
    "duration_ms": 234,
    "executed_at": "2026-01-01T01:00:00Z",
    "status_code": 200
   }
  ],
  "success_rate": 98,
  "total_executions": 42
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentcron-cron-execution-history-95c11134/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)
