Atomicbyte

• Vault Search — Run a bounded compound query against Vault's public /v1/query endpoint (natural-language query plus optional structured constraints: ids, kinds, stance, contested, lifecycle_state, typed temporal bounds, source_type/trust filters). Returns the Query Evidence Pack /v1/query produces — cited, structured evidence, never generated prose (Design Rule 1: Vault returns evidence, the caller's own model answers). Depth-1 include/expand is NOT available on this compound-query endpoint (POST /v1/query 400s
• Vault Get — Batch-fetch up to 200 Vault object ids (any atom id, entity, knowledge/forecast version, evidence span, or content chunk id) in one call via the public /v1/hydrate endpoint. Returns real per-type content (statement/typed fields/quoted text as authorized) at the requested level, never an empty placeholder envelope. The single most useful tool for resolving ids surfaced by vault_search/vault_list/vault_timeline/vault_changes.
• Vault List — List a page of a Vault /v1 collection (knowledge, forecasts, entities, claims, signals, predictions, causes, events, metrics, opportunities, daily-snapshots, story-groups, relationships, sources, domains, categories, capabilities — see /v1/capabilities for the live set). `filters` is passed through verbatim as query-string parameters (e.g. domain, category, entity, entity_role, contested, lifecycle_state, source, stated_after/before) — the collection's own /v1 route is the authority on which fil
• Vault Timeline — Fetch one entity's merged timeline (relations + events + metrics, ordered on the uniform governing_time axis) via the public GET /v1/entities/{id}/timeline endpoint. Supports the world-time (valid_at), knowledge cutoff (knowledge_as_of), and timeline-range (timeline_after/timeline_before, half-open) filters.
• Vault Changes — Fetch the public change feed via GET /v1/changes: object creations/publications plus lifecycle-flip deltas for atoms (FA-11 — flips only, atom creation stays excluded by design). Use `since` (RFC 3339 instant) to page forward from a prior read.

Schemas and invoke metadata: Directory API