Schemas

End of the query window used (== the start the next run dedups against).

When this execution finished.

Terminal state of this execution.

Items found in the window (0 on no_data / endpoint_error).

Confirmation message indicating successful creation of the alert.

The unique identifier of the created alert.

The resolved name of the alert (provided or auto-generated).

A sample of the payload envelope that will be delivered to each receiver.

End of the query window used.

Latest successful per-receiver delivery time.

The envelope that was delivered ({name, response}).

Per-receiver delivery outcomes.

The ID of the alert.

The path of the desired endpoint.

A dictionary of arguments to call the endpoint with. Do not include 'start_timestamp' or 'end_timestamp' because the alert owns the polling window.

How often (in minutes) the alert checks the endpoint. Must be a multiple of 5.

1 to 2 delivery targets. Duplicate targets are rejected.

Optional human label for the alert, unique per user. Defaults to the endpoint name plus an index if omitted.

Rolling lookback window (in minutes). Defaults to interval_minutes if omitted.

Minimum number of matching items in the window before the alert fires.

Unique identifier for the alert.

Human label for the alert.

Current status of the alert.

The endpoint the alert polls.

The endpoint arguments.

How often the alert checks the endpoint, in minutes.

Rolling lookback window, in minutes.

Minimum item count before the alert fires.

The configured delivery targets.

end_timestamp of the last successful delivery, or null.

Recent execution attempts (no payload).

Recent deliveries (includes payload).

When the alert was created.

Logical identifier for the development across updates.

Canonical backtest system timestamp of this development version.

Most recent timestamp of any source used for the development.

Actual (estimate of) real world time that the development took place.

Confidence score in estimate of occurrence_timestamp.

Name of the development.

Description of the development.

Type of the development.

Status of the real world occurrence.

Explanation for all decisions made.

List of involved stakeholders and their impacts.

LLM heuristic of general development importance.

LLM heuristic of how surprising the development is to the market.

LLM 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.

Semantic search query. If None, retrieves all developments matching the filters.

Filter for results >= this ISO 8601 timestamp. None means realtime mode.

Filter for results <= this ISO 8601 timestamp. None means realtime mode.

Filter for occurrence_timestamp >= this ISO 8601 timestamp. None means no limit.

Filter for occurrence_timestamp <= this ISO 8601 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].

Maximum number of results to return.

Logical identifier for the development across updates.

Canonical backtest system timestamp of this development version.

Actual (estimate of) real world time that the development took place.

Confidence score in estimate of occurrence_timestamp.

Name of the development.

Description of the development.

Type of the development.

Status of the real world occurrence.

LLM heuristic of general development importance.

LLM heuristic of how surprising the development is to the market.

LLM heuristic of its confidence in everything it presents.

Raw list of event IDs this development is associated with.

Logical identifier for the event.

Name of the event.

Description of the event.

Type of the event.

Most recent developments for this event (count controlled by developments_per_event param), ordered by occurrence_timestamp descending.

Semantic search query over event descriptions. If None, returns events ordered by recency of event creation.

Filter for events with development activity >= this ISO 8601 timestamp.

Filter for events with development activity <= this ISO 8601 timestamp. None means realtime mode.

Filter by event type.

Maximum number of events to return.

Number of most recent developments to embed per event result, ordered by occurrence_timestamp descending.

Whether 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.

Logical identifier for the event across updates.

Name of the event.

Description of the event.

Type of the event.

Logical identifier for the event.

Name of the event.

Description of the event.

Type of the event.

Developments associated with this event, ordered by occurrence_timestamp descending (real-world timeline).

Unique snake_case primary key for the factor. Name must be entirely self contained and describe the situation unambiguously. Name should be consistent and reusable across separate calls.

What the factor represents. This will be embedded for semantic retrieval, so write it as a clean, general definition.

Scale of factor.

Mandatory scoring rubric for consistency. Keep it short but explicit. This should ensure absolute consistency globally across separate calls.

Only for CATEGORICAL: enum of allowed category strings.

A brief explanation of the reasoning behind the assessment for this stakeholder given the factor.

Assessed value (type depends on factor_type). 1. BINARY -> bool; 2. CONTINUOUS -> float in [0,1]; 3. SIGNED_CONTINUOUS -> float in [-1,1]; 4. CATEGORICAL -> str in allowed_values.

List of sources that support this factor assessment.

Factor definition.

Map: stakeholder symbol -> assessment object for this factor.

The source_metadata key to filter. Phase 1 supports publisher only.

Exact publisher values to include. At least one match is required when provided.

Exact publisher values to exclude. Every listed value is excluded when provided.

The receiver channel.

Where it was delivered (webhook url, telegram chat id, or account email).

Whether delivery to this receiver succeeded.

When this receiver was successfully delivered to, or null on failure.

Failure reason, or null on success.

The ID of the development to retrieve.

Filter for results <= this ISO 8601 timestamp. None means realtime mode.

The event_id to retrieve developments for.

Filter developments with timestamp >= this ISO 8601 timestamp. None means no lower bound.

Filter developments with timestamp <= this ISO 8601 timestamp. None means realtime mode.

Maximum number of developments to return, ordered by occurrence_timestamp descending.

Whether 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.

List of semantic search queries.

Best-effort target number of results to return after flattening and deduplication.

Filter for results >= this ISO 8601 timestamp.

Filter for results <= this ISO 8601 timestamp.

Filter results for cosine similarity >= this value.

Optional exact-match source metadata filters. Each filter specifies a supported source_metadata key and include_any / exclude_any values.

Optional overlap filter for chunk entity types. Returns chunks containing at least one requested entity type.

Filter results for utility_score >= this value.

Filter results for sentiment_score >= this value. Mutually exclusive with sentiment_score_le.

Filter results for sentiment_score <= this value. Mutually exclusive with sentiment_score_ge.

Ranking 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.

The semantic search query string.

Number of results to return.

Filter for results >= this ISO 8601 timestamp.

Filter for results <= this ISO 8601 timestamp.

Filter results for cosine similarity >= this value.

Optional exact-match source metadata filters. Each filter specifies a supported source_metadata key and include_any / exclude_any values.

Optional overlap filter for chunk entity types. Returns chunks containing at least one requested entity type.

Filter results for utility_score >= this value.

Filter results for sentiment_score >= this value. Mutually exclusive with sentiment_score_le.

Filter results for sentiment_score <= this value. Mutually exclusive with sentiment_score_ge.

Cosine similarity score between the query and the chunk embedding.

Unique identifier for the chunk.

System timestamp.

Identifier of the source document.

Title of the source document, if available.

Content of the chunk.

Canonical entity names associated with the chunk.

Utility score of the chunk between 0.0 and 1.0.

Sentiment score of the chunk between -1.0 and 1.0.

Source information.

Timestamp of the source item.

Table (Type) of the source item (e.g., 'news', 'earnings_calls', 'press_releases', etc.)

'id' of the source item

Additional metadata about the source item.

URL of the source material, if applicable.

Title of the source material, if applicable.

Publisher of the source material, if applicable.

Timestamp of the source item.

Table (Type) of the source item (e.g., 'news', 'earnings_calls', 'press_releases', etc.)

'id' of the source item

Additional metadata about the source item.

List of EXACT quotes from the source material.

Name of the stakeholder

The type of stakeholder. ONLY the following are allowed: [PUBLIC_COMPANY].

Ticker symbol of the stakeholder

The query / subject for which to identify stakeholders for.

Optional additional context to help identify stakeholders.

Optional additional instructions to guide stakeholder identification.

Filter for results >= this ISO 8601 timestamp.

Filter for results <= this ISO 8601 timestamp.

List of identified stakeholders with their impact details.

Factor matrix providing scoring for each stakeholder across defined factors.

The stakeholder being identified.

Impact score (-1.0 to 1.0) indicating the estimated magnitude and direction of the impact on the stakeholder.

Confidence score (0.0 to 1.0) indicating level of certainty in the stakeholder being materially impacted.

A brief explanation of why this stakeholder is relevant to the query

List of sources (with quotes) that support the identification of this stakeholder.

The Telegram chat id to deliver to. You must have started a conversation with the Ultralayer alerts bot first.

The URL to which the alert payload will be POSTed.

Optional headers to include in the POST to your URL.