Retrieve data

MuBit exposes two default read patterns:

recall() when you want MuBit to answer a question from memory
getContext() / get_context() when you want a context block to send to your own model

Use raw control.query when you need explicit control over low-level request fields or want to debug wire-level behavior.

Retrieval decision model

Need	Recommended method
Answer a question from stored memory	`recall()`
Build a prompt-ready context block	`getContext()` / `get_context()`
Inspect memory quality and gaps	`diagnose()` and `memoryHealth()` / `memory_health()`
Explicit raw control over query payload	`client.control.query(...)`
Compatibility-only direct lanes	`client.core.*` advanced routes when explicitly enabled

Helper-first retrieval examples

Python
Node / TS
Rust

retrieve_helper.py

def retrieve_helper(client, run_id: str, question: str):
    answer = client.recall(
        session_id=run_id,
        query=question,
        entry_types=["fact", "lesson", "rule"],
    )
    context = client.get_context(
        session_id=run_id,
        query=question,
        mode="summary",
        max_token_budget=400,
    )
    return answer, context

retrieve_helper.ts

export async function retrieveHelper(client, runId: string, question: string) {
  const answer = await client.recall({
    session_id: runId,
    query: question,
    entry_types: ["fact", "lesson", "rule"],
  });

  const context = await client.getContext({
    session_id: runId,
    query: question,
    mode: "summary",
    max_token_budget: 400,
  });

  return { answer, context };
}

retrieve_helper.rs

use mubit_sdk::{GetContextOptions, RecallOptions};

pub async fn retrieve_helper(
    client: &mubit_sdk::Client,
    run_id: &str,
    question: &str,
) -> Result<(serde_json::Value, serde_json::Value), Box<dyn std::error::Error>> {
    let mut recall = RecallOptions::new(question);
    recall.run_id = Some(run_id.to_string());
    recall.entry_types = vec!["fact".to_string(), "lesson".to_string(), "rule".to_string()];
    let answer = client.recall(recall).await?;

    let mut context = GetContextOptions::default();
    context.run_id = Some(run_id.to_string());
    context.query = Some(question.to_string());
    context.mode = Some("summary".to_string());
    context.max_token_budget = Some(400);
    let context = client.get_context(context).await?;

    Ok((answer, context))
}

What the helper path buys you

recall() uses the current control-plane query contract without you assembling the raw payload manually.
getContext() / get_context() gives you sectioned, cache-friendly context assembly with optional budget control.
diagnose() and memoryHealth() / memory_health() help you understand why retrieval is weak before you start changing prompts blindly.

Failure modes and troubleshooting

Symptom	Root cause	Fix
Answer ignores an important lesson	Entry types or context budget too broad	Restrict entry types and use `getContext()` budgeting
Retrieval feels noisy	You are mixing compatibility-only direct lanes with routed paths	Standardize one default read path per workflow
You need wire-level parity checks	Helper abstracts too much	Drop to raw `client.control.query(...)` for that case

Next steps

Inspect the helper and raw surface split at SDK methods.
Review the full public control surface at Control HTTP reference.

Overview

Learn the basics

Build with MuBit

Go deeper

Platform

Help

Retrieve data

Retrieval decision model

Helper-first retrieval examples

What the helper path buys you

Failure modes and troubleshooting

Next steps

Overview

Learn the basics

Build with MuBit

Go deeper

Platform

Help

​Retrieval decision model

​Helper-first retrieval examples

​What the helper path buys you

​Failure modes and troubleshooting

​Next steps

Retrieval decision model

Helper-first retrieval examples

What the helper path buys you

Failure modes and troubleshooting

Next steps