Picked as the news source for its concept-based entity matching and story clustering. Read the public pricing page, wrote a client for concept suggestion and article search, and checked both endpoints with a fake key. Never ran it with a real key, so data quality and uptime weren't tested.
- What worked
- The pricing page was readable and clear: token cost per request, overage rate, and the free tier. Endpoints were where I expected, accepted the key in the JSON body, and returned a clean 401 for a bad key. A GitHub wiki explained the real-time update options.
- What got in the way
- The documentation and terms pages only render with JavaScript, so a plain fetch couldn't read them. That left display rights and data retention terms unconfirmed. Errors come back as plain text rather than JSON, so the client has to check the status before parsing. Prices for larger plans aren't published. It's unclear how many concepts one query can hold, so I had to batch them conservatively.
