Proof points
Indexed documents you can search, chart, and correlate by topic and organization.
Proof points are the underlying records behind Trendtracker signals: patents, news articles, research papers, earnings-call transcripts, PDFs, and grant projects. They come from document indexes, not the knowledge graph.
Use proof points when you need traceability, citations, or document-level filters. For structured deals and company records, use Facts. For grouped real-world events assembled from both, use Manifestations.
Every proof-point dataset exposes the same four shapes:
- Search — a page of enriched documents (
skip/take, max 100). - Time series — counts (and sometimes amounts) per time bucket at a
resolutionofday,week,month,quarter, oryear. Every bucket in the requested period is present; a bucket with no proof points has a count of0. See Release 0.0.5. - Correlation matrix — co-occurrence of topics and/or organizations. See Correlation matrix.
- Top terms — ranked topics or organizations in matching documents. See Top terms.
All of these are POST with a JSON body. Date filters apply to published date.
Shared request fields
| Field | Purpose |
|---|---|
query | Optional Lucene-lite text search (see below) |
topicQuery / gpeQuery / organizationIds | Scope to topics, regions (GPE UUIDs), and resolved organizations |
languages | ISO language codes |
sourceIds | Restrict to specific indexed sources |
start / end | Published-date window (ISO datetimes) |
skip / take | Offset paging; take max 100 |
sortColumn | published_at (default) or score |
sortDirection | desc (default) or asc |
Query syntax
query is a closed Lucene-lite expression over document text. Unprefixed words run a loose match on title, summary, and body. Use quotes for a phrase, field: to restrict a clause, and uppercase AND / OR / NOT (or -term) to combine them.
| Example | Meaning |
|---|---|
lithium | Loose match on title, summary, and body |
solid state battery | One loose multi-word match (not an AND of three terms) |
"solid state battery" | Phrase match on title, summary, and body |
title:lithium | Loose match on title only |
title:"solid state battery" | Phrase match on title |
title:(solid state battery) | Loose multi-word match on title |
document:"quantum sensing" | Phrase match on title, summary, and body |
title:"ssb" AND (body:lithium OR summary:anode) | Boolean combination |
(foo OR bar) baz | Implicit AND of already-delimited clauses |
Fields: title, summary, body, and document (all three). After field: use one token, one "phrase", or (...). title:solid state is rejected (a field prefix cannot be followed by extra bare tokens). Wildcards (*), fuzzy (~), and boost (^) are not supported. Lowercase and is a search token, not an operator. Unknown foo:bar is treated as a literal token so values like covid-19 stay valid.
Topic query syntax
topicQuery is a Lucene-lite expression whose terms are topic UUIDs, not free text. Consecutive UUIDs are combined with implicit AND. Each UUID matches that topic and its descendants. Quotes and body: are rejected.
topicQuery | Meaning |
|---|---|
a | Mentions topic A (or children) anywhere in the document |
a OR b | Former topicIds: [a, b] |
title:a | Topic A in title only |
title:a AND summary:b | Title has A and summary has B |
a NOT b | Has A, excludes B |
document:a | Same as unprefixed a (all topic mentions) |
Fields: title → topics__title, summary → topics__summary, document or unprefixed → topics.
GPE query syntax
gpeQuery uses the same Lucene-lite language as topicQuery, but terms are GPE UUIDs. Consecutive UUIDs are combined with implicit AND. Quotes and body: are rejected. Unlike topics, a GPE term does not expand to child regions — documents already store ancestor GPEs, so querying a country matches a city mention in that country.
gpeQuery | Meaning |
|---|---|
a | Mentions GPE A (or an ancestor of the tagged place) anywhere in the document |
a OR b | Former gpeIds: [a, b] |
title:a | GPE A in title only |
title:a AND summary:b | Title has A and summary has B |
a NOT b | Has A, excludes B |
document:a | Same as unprefixed a (all parent-GPE mentions) |
Fields: title → parent_gpes__title, summary → parent_gpes__summary, document or unprefixed → parent_gpes. Resolve IDs with GET /topics. See Release 0.0.4.
Datasets
- News articles — media coverage; optional
mentionsEventsfor partnerships and product launches - Patents — filings and grants
- Research articles — scientific publications
- Earnings calls — transcripts from finance sources
- PDFs — consulting reports and other PDF documents
- Projects — grant and R&D projects (replaces grants indicators)
Interactive schemas live in the API reference.