> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qoory.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Bounded discovery

> Search, resolve, filter, and paginate without bulk entity enumeration.

Qoory exposes research workflows, not raw database tables. There is no endpoint
that returns every project, fund, person, token, stock, event, news story,
narrative, or X account.

## Search and resolve

Use search when you have a name, ticker, handle, or natural-language identity
query. The optional type filter can restrict work to one or more of `project`,
`fund`, `person`, `token`, `stock`, and `x_account`.

Use entity resolution when you need stable identifiers and supported detail
paths. A `null` detail path means the identity is valid but the corresponding
detail operation is not available in the current release surface.

## Curated discovery

When the user does not know an identity, begin with a bounded collection such
as trending projects, upcoming events, recent news, narratives, market movers,
or rankings. Apply the operation's entity, time, region, sentiment, or category
filters before increasing its limit.

## Limits and bounded windows

Current collection operations use explicit bounded limits rather than an
unbounded get-all route. REST v1 does not currently expose cursor or page-number
pagination. Treat each result as the bounded window described by its operation;
do not infer that increasing a limit or rotating filters produces a complete
database snapshot.

For scheduled ingestion:

* Store stable Qoory IDs or slugs, not array positions.
* Deduplicate records by the documented identity field.
* Respect observation and publication timestamps.
* Back off on `429` and stop on authorization failures.
* Do not rotate filters to reconstruct a bulk database export.