Context Management - Overview

​

Endpoint references

​

Lifecycle

​

Core Ingestion Concepts

• Knowledge vs. Memories: Knowledge is shared, database-wide content (documents, app pages, Slack messages). Memories are user-specific preferences and conversational traits scoped by collection. Both can be searched together via type: "all" on POST /query.
• IDs: Unique identifiers returned by /context/ingest. You can assign custom IDs using id in metadata or id in app_knowledge items. Use them for polling status, inspecting content, and deleting context.
• Metadata Filtering: You can scope queries using metadata (structured fields defined in your database schema) or additional_metadata (free-form per-document JSON). For detailed guidelines on structuring metadata, see the Scoping using metadata guide.
• Forceful Relations: Relationships between sources can be declared at ingestion time to construct a robust knowledge graph. For more details on the graph layer, see the Context Graphs guide.

​

Forceful relations and metadata

result = client.context.ingest(
    type="knowledge",
    database="acme_corp",
    documents=[("runbook.pdf", f, "application/pdf")],
    document_metadata=json.dumps([{
        "id": "runbook_deploy",
        "metadata": {"department": "ops"},
        "additional_metadata": {"owner": "platform-team"},
        "relations": {"ids": ["monitoring_guide"]},
    }]),
)

​

Related sections

• Usage - Forceful Relations - linking sources at ingestion (see §7)
• Query - retrieve ingested content