Semantic Search
Perform a semantic search over all indexed document chunks using a query string. Returns the top-k most relevant chunks based on cosine similarity of embeddings, with optional filters for timestamp, keywords, tags, and minimum rating.
Semantic Search › Request Body
queryThe semantic search query string.
filter for results >= this integer unix timestamp.
filter for results <= this integer unix timestamp.
top_kNumber of results to return.
minimum_cosine_similarityfilters results for cosine similarity >= this value.
List of exact match keywords. If provided, returns results containing at least one.
List of tags to filter by. If provided, returns results containing all specified tags.
filters results for quality rating >= this value.
Semantic Search › Responses
Successful Response
cosine_similarityCosine similarity score between the query and the chunk embedding.
idUnique identifier for the chunk.
timestampUnix timestamp of the source document.
document_idIdentifier of the source document.
tagsList of tags associated with the chunk.
titleTitle of the source document.
contentContent of the chunk.
named_entitiesList of named entities extracted from the chunk.
ratingQuality rating of the chunk between 0.0 and 1.0.
Source information.
Semantic Search Multi
Perform semantic search across multiple queries in one request. Results are flattened, deduplicated, and returned in a single ranked list. Benefits (vs just making multiple semantic_search calls): 1. simpler client implementation, 2. smarter strategies for deduplication and ranking, 3. cheaper as duplicates arent charged.
Semantic Search Multi › Request Body
queriesList of semantic search queries.
total_top_kBest-effort target number of results to return after flattening and deduplication.
filter for results >= this integer unix timestamp.
filter for results <= this integer unix timestamp.
minimum_cosine_similarityfilters results for cosine similarity >= this value.
List of exact match keywords. If provided, returns results containing at least one.
List of tags to filter by. If provided, returns results containing all specified tags.
filters results for quality rating >= this value.
strategyRanking strategy for consolidating results across queries. Final output is always ordered by cosine_similarity. - 'cosine_similarity': rank purely by cosine similarity. - 'round_robin': interleave results from each query in a round-robin fashion to promote diversity across queries. - 'rank_sum': assign a score to each chunk based on its rank in each query's results and sum these scores across queries, promotes duplicates.
Semantic Search Multi › Responses
Successful Response
cosine_similarityCosine similarity score between the query and the chunk embedding.
idUnique identifier for the chunk.
timestampUnix timestamp of the source document.
document_idIdentifier of the source document.
tagsList of tags associated with the chunk.
titleTitle of the source document.
contentContent of the chunk.
named_entitiesList of named entities extracted from the chunk.
ratingQuality rating of the chunk between 0.0 and 1.0.
Source information.
Identify Stakeholders
Identify key stakeholders relevant to a given query, with optional context and instructions to guide the identification process.
Identify Stakeholders › Request Body
queryThe query / subject for which to identify stakeholders for.
Optional additional context to help identify stakeholders.
Optional additional instructions to guide stakeholder identification.
Optional start timestamp (unix epoch) to consider for time-sensitive queries.
Optional end timestamp (unix epoch) to consider for time-sensitive queries.
Identify Stakeholders › Responses
Successful Response
List of identified stakeholders with their impact details.
Factor matrix providing scoring for each stakeholder across defined factors.
Search Developments
Search for developments semantically (or not). Various filters available: timestamp, development type, stakeholder impact, and more.
Search Developments › Request Body
Semantic search query. If None, retrieves all developments matching the filters.
Filter for results >= this integer unix timestamp. None means realtime mode.
Filter for results <= this integer unix timestamp. None means realtime mode.
Filter for occurrence_timestamp >= this integer unix timestamp. None means no limit.
Filter for occurrence_timestamp <= this integer unix timestamp. None means no limit.
Filter by development type.
Filter by stakeholder symbol.
Minimum impact score filter in [-1, 1]. If both min and max are provided, matching is directional OR (impact >= min OR impact <= max).
Maximum impact score filter in [-1, 1]. If both min and max are provided, matching is directional OR (impact >= min OR impact <= max).
Minimum importance score in [0, 1].
Minimum surprise score in [0, 1].
Minimum confidence score in [0, 1].
limitMaximum number of results to return.
Search Developments › Responses
Successful Response
development_idLogical identifier for the development across updates.
timestampCanonical backtest system timestamp of this development version.
source_timestampMost recent timestamp of any source used for the development.
occurrence_timestampActual (estimate of) real world time that the development took place.
occurrence_timestamp_confidence_scoreConfidence score in estimate of occurrence_timestamp.
nameName of the development.
descriptionDescription of the development.
development_typeType of the development.
occurrence_statusStatus of the real world occurrence.
rationaleExplanation for all decisions made.
List of involved stakeholders and their impacts.
importance_scoreLLM heuristic of general development importance.
surprise_scoreLLM heuristic of how surprising the development is to the market.
confidence_scoreLLM heuristic of its confidence in everything it presents.
List of events this development is associated with, resolved to their most recent known state.
List of sources used for this development.
Retrieve Development
Retrieve a specific development by its ID.
Retrieve Development › Request Body
development_idThe ID of the development to retrieve.
Filter for results <= this integer unix timestamp. None means realtime mode.
Retrieve Development › Responses
Successful Response
Decision Table
| Variant | Matching Criteria |
|---|---|
| type = object · requires: development_id, timestamp, source_timestamp +13 more | |
| type = null |
development_idLogical identifier for the development across updates.
timestampCanonical backtest system timestamp of this development version.
source_timestampMost recent timestamp of any source used for the development.
occurrence_timestampActual (estimate of) real world time that the development took place.
occurrence_timestamp_confidence_scoreConfidence score in estimate of occurrence_timestamp.
nameName of the development.
descriptionDescription of the development.
development_typeType of the development.
occurrence_statusStatus of the real world occurrence.
rationaleExplanation for all decisions made.
List of involved stakeholders and their impacts.
importance_scoreLLM heuristic of general development importance.
surprise_scoreLLM heuristic of how surprising the development is to the market.
confidence_scoreLLM heuristic of its confidence in everything it presents.
List of events this development is associated with, resolved to their most recent known state.
List of sources used for this development.
Retrieve Event Developments
Retrieve all developments associated with a known event_id. Filters for timestamp and occurrence are available. Track and understand the full event lifecycle through its developments.
Retrieve Event Developments › Request Body
event_idThe event_id to retrieve developments for.
Filter developments with timestamp >= this unix timestamp. None means no lower bound.
Filter developments with timestamp <= this unix timestamp. None means realtime mode.
limitMaximum number of developments to return, ordered by occurrence_timestamp descending.
include_future_developmentsWhether to include developments whose occurrence_timestamp is in the future (relative to end_timestamp, or current time if end_timestamp is None). Set to False to restrict results to developments that have already occurred.
Retrieve Event Developments › Responses
Successful Response
Decision Table
| Variant | Matching Criteria |
|---|---|
| type = object · requires: event_id, name, description +2 more | |
| type = null |
event_idLogical identifier for the event.
nameName of the event.
descriptionDescription of the event.
event_typeType of the event.
Developments associated with this event, ordered by occurrence_timestamp descending (real-world timeline).
Search Events
Search for events semantically (or not). Various filters available: timestamp, occurrence, event type and more.
Search Events › Request Body
Semantic search query over event descriptions. If None, returns events ordered by recency of event creation.
Filter for events with development activity >= this unix timestamp.
Filter for events with development activity <= this unix timestamp. None means realtime mode.
Filter by event type.
limitMaximum number of events to return.
developments_per_eventNumber of most recent developments to embed per event result, ordered by occurrence_timestamp descending.
include_future_developmentsWhether to include developments whose occurrence_timestamp is in the future (relative to end_timestamp, or current time if end_timestamp is None) in the embedded per-event development list. Set to False to restrict to already-occurred developments.
Search Events › Responses
Successful Response
event_idLogical identifier for the event.
nameName of the event.
descriptionDescription of the event.
event_typeType of the event.
Most recent developments for this event (count controlled by developments_per_event param), ordered by occurrence_timestamp descending.