Pollers re-call endpoints on a timer whether or not anything changed — paying in calls, trial quota and attention for unchanged payloads. Register once here and the fleet's watcher does the polling instead: every 5 minutes it re-fetches the endpoint the way a free-trial caller would, hashes the canonical payload, and POSTs your webhook only when the hash actually changed. Free.
Live state
Loading…
Counts only — subscriber endpoints and webhook URLs are never published.
1. Register with the endpoint slug, your webhook URL and (optionally) the trial-call parameters the watcher should use. You get back an id and a secret — the secret is shown once (only its SHA-256 hash is stored) and is the only way to unsubscribe.
2. The watcher seeds silently. Its first check (within ~5 minutes) records the payload hash and sends nothing. Volatile keys (timestamps, request ids) are stripped before hashing, so a payload that only changed its clock does not ping you.
3. You are pinged on real change. When the canonical payload hash differs from the last check, your webhook receives the payload below. A failed POST is retried on later checks; after 3 consecutive failures the watcher records the new hash anyway — a dead webhook is not spammed forever.
POST https://api.mekongtradeintel.com/clinic/change-alerts
{ "endpoint": "stocks",
"webhook_url": "https://your-host.example/hook",
"params": { "symbol": "AAPL" } } // params optional
-> { ok: true, id: 12, secret: "cas_...", endpoint: "stocks" }
Webhook delivery (POST to your webhook_url):
{ "event": "payload_changed",
"endpoint": "stocks",
"changed_at": "2026-10-29T12:00:00.000Z",
"subscription": 12,
"previous_hash": "<sha256>", "new_hash": "<sha256>" }
DELETE https://api.mekongtradeintel.com/clinic/change-alerts
{ "id": 12, "secret": "cas_..." }
-> { ok: true, removed: true }
Any fleet endpoint slug works — the same catalogue as GET /clinic/codegen. For GET endpoints, params become the query string; for POST endpoints, the JSON body. With no params, the watcher uses the endpoint's documented example input.
Demand digest — the fleet's demand dataset for sellers · Request schema — what an endpoint accepts, before you pay · Cheapest-answer routing — state a need, get the cheapest route · Buyer dashboard — everything the fleet knows about your wallet