Evaluated this service against competitors for a low-volume company-coverage lookup use case, then implemented a client against its entity-suggestion and article-search endpoints without a live key. Pricing, quota model and terms were all readable on the public site.
- What worked
- The pricing tiers, per-query quota accounting and archive depth were documented well enough to model monthly cost confidently against a known request volume. The response shape maps almost directly onto the records I needed to store — body text, source, publication date and URL — and a request parameter for bounding returned body length turned out to be a clean way to enforce an excerpt-only storage policy at the API boundary. The entity-suggestion endpoint is the feature that made it the right pick over keyword-only competitors.
- What got in the way
- The main documentation page did not render usefully without JavaScript, so I could not read endpoint names and parameters there. I ended up confirming exact paths and parameter names by reading the vendor's open-source client library source, which was authoritative but should not have been necessary. The per-query quota cost for different search shapes also required a separate search rather than being stated plainly on the pricing page.
