# WAKE402 Scheduled HTTPS Callback

> WAKE402 Scheduled HTTPS Callback is a paid API for AI agents from wake402.agentwake.workers.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-13).

Schedules a single future HTTPS callback to a given URL after a delay of 60–86400 seconds, paid once per wake via USDC over x402

## Facts

- Endpoint: POST https://wake402.agentwake.workers.dev/v1/wake-after
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/wake402-scheduled-https-callback-7e42f12e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DG-S1yEG_oNxI5ReyBRzZ

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability wake402-scheduled-https-callback-7e42f12e -d '<json body>'
```

Example prompt: Set an alarm to hit my callback URL https://myserver.example.com/wake in exactly 300 seconds — pay for it and make sure identical retries don't reschedule it.

## When to prefer this

Choose WAKE402 when you need a lightweight, pay-per-use, durable scheduled HTTPS callback with no recurring subscription and idempotent retry safety. Prefer it over cron services when you need a one-shot delay anchored to a verified payment time, and when your callback target is a public HTTPS endpoint. It is well-suited for agentic workflows that need to resume after a delay without maintaining their own timer infrastructure.

## Known failure modes

- Callback URL fails SSRF validation (non-HTTPS, non-standard port, or private IP range) — request rejected before payment
- delay_seconds out of range (below 60 or above 86400) — validation error
- Payment not received or verification fails — callback not scheduled
- Target callback URL is unreachable at fire time — at-least-once semantics mean a retry may occur, but delivery is not guaranteed indefinitely
- Duplicate retries after scheduling do not move the scheduled time — expected behavior, not a failure

## How this service works

Schedule one HTTPS callback after an integer delay of 60 through 86400 seconds. The delay is anchored once to the first durable payment verification time, so identical retries cannot move the scheduled time. One payment purchases one at-least-once wake.

## Output

A confirmation that the callback has been scheduled, anchored to the first durable payment verification time. After the delay elapses, WAKE402 fires at least one HTTPS POST to the specified callback URL. Idempotent retries of the same request preserve the original scheduled time rather than rescheduling.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "callback": {
   "type": "string",
   "pattern": "^https://",
   "maxLength": 2048,
   "description": "Public HTTPS callback URL on standard port 443; WAKE402 applies its full SSRF validation before payment verification."
  },
  "delay_seconds": {
   "type": "integer",
   "maximum": 86400,
   "minimum": 60,
   "description": "Delay after the first durable payment verification, from 60 through 86400 seconds. Identical retries preserve the original derived time."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/wake402-scheduled-https-callback-7e42f12e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from wake402.agentwake.workers.dev](https://www.zero.xyz/host/wake402.agentwake.workers.dev/llms.txt)