An alarm clock for agents

An agent has no clock. It cannot sleep without burning its runtime, and it cannot cron without owning infrastructure. One cent buys a wake at a named moment — delivered to your URL with a signed receipt, or pollable for free.

Wake — $0.01

POST /v1/wake?in=3600&url=https://your-agent.example/resume
  → { "wake_id": "8b35f314…", "status": "scheduled", "mode": "callback",
      "scheduled_at": "…", "handshake": "verified",
      "status_url": "https://soren.com/v1/wake/8b35f314…",
      "settlement": "0x…" }

at the appointed time, POSTed to your URL (retries: 30s, 2m, 10m, 30m):
  { "event": "wake", "wake_id": "…", "scheduled_at": "…", "fired_at": "…",
    "statement": "wake|<id>|<scheduled_at>|<fired_at>",
    "signature": { "algorithm": "Ed25519",
                   "public_key_url": "https://soren.com/oracle-key.json", "…": "…" } }

in is seconds from now: 30 seconds to 30 days. Omit url entirely and the wake is a pure timer instead: poll GET /v1/wake/:id for free and the status flips to fired at the moment, carrying the same signed receipt. No public endpoint required.

The consent handshake

A paid service that will POST to any URL you name is a denial-of-service tool with a receipt, so callbacks are opt-in by construction. At registration your URL receives {"event":"wake_verification","challenge":"<random>"} and must answer 200 with the challenge echoed anywhere in the body. No echo, no wake, no charge. Callbacks are https-only, private address space is refused outright, and a single host is capped at 50 registrations a day — even a consenting host cannot be flooded through us.

The receipt is provable

The statement binds wake_id, the scheduled time, and the actual fire time, signed with the same published Ed25519 key as our oracles and attestations. It is signed once, at first fire; every retry resends the identical copy. When a deadline mattered, you can show a counterparty exactly when you were woken and how late the fire was.

What this composes with

What this deliberately does not do

• No payloads. A wake knows its URL and its time, nothing else. It is a time signal, not a message queue — there is nothing to leak.
• No cancellation or rescheduling. A wake is one cent and immutable; register a new one and ignore the old. An authentication surface for cancellation would cost more than it saves.
• No delivery guarantee beyond the retries. Four retries over 43 minutes, then failed, recorded honestly. The signed receipt stays pollable for 7 days either way, then the wake is deleted entirely.