Directories
Directories describe the entities behind the news rather than the news itself. Each profile combines Wikidata metadata, a coverage block showing how that entity is covered across the corpus, and its most recent articles — so one request answers "who is this and what is being written about them".
The three directories
| Directory | Endpoints | Contains |
|---|---|---|
| People | GET /v1/people · GET /v1/people/{id} | Public figures — politicians, executives, other known persons. |
| Companies | GET /v1/companies · GET /v1/companies/{id} | Organizations and brands, with headquarters, founding date, website, key people and subsidiaries. |
| Journalists | GET /v1/journalists · GET /v1/journalists/{id} | Article bylines, normalized by name — one record per journalist with an outlets array. |
Each has the same two-call shape: the list endpoint searches and filters, the {id} endpoint returns one full profile.
Directories vs. entity search
Both let you follow a person or company, and they answer different questions:
/v1/news/entity/{entity_id}returns articles mentioning the entity — a feed you page through.- A directory profile returns the entity — who they are, how much coverage they get, which outlets and topics dominate it, plus a handful of recent articles.
Build a dossier or a profile page from the directory, then switch to the entity endpoint when you need the full article stream.
Billing
A directory request costs 1 point, charged only when the response contains at least one result — zero-result searches are free. With no points left the request returns 402. See Balance and usage.
Next steps
- Build a person dossier — one call, full picture of a public figure
- Monitor a company — volume, sentiment and momentum over time
- Find journalists on a beat — who writes about a subject, and where