Loops

A Loop is a recurring agent run. It’s a first-class object built on the trigger router: a cron-source subscription bound to an agent run. Creating a Loop records the binding and creates the backing cron job that executes it — the box’s Hermes gateway cron on a Tower, or the cloud sidecar cron.

Create a loop

curl -X POST https://api.usenaive.ai/v1/loops \
  -H "Authorization: Bearer nv_sk_live_..." -H "Content-Type: application/json" \
  -d '{
    "name": "Morning inbox triage",
    "schedule": "0 9 * * *",
    "prompt": "Review overnight email + SMS and summarize what needs my attention."
  }'

schedule is a standard cron expression. The response includes the loop subscription and the cron_job_id of the backing executor (null if no runtime is reachable yet — the binding still persists and syncs later).

Manage loops

curl https://api.usenaive.ai/v1/loops -H "Authorization: Bearer nv_sk_live_..."

# pause / resume
curl -X PATCH https://api.usenaive.ai/v1/loops/{id} \
  -H "Authorization: Bearer nv_sk_live_..." -H "Content-Type: application/json" \
  -d '{ "active": false }'

# run once, now
curl -X POST https://api.usenaive.ai/v1/loops/{id}/run \
  -H "Authorization: Bearer nv_sk_live_..."

# delete (also removes the backing cron job)
curl -X DELETE https://api.usenaive.ai/v1/loops/{id} \
  -H "Authorization: Bearer nv_sk_live_..."

Loops vs. cron jobs

The lower-level cron API is a push-through to the runtime’s scheduler. A Loop is the governed, observable wrapper: it owns the binding registry row, surfaces in the trigger delivery-status feed, and pauses/resumes without touching the runtime directly.

Billing

Free — each scheduled run bills as a normal agent run.

Getting Started

Self-hosting (Tower)

Agent Profiles

Architecture

Templates

Migration Guides

Integrations

Primitives

Create a loop

Manage loops

Loops vs. cron jobs

Billing

​Create a loop

​Manage loops

​Loops vs. cron jobs

​Billing

Create a loop

Manage loops

Loops vs. cron jobs

Billing