Use case · Data
Reference and product records
The row itself: identifiers, attributes and the source they came from, for the one thing you are writing about.
What it is.
Structured facts about a thing, a product or a company, charged per record rather than per month of access.
What you send
An identifier, a name or a code.
What comes back
- The record, as fields rather than prose
- The identifiers it can be joined on
- Where the record came from
Who reaches for it
Anyone filling a gap in a spreadsheet, and agents that need a fact they can join on.
Instead of.
A database licence for a table you will read a hundred rows out of.
Reference and product records
An identifier, a name or a code.
Per request
The price is set by the provider and shown in euros before anything runs. Nothing renews, and a month you ask for nothing costs nothing.
The result
The record, as fields rather than prose, and the rest of the record with it.
More jobs
What else people ask for.
Search, mid-task
A web search an agent can call in the middle of a job instead of stopping and asking a person to look something up.
ResearchClaim verification
A statement checked against sources, with the sources returned, so the claim can be traced back rather than taken on trust.
ResearchSources from one country
Coverage filtered to where it was published, for the questions where the answer depends on who is asking it.
