Documentation Index
Fetch the complete documentation index at: https://docs.auvy.ai/llms.txt
Use this file to discover all available pages before exploring further.
Search Guide
Search and browse are how most integrations discover content on the unified resource spine: indexed text lives inresource_chunks; POST /v1/search and POST /v1/browse are the primary HTTP surfaces. Paths use plural tokens (assets/, artifacts/, neurons/, …) with an optional pattern after /.
AUVY exposes one resource-addressing model across API, SDK, CLI, MCP, and Vault. Set a brain context for brain-scoped resources.
Setup
getBrainId or send X-Brain-Id.
Which Surface To Use
| Need | Use |
|---|---|
| List resources by type | auvy.resources.browse.list({ type: 'neurons' }) |
Keyword, substring, or hybrid type/pattern | auvy.resources.search.searchSemantic({ query: 'assets/refund', search_mode: 'hybrid' }) (same as deprecated resources.grep.query) |
| Keyword-only (no vector arm) | auvy.resources.search.searchSemantic({ query: 'assets/refund', search_mode: 'lexical' }) |
| Multi-type async search | auvy.resources.search.search({ q, types }) |
| Folder/Vault navigation | auvy.resources.browse.resourceTree({ parent_key: '/' }) |
| Owner-scoped RAG retrieval | auvy.recollections.search(...) |
Supported Path Tokens
/v1/search accepts the same primary path tokens:
assets, artifacts, stakeholder_maps, meetings, cortex_action_plans, receptors, pathways, neurons, reflexes
assets/ is the immutable document lane. artifacts/ is the mutable, versioned document lane. Use Assets and Artifacts for storage details.
Browse
Browse is list-only and has no text pattern:Hybrid search (/v1/search)
Default search_mode is hybrid: lexical matches on resource_chunks (and catalog heads for synapse kinds) merge with vector hits from the search-resource index when embeddings exist.
Use type or type/ to bias listing, and type/pattern to match indexed text. For keyword-only behavior (no vector merge), pass search_mode: 'lexical'.
type/pattern query. Async multi-facet:
Recollection Search
Use recollections when you want retrieval within a configured owner context, such as a trace or neuron:resource_type can target asset, artifact, or all.
Resource Trees
Vault-style navigation uses the merged resource tree, not text search:Best Practices
- Use browse or resource-tree for navigation, not text search.
- Use
POST /v1/searchwithsearch_mode: 'lexical'when you want keyword-onlytype/patternbehavior (default ishybrid, which adds vectors when indexed). - Use search for meaning-based retrieval or multi-facet discovery (
GET /v1/search+job_id). - Prefer
assets/andartifacts/in new queries;memories/is accepted as an alias and normalizes toassets/in responses. - Poll async search jobs through
auvy.jobs.getStatuswith backoff.