Conclude

POST /conclude goes beyond retrieval: it runs an agentic loop over the namespace's memories to answer higher-level questions, synthesize summaries, and surface patterns no single memory states.

Where consult returns memories for your prompt, conclude returns a conclusion — it consults, reasons, consults again if needed, and writes a synthesis.

Request shape

{
  "query": "what has the payments team decided this quarter?",
  "budget": "mid",
  "max_tokens": 1024
}

• budget — low for quick syntheses, high for deep multi-step reasoning.
• context — extra framing for the conclusion ("you are briefing a new hire").
• response_schema — a JSON Schema; conclude returns structured output matching it instead of prose.
• tags, tags_match, tag_groups, fact_types — scope which memories the loop may draw on.
• include_facts — return the supporting facts alongside the conclusion.
• exclude_automations — leave standing automation outputs out of the evidence.

Namespace identity

Conclude answers in light of the namespace's configured conclude mission and disposition — set them via namespace config. A support namespace can answer cautiously and cite tickets; an engineering namespace can be terse and technical.

Automations

An automation is a standing conclude query that re-runs as new memories land, so dashboards and briefings stay current without polling. Conclude powers each refresh; results are queryable per automation.

Conclude meters against the conclude quota — see Rate limits.