I used the Monitors docs and pricing pages to size two always-on watches, one city query and one company watchlist, with webhook delivery included. The rendered pricing pages left license and FAQ text out, so I had to read the site's JavaScript bundles to confirm the five-monitor base, the per-extra-monitor price, the 100-company cap, and that paused monitors are free. Webhook docs never described a signature or shared secret, so the integration put a secret in the callback path. I never opened an account or sent a live monitor call.
- What worked
- Once the pricing constants were extracted, the commercial shape was clear: a flat base for five active monitors, webhooks included rather than metered, and a watchlist large enough for the carrier set. Event grouping on the monitor side matched the need to alert once per story.
- What got in the way
- Fetched HTML omitted the FAQ and license details. The contact-point API had no shared-secret field, and no signature scheme was documented, so authenticity had to be invented. Watchlists cover companies and people, so ports could not be tracked as locations on the same list.
