What Is CueAPI?

What Is CueAPI?

CueAPI is a scheduling API built for AI agents. It lets agents register tasks (called cues) that fire at specific times or on recurring schedules. When a cue fires, CueAPI delivers the payload via webhook or worker pull.

What Problem Does CueAPI Solve?

AI agents need to perform actions on schedules — polling APIs, sending follow-ups, running batch jobs, retrying failed tasks. Without CueAPI, agents rely on cron jobs, setTimeout hacks, or custom scheduling infrastructure that breaks under load.

CueAPI replaces all of that with a single API call.

How Does CueAPI Work?

An agent creates a cue by calling POST /v1/cues with a schedule and a callback URL. CueAPI stores the cue, fires it at the right time, and delivers the payload. The agent receives a webhook with the execution data and reports the outcome.

curl -X POST https://api.cueapi.ai/v1/cues \
  -H "Authorization: Bearer cue_sk_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "daily-report",
    "schedule": {"type": "recurring", "cron": "0 9 * * *"},
    "callback": {"url": "https://your-agent.com/webhook"},
    "payload": {"action": "generate_report"}
  }'

What Are the Key Features?

• Cron and one-time schedules: Recurring cron expressions or single-fire timestamps.
• Webhook delivery: CueAPI POSTs to your callback URL when a cue fires.
• Worker transport: Agents poll for executions instead of receiving webhooks.
• Automatic retries: Failed deliveries retry with exponential backoff (1, 5, 15 minutes).
• Execution tracking: Every firing is logged with status, timestamps, and outcome.
• Per-user webhook secrets: HMAC signature verification for secure delivery.
• Usage tracking: Monthly execution counts with plan-based limits.

Who Uses CueAPI?

CueAPI is designed for:

• AI agent frameworks that need reliable task scheduling
• Multi-agent systems coordinating work across agents
• Backend services replacing fragile cron jobs with a managed API
• Developers building automation workflows with scheduled triggers

How Is CueAPI Different from Cron?

Cron runs on a single server. If the server goes down, cron stops. CueAPI is a managed service with:

• No infrastructure to maintain — create cues via API, CueAPI handles the rest
• Built-in retries — failed webhooks retry automatically
• Execution history — see every firing, its status, and outcome
• Multi-tenant — each API key gets isolated cues, usage, and billing
• Worker transport — agents can pull work instead of exposing webhook endpoints

What Does a CueAPI Response Look Like?

When a cue fires, CueAPI sends a POST request to your callback URL:

{
  "execution_id": "exec_abc123",
  "cue_id": "cue_xyz789",
  "cue_name": "daily-report",
  "payload": {"action": "generate_report"},
  "scheduled_for": "2026-03-15T09:00:00Z",
  "attempt": 1
}

How Do I Get Started?

1. Sign up at cueapi.ai
2. Get your API key from the dashboard
3. Create your first cue with POST /v1/cues
4. Receive webhooks when your cue fires

Read the full documentation at docs.cueapi.ai.