Data model overview - Qoory Docs

Every API response is a purpose-built public projection, not a serialized database row. Exact request and response fields come from the OpenAPI schema; this page explains how the entity families relate.

Entity	Stable lookup	Related resource families
Project	Slug and Qoory ID	Market, tokens, TVL, funding, events, features, news
Fund	Slug and Qoory ID	Portfolio, partners, rankings, news
Person	Slug and Qoory ID	Roles, investments, news, linked X account
X account	Opaque Qoory UUID	Optional canonical person or project link
Token	Qoory token ID	Market, tokenomics, unlocks, linked project
Stock	Slug and Qoory ID	Profile, rankings, crypto angle, news
Event	Slug and Qoory ID	Dates, location, speakers, participating projects
News	Canonical-story ID	Headline, publication context, linked entities
Narrative	Slug and Qoory ID	Summary, actors, timeline, bounded evidence

Identity rules

Slugs are readable identifiers for canonical entities; do not derive them from display names.
X accounts use an opaque Qoory UUID so integrations do not depend on a handle that can be renamed or reassigned.
Token symbols are not unique. Use the returned Qoory ID and project context.
Missing relationships are unknown, not proof that no relationship exists.

Response boundaries

Schemas return only the fields documented for an operation rather than complete storage records. Source attribution is included only when it is part of the documented research record. REST, MCP, and Skills use the same response shapes.

Exact schemas

The generated API reference is the source of truth for required fields, nullable values, enums, limits, examples, and errors. See API reference reference.