Limitations
The IntelCenter API is designed for authorized retrieval and analysis. Integrations should account for the following limits.
Authorization Scope
Results reflect only the datasets, records, entities, and capabilities authorized for the API key. Empty, not-found, and unavailable responses must not be used to infer content outside that scope.
Search
- Keyword search matches indexed fields and does not guarantee conceptual equivalence.
- Natural Language Search returns ranked candidates, not exhaustive proof that no other relevant record exists.
- Relevance scores are comparative retrieval signals, not probabilities or truth ratings.
- A known Component ID should use the dedicated direct-lookup route.
- Date, entity, and country filters depend on the corresponding indexed metadata.
Paging and Counts
- Page sizes and result windows are bounded by the endpoint and account controls.
- Totals, when returned, describe the authorized result set for that operation.
- Do not infer unrestricted dataset size from paging fields.
- Geo Manifest traversal uses an opaque cursor; repeat the exact original request parameters when continuing. If a cursor is rejected, restart the same request without a cursor.
- A null exact-count field is not equivalent to zero.
Media Access
Player and viewer URLs are authorization-bound and may expire. Applications should request a fresh URL when needed and must not persist or redistribute temporary URLs.
Domain GenAI
- Answers can be incomplete or inaccurate and should be reviewed with their returned sources.
- Conversation context is dataset-specific and credential-bound.
- Conversations expire after 60 minutes of inactivity or 24 hours from creation, whichever occurs first.
- For long conversations, restate critical context when necessary.
- Successful turns consume the applicable credits.
- A repeated request can create another turn and charge; do not treat Domain GenAI as idempotent.
- Delete a conversation when its context is no longer needed.
Rate and Usage Controls
Requests remain subject to account quotas, credits, rate limits, and abuse protections. Clients should honor retry guidance, use exponential backoff with jitter, and avoid aggressive polling.
Data Freshness
New or updated records may not become searchable across every capability at exactly the same moment. See Data Freshness and Updates.
Service Evolution
Backward-compatible fields may be deprecated before removal. Review the Changelog and API Reference during upgrades. Deprecated fields remain supported only for the announced compatibility period.