EDGECASE WAIT / EVENT INFRASTRUCTURE

Stop making agents poll.

Give an agent a temporary receiver for one future event. Pay one cent, hand the event URL to the producer, and let Wait call you when something happens.

View API →See how it works ↓Pay-per-use · no account · no subscription · Base-mainnet USDC through x402
LIVE SERVICE wait.edgecasesystems.workers.devCheck service status ↗
THE PROBLEM

“Is it done yet?” is a costly loop.

Agents wait for approvals, long-running jobs, external workflows, and services whose timing is unknown. Repeated checks consume requests, compute, context, tokens, and attention.

Wait turns that loop into one future JSON event, one temporary receiver, and one callback destination.

HOW WAIT WORKS

A temporary endpoint for a future event.

01

Create a wait

Send a callback URL and a timeout from 60 seconds through 24 hours.

02

Pay and receive

Pay $0.01 and receive private capabilities.

03

Hand off the event

Give the event URL to the process that will produce the JSON.

04

Resume on delivery

The first accepted event wins. Wait uses event-driven callback delivery.

A SMALL CONTRACT

Readable by people. Consumable by agents.

The live API negotiates payment with unsigned HTTP 402 and publishes its contract in OpenAPI.

Step 1: unsigned request
POST /v1/waits
Content-Type: application/json

{"callback_url":"https://example.com/wait","timeout_seconds":3600}

→ HTTP 402
→ PAYMENT-REQUIRED

Step 2: repeat the same logical request
with a fresh UUIDv4 Idempotency-Key and:
PAYMENT-SIGNATURE: <proof>
DELIVERY SEMANTICS

First event wins. A different event conflicts.

202 means accepted. It does not mean callback delivery has completed.

Delivery is bounded at-least-once; deduplicate by wait_id.

Keep capabilities private. URLs and tokens are bearer credentials.

Recover deliberately. Retain original request information for exact replay.

PRICING$0.01per wait · one future event · up to 24 hours

No account. No subscription.