// Cloud. Laptop. Mac Mini. NAT. Same primitive.
Coordination infrastructure for agent systems.
Connect any step, task, job, or agent across any environment. Every handoff verified.
# 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" }
THE PRIMITIVES
Five primitives. One journey.
Every scheduled run passes through these five stages. Each primitive is one station on the rail.
Cue
Schedule lives in CueAPI. Survives every restart and deploy.
cron 0 9 * * *Execution
One row per firing. Status, attempts, outcome all attach here.
exec_a3f9b2c8Worker
Agent pulls its work. Reaches behind NAT, firewalls, laptops.
laptop, behind NATOutcome
Handler POSTs back what happened. Closes the execution record.
successEvidence
Structured fields on the outcome. Verified against the cue rule.
github.com/org/repo/pull/42One run. Five stations. No silence between.
HOW IT WORKS
Agents coordinate through cues.
One agent finishes. Its outcome fires the next cue. The next worker catches. No scheduler between them, no glue code, no polling.
IN THE WILD
The shapes cues take.
Content machines. Build pipelines. Creative stacks. Agent factories. Cross-agent meshes. Same primitive underneath, six different chains on top.
A nervous system for agents.
Every agent talks through a cue bus. No middleware, no polling. Outcomes flow, the mesh forms itself.
Commit to prod, with proof.
Push fires tests. Build fires deploy. Every stage leaves evidence, not just a green check.
Research. Draft. Edit. Ship.
One agent researches. Another drafts. An editor polishes. A publisher fans out. Every revision recorded.
Image, audio, video. One take.
Brief fires every creative agent in parallel. Image, voice, edit work their tracks. Output assembles itself.
Spec in. Ship out.
Claude codes from the spec. A QA agent tests. Passing code ships and reports back.
Agents that build agents.
One agent writes the next. A tester runs it against a suite. A deployer puts it live. Your factory floor, on cue.
CODE & CLI
Five minutes from install to first cue.
Any language on the left. Any shell on the right. Pick your surface.
# Create a cuecurl -X POST https://api.cueapi.ai/v1/cues \-H "Authorization: Bearer cue_sk_..." \-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"}}'# 201 Created{"id": "cue_x7k9m2p4q8w1", "status": "active"}
PATTERNS
What teams build on Cue.
OPEN SOURCE
The whole primitive. Apache 2.0.
Cue is open infrastructure. docker compose up boots the full stack: API, poller, worker, Postgres, Redis. Same verification. Same workers. Same REST surface. Self-host your coordination, or use the hosted service.
SECURITY & PRIVACY
Built for trust, not theater.
Defense in depth. Five layers, core outward, every claim verifiable.
Full details at cueapi.ai/security and cueapi.ai/privacy.
Start coordinating.
pip install cueapi. First cue in 60 seconds. Free forever to start.