schedule_wakeSchedule a wake-up for your agent. At the time you pick, Agent Wake POSTs your saved state (notes, thread ID, next step) to your callback URL, or holds it for check_wakes.
MCP · live · free 50/day
Your agent forgets between runs. Wake it up with its notes.
Your AI agent picks up where it left off. Schedule a wake-up with its notes and next step; we POST it back on time or hold it for the next session. Free 50 calls a day, then $9 a month.
Works with ClaudeCodexChatGPTGrok Bot· bring your own model
Preview: wake at 2026-10-15 14:33 UTC, held for check_wakes. Show this to the user; call again with confirm=true to save.
fires at (UTC)2026-10-15T14:33:11Z
deliveryheld for check_wakes
repeatonce
statuspreview, nothing saved
checked2026-10-15 12:33 UTC (prerendered; Run for live)
Tools your agent gets
Each result includes understood, job, and a one-line outcome, so your agent can confirm and report back in plain words.
check_wakesCollect wake-ups that are due for your inbox (each returned once, with its saved state and thread ID) and list upcoming ones. Call this at the start of a session.
cancel_wakeCancel a pending wake-up by wake_id. Call once without confirm to preview, then with confirm=true.
usage_and_upgradeUsage today + upgrade link (not metered).
Free first. Pro when it matters.
The free tier resets every day. It is not a trial. Upgrade when your agents need volume.
01
Just call it
No signup. 50 calls a day per IP over MCP or REST.
$0
02
Free API key
A stable identity for your agent with the same 50/day. One click, no email.
03
Pro
5,000 calls a day. After you pay, you get your key immediately. Cancel anytime.
$9/month
FAQ
What problem does this solve?
Scheduled agent runs start as fresh sessions, so they forget what the last run was doing. Agent Wake stores a small state blob (goal, progress, next step, IDs) and gives it back at the time you pick, so the next run continues instead of starting over.
How does the wake-up reach my agent?
Two ways. With a callback_url, we POST the state as JSON to your public https endpoint within about a minute of the scheduled time, signed with an HMAC header you can verify. Without one, the wake waits in your inbox and your agent collects it with check_wakes at the start of its next session.
Does it change anything without asking?
No. schedule_wake and cancel_wake first return a preview of exactly what will be saved or canceled. Nothing is written until your agent calls again with confirm=true, so it can show the user and get a yes first.
What does it cost?
Free: 50 calls a day, 10 active wakes, repeats every 60+ minutes, 8 KB of state. Pro is $9 a month: 5,000 calls a day, 1,000 active wakes, repeats every 5+ minutes, 64 KB of state. You get your Pro key on screen right after paying.
Is there a model inside?
No. Bring your own model. Agent Wake only stores and delivers what your agent saves, and works with Claude, Codex, ChatGPT and Grok Bot over MCP or REST.
What can I store?
Any JSON object: the task, what is done, what is next, links and IDs. Don't store passwords or API keys. Delivered wake-ups are deleted 7 days after your agent collects them.
Connect in one line
Remote MCP over streamable HTTP. Claude Code:
claude mcp add --transport http agent-wake https://wake.botrecipe.com/mcp
MCP URL https://wake.botrecipe.com/mcp
REST POST https://wake.botrecipe.com/api/run/<tool>
Auth optional Authorization: Bearer <key>
Codex, ChatGPT, Grok Bot: add a remote MCP server with the URL above. Skill file: SKILL.md · catalog entry: tool.json