Scheduling infrastructure for agents.
One schedule for all your agents: Set it. Watch it run. Get proof it worked.
Get API key free → | View docs
# Your agent. On time. Every time. curl -X POST https://api.cueapi.ai/v1/cues \ -H "Authorization: Bearer cue_sk_..." \ -H "Content-Type: application/json" \ -d '{"name":"morning-briefing", "schedule":{"type":"recurring","cron":"0 9 * * *"}, "callback":{"url":"https://your.agent/run"}}' # HTTP 200 { "id": "cue_a3f9b2...", "status": "active" }
POST to /v1/cues. Give it a name, a schedule (cron or ISO timestamp), and the URL to call. Add any payload you want returned. Done.
{ "name": "morning-briefing", "schedule": "0 9 * * *", "callback_url": "https://your.agent/run", "timezone": "America/New_York", "payload": { "task": "check_pipeline" } }
At the scheduled moment, CueAPI calls your webhook with a signed payload. 3 retries with exponential backoff. HMAC-SHA256 verified. At-least-once delivery guaranteed.
{ "execution_id": "exec_8f2a1b", "cue_id": "cue_a3f9b2", "name": "morning-briefing", "scheduled_for": "2026-03-12T09:00:00Z", "attempt": 1, "payload": { "task": "check_pipeline" } }
Run your logic. Report the outcome back. CueAPI logs success, failure, retrying. So you always know if your agents are actually doing the work.
POST /v1/executions/{id}/outcome { "status": "success", "message": "Briefing sent to 3 users", "duration_ms": 1240 }
Your agent said it would handle it. Did it? CueAPI shows every execution with timestamp, cue name, status, attempt number, and duration.
847 jobs. 23 missed in 12 months. That data is real.
Full execution history per cue. Delivery failure vs handler failure, logged separately.
Cron was built for servers in the 1970s. No retries. No history. No visibility. CueAPI is built for agents in 2026.
Every webhook delivery is signed. SSRF protection on all callback URLs.
Exponential backoff. Stale execution recovery. You see exactly what happened.
Claude, ChatGPT, CrewAI, LangChain, custom code. Same five endpoints. One API key.
"The real gap in the market is visibility. Developers don't know their crons are broken until something goes wrong in production." — Socrates, AI Agent, OpenClaw System. First production user, CueAPI closed beta.
"The real gap in the market is visibility. Developers don't know their crons are broken until something goes wrong in production."
— Socrates, AI Agent, OpenClaw System. First production user, CueAPI closed beta.
If you've read the docs, you've learned everything.
# Create a cue curl -X POST https://api.cueapi.ai/v1/cues \ -H "Authorization: Bearer cue_sk_xxx" \ -H "Content-Type: application/json" \ -d '{ "name": "morning-analytics", "schedule": {"type": "recurring", "cron": "0 9 * * *", "timezone": "America/Los_Angeles"}, "callback": {"url": "https://my-agent.com/webhook"}, "payload": {"task": "pull-dashboard", "context_mode": "live"} }' # Response { "id": "cue_a1b2c3d4e5f6", "name": "morning-analytics", "status": "active", "next_run": "2026-03-13T09:00:00-07:00" }
import httpx client = httpx.Client( base_url="https://api.cueapi.ai/v1", headers={"Authorization": "Bearer cue_sk_xxx"} ) cue = client.post("/cues", json={ "name": "morning-analytics", "schedule": {"type": "recurring", "cron": "0 9 * * *"}, "callback": {"url": "https://my-agent.com/webhook"}, "payload": {"task": "pull-dashboard"} }).json() print(cue["next_run"]) # 2026-03-13T09:00:00Z
const res = await fetch("https://api.cueapi.ai/v1/cues", { method: "POST", headers: { "Authorization": "Bearer cue_sk_xxx", "Content-Type": "application/json" }, body: JSON.stringify({ name: "morning-analytics", schedule: { type: "recurring", cron: "0 9 * * *" }, callback: { url: "https://my-agent.com/webhook" }, payload: { task: "pull-dashboard" } }) }); const cue = await res.json(); console.log(cue.next_run); // 2026-03-13T09:00:00Z
$ cueapi create \ --name "morning-analytics" \ --cron "0 9 * * *" \ --url https://my-agent.com/webhook \ --payload '{"task": "pull-dashboard"}' # ✓ Created cue_a1b2c3d4e5f6 # Next run: 2026-03-13 09:00:00 PDT
Same features across all tiers. More volume as you grow.
Save 20% with annual billing. Pro annual: $95.88/year. Scale annual: $470.40/year.
Install → login → first cue in under 30 seconds. Zero friction.
$ pip install cueapi Successfully installed cueapi-0.1.0 $ cueapi login Opening browser to authenticate... ✓ Authenticated as you@email.com $ cueapi quickstart Creating test cue... ✓ Waiting for delivery... ✓ Delivered in 3.8s Your agents now have a clock.
Available CLI commands: cueapi login, cueapi quickstart, cueapi create, cueapi list, cueapi get, cueapi pause, cueapi resume, cueapi delete, cueapi usage, cueapi upgrade.
cueapi login
cueapi quickstart
cueapi create
cueapi list
cueapi get
cueapi pause
cueapi resume
cueapi delete
cueapi usage
cueapi upgrade
CueAPI is tracking NIST AI Agent Standards Initiative and AIUC-1 certification for future compliance. Full security details at cueapi.ai/security.
No. Sign up with just an email. 10 active cues, 300 executions per month, 60 API requests per minute. Free forever.
Per delivery attempt, not per cue fire. If a webhook fails and CueAPI retries 3 times, that counts as 3 executions. This is documented in your usage dashboard.
CueAPI gives you a 24-hour grace period. Cues keep firing during grace. After 24 hours, new executions are blocked until the next billing cycle or you upgrade.
Yes. Upgrades take effect immediately with full access to new limits. Downgrades take effect at the end of your billing period. Excess cues are paused, not deleted.
Yes. Pro annual is $95.88/year (save ~20%). Scale annual is $470.40/year (save ~20%).
Yes. Free, Pro, and Scale only differ in volume: active cues, monthly executions, and request rate. Every feature is available on every plan.
Yes. Install cueapi-worker on your local machine. It pulls scheduled work from CueAPI and runs your scripts locally. No public URL, no webhook server, no tunnel.
CueAPI retries automatically. 3 attempts with exponential backoff (1, 5, 15 minutes by default, configurable up to 10 retries). If all fail, you receive an email notification.
API keys are SHA-256 hashed. Webhooks are signed with HMAC-SHA256 using your per-user secret. All traffic is HTTPS. Callback URLs are validated against SSRF. Full details at cueapi.ai/security.
CueAPI checks for due cues every 5 seconds. Typical delivery latency is 2–3 seconds after the scheduled time. Not suitable for sub-second precision.
Yes. Cancel through the Stripe billing portal. You keep access until the end of your billing period. No refunds for partial periods.
Not yet. If Scale limits are not enough, contact support@vector.build. Custom plans are on the roadmap.
All major credit and debit cards via Stripe.
CueAPI targets high availability but does not offer a formal SLA yet. Current status is always visible at status.cueapi.ai. Failures delay delivery but never lose schedules.
Let the agent be the brain. Let CueAPI be the clock.
Get API key free → | Read the docs
Agent API Reference · About · Pricing · Blog · Security · Privacy · Terms · Docs · Dashboard · X / Twitter · Status
© Vector Apps Inc 2026