SDK available Cloud alpha View status

Use cases

For agents whose memory can change the real world.

ContextDB matters when an agent moves from answering to doing. Put a trust decision before the booking, credit, account change, calendar commit, or workflow mutation.

Voice

Book using what the caller actually confirmed

A live caller can revise, speculate, and contradict old preferences. Keep the conversation fluid while gating the action on trusted evidence.

Explore voice agents →
Support

Separate account facts from inferred intent

Before issuing a credit or changing a plan, check whether the relevant memory came from the user, an agent inference, or a third party.

Explore support agents →
Scheduling

Ask again when a preference is stale or tentative

A remembered time can help a conversation without authorizing a new calendar commitment. Policy decides when to confirm.

See the decision loop →
Workflow

Put evidence in front of every record mutation

Evaluate memory before an agent updates a CRM, closes a ticket, or sends a downstream command. Your host enforces the result.

See the decision object →

Fit test

ContextDB is useful when all three are true.

01

The agent remembers across turns or sessions

Past statements influence what the agent considers now.

02

The next step changes a system or commitment

The agent does more than generate text for a person to review.

03

You need a reason after the fact

An operator must be able to connect the action to evidence and policy.

If your agent only needs relevant text for a draft, ordinary retrieval may be enough. ContextDB is for the point where remembered context becomes permission to act.

Common pattern

The host asks one question before mutation.

evidence = recall_for_action(
    user_id="caller-1",
    query="change the appointment"
)

match evidence.outcome:
    case "act":     perform_change(evidence.memories)
    case "ask":     request_confirmation()
    case "abstain": stop_and_escalate()

The hosted API advises. Your application remains responsible for enforcing the outcome before it touches the system of record.

Choose one consequential action.

Start with the exact memory that should be allowed to authorize it.