# x402.shizu.me Durable Cron Timer

> x402.shizu.me Durable Cron Timer is a paid API for AI agents from x402.shizu.me, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-15).

Returns the number of intervals elapsed since last poll for a registered schedule, enabling stateless agents to track time passage without background processes.

## Facts

- Endpoint: GET https://x402.shizu.me/cron
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-shizu-me-durable-cron-timer-e0dd836b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hMfYGOF5k9s09a_hQnakC

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 x402-shizu-me-durable-cron-timer-e0dd836b
```

Example prompt: Check how many 60-second intervals have elapsed on my cron schedule since I last polled — my schedule ID is abc123.

## When to prefer this

Use this endpoint when you need a stateless, poll-based timer for an AI agent that cannot schedule its own future wake-up calls. Ideal for agents running in serverless or ephemeral environments where background workers are unavailable and you need to know how many intervals have elapsed since the last check.

## Known failure modes

- Unknown or expired schedule ID returns an error or zero ticks
- Missing id parameter causes a bad request response
- Payment failure results in 402 response requiring USDC payment
- Stale or invalid schedule registration causes incorrect tick counts
- Network timeout before response is returned

## How this service works

A durable timer for stateless agents. POST {interval_seconds, count} registers a schedule; GET ?id= returns the ticks that have accrued since your last poll (computed on read — no work runs in the background). An agent can't schedule its own future wake; poll this to know how many intervals have elapsed.

## Output

Returns the number of intervals (ticks) that have accrued since the last poll for the given schedule ID, computed on-demand at read time with no background processing required.

## Request schema (JSON Schema)

```json
{
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "properties": {
  "input": {
   "type": "object",
   "properties": {
    "method": {
     "const": "GET"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "id": {
       "type": "string"
      }
     },
     "required": [
      "id"
     ]
    }
   },
   "required": [
    "method"
   ]
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "id": "Xy7…",
  "poll": "GET /cron?id=Xy7…",
  "count": 12,
  "interval": 300,
  "first_tick_in": 300
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-shizu-me-durable-cron-timer-e0dd836b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.shizu.me](https://www.zero.xyz/host/x402.shizu.me/llms.txt)