Your first API-to-event watch

RerunLab checks a public HTTPS JSON API on a schedule and saves an event when your selected value changes or a condition becomes true. It continues while your laptop and agent are offline. It does not wake an agent automatically.

1. Sign in and choose a project

Open /signup, verify your email using the confirmation button, and open the dashboard. During the private beta, access is limited to admitted pilot accounts. Paid checkout is unavailable until billing verification is complete.

2. Try the synthetic demo

Choose “Try a demo job” from the overview. Keep the supplied source URL, select /status, and use a change trigger. Create the watch and wait for its first successful check: queued becomes the baseline, with no event. Press “Complete demo job,” then “Check now” on the watch. The completed response creates watch.changed. Demo jobs expire after 24 hours and contain synthetic data only. The public homepage animation is a simulation, not a live check.

3. Watch your own API

Create a watch with a public HTTPS JSON GET URL, a JSON Pointer such as /status, and a change or condition trigger. Authentication belongs in a project credential, bound to the source origin. Put correlation information in metadata. Credentials and query values are masked in read responses.

Free checks run no faster than every 600 seconds. One constantly running watch at that interval uses roughly 4,320 checks in 30 days. Previews and manual checks also count when dispatched. There are no automatic overage charges.

4. Read the inbox or receive a webhook

Every event stays in the durable inbox for your plan’s retention period. For push delivery, add a public HTTPS destination, implement its verification challenge, verify it, and assign it to the watch. The inbox works without a destination.

5. Connect an agent

The owner creates a scoped key in Settings and provides it to the agent. An agent can create watches, read events and inspect delivery outcomes. Give only the scopes needed. No autonomous signup, checkout, or model-session wake-up is supported.

Complete watch.json for the controlled demo

Set RERUNLAB_PROJECT_ID to the project ID shown in Settings, and RERUNLAB_DEMO_SOURCE_URL to the opaque demo job URL shown in your watch form. Set RERUNLAB_BASE_URL=https://api.rerunlab.com and provide your human-issued RERUNLAB_API_KEY through your environment.

node --input-type=module -e 'console.log(JSON.stringify({
  project_id:process.env.RERUNLAB_PROJECT_ID,
  name:"Wait for demo export",
  source:{url:process.env.RERUNLAB_DEMO_SOURCE_URL},
  selector:"/status",
  trigger:{type:"condition",operator:"eq",value:"completed",
    fire_on_initial_match:true,stop_after_match:true},
  interval_seconds:600,
  expires_at:new Date(Date.now()+6*3600*1000).toISOString()
}))' > watch.json
curl "$RERUNLAB_BASE_URL/v1/watches" \
  -H "Authorization: Bearer $RERUNLAB_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: demo-export-watch' \
  --data @watch.json

On the demo watch’s detail page, “Attach demo receiver” creates a destination on the isolated demo host, verifies it through the real challenge, and attaches it for future events. Complete the job, then Check now. The receiver verifies the signature and stores only synthetic event/delivery IDs. It rejects generic capture payloads. A separate inbox entry and delivery history confirm the result; it is never simulated in the dashboard.