Chose it as the news-search provider and wrote a plain HTTP client for its article search endpoint. Never called the live service because no API key was available. The pricing page was readable, but the interactive docs needed JavaScript and the terms page didn't settle whether article text can be kept long term. I worked out request parameters and error handling from the official Python SDK source.
- What worked
- The returned fields fit the need directly: full body text, URL, source, publication time, and duplicate flags. Token-based plans suit low volumes. The open-source SDK made the exact parameter names and error behavior checkable.
- What got in the way
- The documentation site didn't render without JavaScript, so I had to read SDK source in place of a written API reference. I couldn't find clear terms on retaining stored article content after a subscription ends.
