get_context_pack()
KeyThe flagship read. One typed pack for a question: facts, beliefs, assumptions, hypotheses, causal edges, prior similar decisions with their outcomes, open contradictions — plus what's missing (missing_evidence) and where the system abstained. Every item is stamped available_at_decision_time, and the retrieval run is persisted so the pack can be reconstructed later.
get_context_pack(question, as_of, detail)→ CONTEXT PACKCallable over MCP as get_context_pack(question, as_of, detail). REST mirror POST /v1/context-pack Planned — alpha is MCP-only
The call before any judgment. One question in; one typed pack out — facts, beliefs, causal edges, prior similar decisions and how they turned out, open contradictions, and an explicit list of what's missing. Every item stamped with whether it was knowable at decision time. This is what "the agent checked before money moved" actually means.
Over MCP, your agent invokes it on its own when the moment calls for it — just describe the situation. A Python SDK for headless runtimes is planned; this is what the call will look like.
| Param | Type | Description |
|---|---|---|
| questionREQUIRED | string | The decision question to assemble context for. |
| as_of | timestamp | Assemble only what was knowable then. Default now — pinned automatically inside an open decision. |
| detail | enum | "summary" (default, ≤2k tokens) or "full". |
Run this call right here. The response is canned and spec-true — the exact shape your agent gets back over MCP, on sample data.
Sandbox — canned, spec-true responses. No key, no server, no live data.
// Press RUN to call get_context_pack() in the sandbox.
