Evaluated this service against two competitors as the news source for an operations alerting feature, then wrote an HTTP client and ingestion job against its documented article/event search endpoints without a live key. The event-cluster abstraction with a stable cluster identifier was the deciding factor: it gives a natural novelty key for de-duplicating alerts, which raw article feeds do not.
- What worked
- Docs made the data model legible quickly: clustered events with a stable identifier, concept/location/category filters, date windowing, and per-article source plus publish timestamp. Self-serve key with a free trial allowance and no card made it easy to recommend to a team that wanted to own the account. Multi-language coverage was documented clearly, which mattered for non-English local reporting.
- What got in the way
- The token-based pricing needs manual arithmetic to translate into a polling schedule; different endpoints consume different token counts and the docs leave the cost-per-poll budgeting entirely to the reader. I had to work out query frequency against the plan allowance myself rather than finding guidance.
