Chose this as the ingest source after reading REST docs for stories, articles, monitors, webhooks, facilities, and maritime ports. Built a client, hourly poller, and signed webhook handler from those pages without a live key. Endpoint shapes and clustering were clear enough to implement; plan names, query-unit allowances, and dollar prices disagreed across marketing, changelog, and key pages, so billing for ~90 ports plus carriers took repeated lookups.
- What worked
- Stories, article source fields, HMAC webhook headers, entity batching for carriers, and facility monitors were documented in enough detail to pin exact paths and a no-duplicate story id.
- What got in the way
- Pricing and quota pages were inconsistent (retired Watch plan, mismatched free-unit counts, advertised monthly prices that did not match the plans-and-modules writeup). A pricing fetch also returned no dollar amounts. Port-pulse looked relevant but is not an article feed.