POST /v1/memory/context/assemble

POST /v1/memory/context/assemble

Builds layered execution context by combining recall, rules evaluation, and optional tool selection.

Request schema

Required:

1. query_text

Common fields:

1. tenant_id?: string
2. scope?: string
3. query_text: string
4. context?: object (runtime execution context)
5. include_rules?: boolean (default true)
6. tool_candidates?: string[]
7. return_layered_context?: boolean (default true)
8. context_layers?: object

Example request

curl -sS "$BASE_URL/v1/memory/context/assemble" \
  -H 'content-type: application/json' \
  -d '{
    "tenant_id":"default",
    "scope":"support",
    "query_text":"refund policy for enterprise",
    "context":{"intent":"billing_support"},
    "include_rules":true,
    "tool_candidates":["ticket_router","email_sender"],
    "return_layered_context":true
  }' | jq

Response schema

Key response fields:

1. tenant_id
2. scope
3. query (text, embedding_provider)
4. recall (includes trajectory and observability)
5. rules (optional)
6. tools (optional)
7. layered_context (optional)

Idempotency

1. Functionally idempotent for the same input and data snapshot.
2. Output can change when memory, rule state, or tool policies change.

Rate limit

1. Uses recall-class limiter and recall tenant quota.
2. Uses embedding quota for text-to-embedding phase.
3. If return_debug + include_embeddings is used, debug embedding controls also apply.

Error codes

Common errors:

1. invalid_request (400)
2. no_embedding_provider (400)
3. unauthorized / forbidden (401/403)
4. rate_limited_* (429)

Replay IDs to persist

1. request_id (from response envelope)
2. tenant_id
3. scope
4. caller run_id for downstream policy/action chain
5. decision_id from subsequent tool selection
6. relevant commit_uri values from recall candidates

Operational notes

1. Use this endpoint as planner input assembly before policy and tool execution.
2. Keep the same run_id across context assembly, tool selection, and action execution.