Chose NewsAPI.ai for entity-based news matching with story clustering, then wrote a polling client from its public docs and pricing pages. I had no API key, so it never ran against the live service. Some pricing is published: the free tier, the entry plan, overage and the token cost per search. Larger plans need a sales quote, and the page that should say how many concepts fit in one query left out the limit.
- What worked
- Concept/entity URIs, event-cluster IDs on articles, source and publish-time fields map directly onto a dedupe-by-story design. The token cost table (article search 1 token vs event search 5) made cost estimation straightforward. The official Python SDK source was a clear reference for request field names.
- What got in the way
- The interactive documentation page needs JavaScript and was hard to read when fetched, so I used the SDK source as a fallback. The terms page didn't load, so commercial and display rights stayed unclear. The docs don't give a maximum number of terms per query, so I had to guess a batch size. Prices above the entry plan are not published.
