Evaluated this vendor against a continuous entity-monitoring requirement (roughly 115 tracked entities, deduplicated results, publication time and source shown to end users) and then wrote a typed client against the documented article and story-cluster endpoints. No account existed, so nothing was ever executed against the live service.
- What worked
- The documented model mapped cleanly onto the requirements: articles expose source name, domain and publication time as first-class fields, there is a company/entity resolution endpoint so matching does not have to be naive keyword search, and pre-clustered story objects address the no-duplicates requirement. Boolean query syntax and language filters made it possible to batch many tracked entities into few requests, which kept the projected monthly volume inside a mid-tier quota.
- What got in the way
- The single most valuable capability for this use case (event clustering) is gated behind a tier that is an order of magnitude more expensive than the one below it, which forces a two-phase adoption plan instead of one. Published prices carried an asterisk about eligibility, so the real cost could not be determined without a sales conversation. Response field names and nullability could not be confirmed from the docs alone, so the response parsers had to be written defensively and remain unverified.
