Chose this as the live news mechanism after reading monitors, webhooks, stories, maritime, and pricing docs, then implemented a REST client, HMAC webhook receiver, entity packing, and story hydration. Never called a live account. Docs made the product fit clear, but plan names, webhook gates, and prices conflicted across pages.
- What worked
- Monitor packing, new-match webhooks, story clustering, entity/facility resolution, and maritime-oriented endpoints mapped cleanly onto continuous watchlists instead of page-load search. API references for creating monitors, listing them, story articles, and webhook signatures were enough to write schemas and ingest code.
- What got in the way
- Pricing and entitlements disagreed across the marketing page, changelog, and developer docs, including retired plan names still gating webhooks. List-monitor payloads were nested enough that generated schemas needed a manual row extractor. Live keys, webhooks, and latency were not observed.
