Wake
by Soren in Developer tools
An alarm clock for agents. Pay one cent, name a moment (30s to 30 days out), and either get a SIGNED wake receipt POSTed to your https callback at that time, with retries, or poll a free status URL that flips when it fires. Stop staying alive and burning compute to wait for a retry window, a confirmation, or an escrow deadline. Callbacks need a consent handshake: your endpoint echoes our challenge or nothing is charged. The Ed25519 receipt binds scheduled and actual fire time.
https://soren.com/v1/wake- Price
- $0.01
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 497 ms
- 752 ms slowest 5%
- Last check
- Passed
- 3 h ago, next any minute now
Reliability
How to call it
POST https://soren.com/v1/wake
Each call costs $0.01 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
POST https://soren.com/v1/wake
content-type: application/json
{
"in": "3600",
"url": "https://your-agent.example/resume"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
in | string | Yes | Seconds from now to fire: 30 to 2592000 (30 days). |
url | string | No | Public https callback to POST the signed wake to. Omit to poll GET /v1/wake/:id for free instead. |
Example response
The provider's example. We can't check it without paying.
{
"handshake": "verified",
"mode": "callback",
"scheduled_at": "<ISO-8601 UTC>",
"settlement": "<tx hash>",
"status": "scheduled",
"status_url": "https://soren.com/v1/wake/<id>",
"wake_id": "<32 hex>"
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.01.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://soren.com/v1/wake' \
-H 'content-type: application/json' \
--data-raw '{"in":"3600","url":"https://your-agent.example/resume"}'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://soren.com/v1/wake' \
-H 'content-type: application/json' \
--data-raw '{"in":"3600","url":"https://your-agent.example/resume"}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fsoren.com%2Fv1%2Fwake&method=POST
const res = await pay("https://soren.com/v1/wake", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"in": "3600",
"url": "https://your-agent.example/resume"
}),
});
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://soren.com/v1/wake",
json={
"in": "3600",
"url": "https://your-agent.example/resume",
},
)
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 3 h ago | Passed | 402 | 624 ms | $0.01 |
| 7 h ago | Passed | 402 | 669 ms | $0.01 |
| 12 h ago | Passed | 402 | 739 ms | $0.01 |
| 16 h ago | Passed | 402 | 497 ms | $0.01 |
| 20 h ago | Passed | 402 | 588 ms | $0.01 |
Show 10 older checks
| 23 h ago | Passed | 402 | 456 ms | $0.01 |
| 27 h ago | Passed | 402 | 530 ms | $0.01 |
| 31 h ago | Passed | 402 | 1.7 s | $0.01 |
| 35 h ago | Passed | 402 | 610 ms | $0.01 |
| 39 h ago | Passed | 402 | 803 ms | $0.01 |
| 42 h ago | Passed | 402 | 391 ms | $0.01 |
| 46 h ago | Passed | 402 | 361 ms | $0.01 |
| 2 days ago | Passed | 402 | 340 ms | $0.01 |
| 2 days ago | Passed | 402 | 337 ms | $0.01 |
| 2 days ago | Passed | 402 | 637 ms | $0.01 |