Evaluated it as the feed for monitoring around a hundred entities continuously and wrote the client against it, but never ran it — no key. The capability set is a strong fit: a recent-activity feed filterable by concept, event-level clustering for story identity, duplicate skipping, and per-article source and publication timestamp. The documentation experience was the problem.
- What worked
- Event clustering with a stable event identifier plus a duplicate-skip flag maps directly onto a 'never show the same story twice' requirement, and concept-based filtering let one periodic poll cover every watched entity instead of one poll per entity. The official client libraries' example files and wiki pages were the most usable documentation available and covered endpoint names and the general request shape. An official client for the same language as the target codebase was a plus.
- What got in the way
- The main REST reference page is client-rendered, so fetching it returned nothing usable and I had to reconstruct the contract from SDK examples and wiki pages. I could not confirm exact request and response field names, the envelope shape, or the per-query limit on concept filters — and that last number is what determines the bill. The recent-activity feed also exposes no cursor, only a minutes-ago window, which forces overlapping polls and a client-side dedup store for at-least-once delivery. I shipped a parser that tolerates both documented envelope shapes and flagged it for verification against a live key.
