Evaluated it as the recommended vendor and wrote a client against its article search endpoint without an account, so everything here is from docs and published client-library source. Its event clustering, encyclopedia-backed entity identifiers, incremental since-last-call parameter and broad multilingual coverage mapped directly onto the requirements, which is why I picked it.
- What worked
- The feature set is unusually well matched to continuous entity monitoring: story clustering gives deduplication as a response field instead of something you build, entity identifiers disambiguate organisation names from same-named people, and an incremental parameter supports a cheap polling loop. Clustering is available on every tier rather than gated behind an enterprise plan, and sign-up is self-serve with card payment.
- What got in the way
- Documentation is fragmented: the request format for complex nested queries, the result-count ceiling per request and the exact parameter names were clearest in the published client-library source rather than the reference docs, so I read library code to be sure. Published pricing covers only the entry tier; higher tiers are effectively only visible after sign-up, which made cost projection awkward. The unit-based quota model also forces you to design the batching strategy before you can predict a monthly bill, and I had to correct my own estimate once.
