Skip to main content

The result envelope

Research a company

Fictional request brief, entities, sources, values and dates. This is a documentation example, not a live HTTP response or customer result. Missing dates remain null.
Current availability: Reviewed bounded request. Execution: Manual / scoped. Automated invocation: Not currently available. API endpoint: None. MCP execution: None.
A research brief for human scope review, not an API payload.

Descriptive format

This result schema is a documentation contract and review format. It is not a live API response, a guaranteed automated serializer or a database export. Scope and delivery are agreed during manual review. task_type identifies an existing task. status describes evidence completeness, not job execution. The original entity and result.company fields remain compatible with V1. V1 entity and V2 subject are alternative identity representations: when subject is present, entity must be null. V2 subject identifies the researched entity; a null entity_type with a stated research_scope represents a market/list question without inventing an organization. Typed result.sections reference specific entity schemas. Customer-private context stays in its separately labeled result.customer_context and never becomes public entity data. result.company may remain null when typed sections carry the relevant detail. as_of is the explicitly recorded assessment time, or null. result contains the answer; evidence binds sources to field paths. unknowns and limitations remain separate from rights. Null means unknown or unavailable, not false, zero or recently checked. Source-dependent collections may be null when not assessed; an empty list alone does not establish that no relationship exists. No public confidence score or chain-of-thought is provided. Delivered-result use is governed by the agreement; the schema does not grant raw graph redistribution.

Fictional fit-assessment result

Every organization, person, source, date and finding below is fictional. Example.com links are placeholders. This example does not demonstrate a live executed task.

Fictional family-office research result

Fictional entities, sources, values and dates. Source URLs are placeholders, missing dates remain null, and private context is separately labeled. This is not a live customer result.

Fictional company ownership result

Fictional entities, sources, values and dates. Source URLs are placeholders, missing dates remain null, and private context is separately labeled. This is not a live customer result.

Fictional institutional-investor result

Fictional entities, sources, values and dates. Source URLs are placeholders, missing dates remain null, and private context is separately labeled. This is not a live customer result.

Fictional relationship-context result

Fictional entities, sources, values and dates. Source URLs are placeholders, missing dates remain null, and private context is separately labeled. This is not a live customer result.

Compatibility

Existing V1 company, organization and result documents remain valid. V2 adds typed sections and source categories; consumers with a closed V1 validator should use the current catalog and schema version before reading V2 results.

Shape and authorization are different

A valid schema does not establish source rights, buyer authorization or scope compliance. The operator must review those separately against the published task maximum before fulfillment. Typed sections preserve each entity’s meaning. A relationship references distinct parties; it does not deduplicate them. Evidence paths can point to fields inside a section. Unknown values stay null.

JSON Schemas