# Agent Wake

> 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.

## Connect
- MCP (streamable HTTP): https://wake.botrecipe.com/mcp
- Claude Code: `claude mcp add --transport http agent-wake https://wake.botrecipe.com/mcp`
- REST: `POST https://wake.botrecipe.com/api/run/<tool>` with JSON args. OpenAPI: https://wake.botrecipe.com/openapi.json
- Auth: optional `Authorization: Bearer <key>`. Free key: `POST https://wake.botrecipe.com/api/key`

## Pricing
- Free: 50 calls/day (daily, not a trial). No signup.
- Pro: $9/month, 5000 calls/day: https://pay.instaloops.com/b/aFa28rgOc8QTgdx4Kr83C3v
- Bring your own model. Works with Claude, Codex, ChatGPT, Grok Bot.

## Tools
### schedule_wake
Schedule 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. Use it so a later, fresh session picks up where this one stopped. Call once without confirm to preview what will be saved, show the user, then call again with confirm=true.
Inputs: `when` (string, required), `repeat_minutes` (integer), `state` (object), `thread_id` (string), `callback_url` (string), `inbox` (string), `confirm` (boolean)

### check_wakes
Collect 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.
Inputs: `inbox` (string)

### cancel_wake
Cancel a pending wake-up by wake_id. Call once without confirm to preview, then with confirm=true.
Inputs: `wake_id` (string, required), `inbox` (string), `confirm` (boolean)

### usage_and_upgrade
Usage today + upgrade link (not metered).

## Example result
`schedule_wake({"when":"in 2 hours"})` → 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.

## 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.

Publisher: Supa Humans (https://supahumans.ai). Marketplace: https://botrecipe.com/tools/

## Machine files
- https://wake.botrecipe.com/
- https://wake.botrecipe.com/index.md
- https://wake.botrecipe.com/llms.txt
- https://wake.botrecipe.com/llms-full.txt
- https://wake.botrecipe.com/SKILL.md
- https://wake.botrecipe.com/openapi.json
- https://wake.botrecipe.com/tool.json
- https://wake.botrecipe.com/.well-known/mcp.json