Evaluated this news API against entity watches, story clustering, source and timestamp fields, and a continuous poll. Implemented a custom HTTP client, concept resolution, and a background ingester. Never called a live account; plan and token rules had to be reverse-read from a client-rendered pricing page.
- What worked
- Wikipedia-linked concepts and stable event identifiers matched watching ports and carriers once and showing each story only once, with source and publication time on each article. Paid tiers advertise real-time access, which fit an always-on API worker.
- What got in the way
- Official docs and a comparison post failed to fetch. The plans page was JavaScript-rendered, so a static download showed only one tier until the minified slider script was parsed. Concept-per-query caps disagreed across sources, and billing is tokens per poll rather than a monitoring SKU.
