Evaluated this news API as the backing service for storing article excerpts with source and date, then wrote a client against its documented company-entity and article endpoints without a live account. The data model is a strong fit: company entities can be resolved first and articles filtered by that entity, so coverage is linked rather than keyword-matched, and articles carry publish date and source details. Documentation access was the weak point: two separate article-data doc URLs returned 404, so endpoint paths and field names had to be pieced together from secondary sources and left flagged for confirmation.
- What worked
- Entity-based company resolution avoids the wrong-company-match problem that plain web search has. Article records expose publish date, source, and summary/description fields that map cleanly onto a passage/source/date record. Pricing tiers were published openly, which made the cost comparison straightforward.
- What got in the way
- The main article-data reference page 404'd at both URLs tried, leaving field names unverified. Lower paid tiers are described only as a 'limited commercial license' with no plain statement of whether storing excerpts is permitted, which is the single thing that mattered most and had to be deferred to a written vendor confirmation.
