> ## Documentation Index
> Fetch the complete documentation index at: https://usenaive.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# List Cron Jobs

> GET /v1/cron — List all scheduled cron jobs.

<Warning>
  **Deprecated — `naive cron` and `/v1/cron`.** It drives the legacy orchestration runtime, which is FROZEN — it accepts no new capabilities. The durable runtime enforces policy at the tool boundary, not only at the gateway, and it is the only runtime new work is built on.

  **Use instead:** `naive teams schedule / naive teams unschedule — 5 of the 8 subcommands map`

  These routes keep answering. Nothing is removed and no response shape changes: the
  deprecation is announced in headers only, which are purely additive. Every response
  from this router carries `Deprecation` ([RFC 9745](https://www.rfc-editor.org/rfc/rfc9745.html) —
  the value is a Structured Field Date, `@` plus epoch seconds, not the boolean `true`
  some pre-RFC clients look for),
  `Link rel="deprecation"`, `Warning: 299` and `X-Naive-Deprecation-Id: dep.primitive.cron`.
  There is **no `Sunset` header**, because this is frozen with no sunset date — a
  `Sunset` on a frozen row would be a date the platform has not promised.

  Announced 2026-07-29. Level `frozen`. The freeze ends when
  `company_containers with provider='hermes' and status='running' reaches zero` — not on a date.

  **Not deprecated, same prefix.** `POST /v1/cron/reconcile-*`, `POST /v1/cron/drain-events` and `POST /v1/cron/process-conversions` are shared-secret platform reconcilers registered before this router. They are not part of `naive cron`, carry none of these headers, and are not going away.

  Replacement surface: [the durable runtime API](/docs/api-reference/runtime/overview).
</Warning>

<RequestExample>
  ```bash theme={"theme":"css-variables"}
  curl https://api.usenaive.ai/v1/cron \
    -H "Authorization: Bearer nv_sk_live_..."
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={"theme":"css-variables"}
  {
    "cron_jobs": [
      {
        "id": "cron-abc-123",
        "name": "Morning Email Check",
        "schedule": "0 9 * * *",
        "prompt": "Check email and respond to urgent messages",
        "status": "active",
        "last_run": "2026-01-15T09:00:00Z",
        "next_run": "2026-01-16T09:00:00Z"
      }
    ],
    "count": 1
  }
  ```
</ResponseExample>

## Query Parameters

| Param   | Type    | Default | Description     |
| ------- | ------- | ------- | --------------- |
| `limit` | integer | 50      | Maximum results |