Searching and Filtering
The IntelCenter API supports direct Component ID lookup, structured keyword search, natural-language retrieval, and Geo Manifest traversal.
Choose the Most Direct Method
- Known Component ID: use
/by-component-id/{component_id}. - Known record UUID: use
/{uuid}. - Exact terms or filters: use structured search.
- Conceptual request: use Natural Language Search.
- Analytical question: use Domain GenAI.
Component ID Lookup
Code
The number is a placeholder. A direct lookup avoids the ambiguity of treating an identifier as a keyword.
Keyword Search
Keyword-search performance has been materially improved without changing its public request or response contract.
Code
Common parameters:
| Parameter | Purpose |
|---|---|
search | Full-text search term |
entity | Associated entity |
country | Primary country |
date_from | Earliest date, formatted YYYY-MM-DD |
date_to | Latest date, formatted YYYY-MM-DD |
page | One-based page number |
per_page | Requested page size |
sort | Supported result order |
Support varies by endpoint. The API Reference is authoritative.
Natural Language Search
Code
Natural Language Search returns ranked records. Relevance scores are comparative signals, not probabilities or confidence guarantees.
Date Ranges
Dates are inclusive and use YYYY-MM-DD.
Code
URL Encoding
Encode spaces and reserved characters in query values. Most HTTP libraries do this when parameters are provided separately.
Geo Manifest Continuation
Geo Manifest results use deterministic newest-first ordering. Records with the same primary date are ordered by Component ID descending.
Start without a cursor. If the response supplies next_cursor, repeat the exact same dataset, component, filters, page size, and format with that cursor.
Code
Do not construct or modify cursor values. They are opaque and bound to the original request context. If a cursor is rejected as invalid or stale, restart the same request without a cursor.
