Overview
Medjat Memory Infrastructure
Medjat gives AI agents structured memory across sessions, agents, and time. One API call to store. One to recall. Everything else is handled.
What it solves
Most agents are stateless by default. Every session starts from scratch with no history, no user preferences, no learned context. Building memory in-house means wiring together storage, retrieval, TTL management, semantic search, and deletion flows. Medjat packages all of that into a single runtime.
Core concepts
Memory is agent scoped. Each agent has its own isolated memory space. No cross-agent bleed by default. Memories have types, retention rules, and can be recalled semantically or by key. Every delete operation produces audit friendly metadata.
Five memory types
Working · Episodic · Semantic · Procedural · Archival. Each with different retention defaults, suited to different data lifetimes. See Memory Types →
Quick Start
From zero to first recall
Get a memory stored and recalled in under 10 lines. Works the same in Python and TypeScript.
1. Install the SDK
# Python
pip install medjat
# TypeScript
npm install @medjat/sdk
2. Initialise the client
from medjat import MedjatClient
client = MedjatClient(
base_url="https://medjat.dev", # your project runtime URL
api_key="mj_live_...",
agent_id="agent_01"
)
3. Store a memory
client.memory.store(
content="User prefers dark mode and concise responses",
type="semantic"
)
4. Recall it later
results = client.memory.recall(
query="user preferences",
type="semantic",
limit=5
)
for m in results:
print(m.content)
Auth header (raw HTTP)
x-api-key: mj_live_...
x-medjat-agent-id: agent_01 # required in strict mode
Memory Types
Five types. Five lifetimes.
Each type is built for a different kind of data. You pick the type, Medjat handles retention and expiry.
working
Short-lived live context. Active session state, in flight task data, scratch memory.
Default 8h TTL
episodic
Event and session memories. What happened, when, and in what order.
Configurable TTL
semantic
Durable facts and knowledge. User preferences, learned truths, domain knowledge.
Default 365d TTL
procedural
Instructions, workflows, and how-to memory. How the agent should behave or execute tasks.
Default 180d TTL
archival
Long term records. Persistent unless explicitly deleted. No automatic expiry.
No TTL · Persistent
TTL defaults are runtime-configurable via environment variables. Override per-request by passing ttl_seconds on store.
API Reference
Core methods
All operations go through client.memory. Base URL is your project runtime, local or cloud.
client.memory.store(content, type, ttl_seconds?, metadata?)
Stores a memory of the given type. Returns a memory ID and confirmation. TTL is optional and defaults to the type's runtime default.
client.memory.recall(query, type?, limit?, threshold?)
Semantically recalls memories matching the query. Optionally filter by type. Returns ranked results with content, score, and metadata.
client.memory.forget(memory_id)
Deletes a specific memory. Returns a signed deletion receipt for audit purposes. GDPR compliant by design.
client.memory.stats()
Returns memory counts by type, storage usage, TTL state, and runtime telemetry for the current agent scope.
client.memory.summarise(type?, since?)
Generates a structured summary of stored memories, useful for context injection into prompts at session start.
Authentication
x-api-key: mj_live_... # required on all requests
x-medjat-agent-id: agent_01 # required in strict-mode runtimes
Service keys use the mj_service_... prefix. Agent keys (mj_live_...) are scoped to a specific agent identity.
SDKs
Python & TypeScript
Both SDKs are built on the same REST API and share identical method signatures. Real code, not vapor. Public package release is coming at launch.
Pre launch preview
Python
pip install medjat
from medjat import MedjatClient
client = MedjatClient(
base_url="https://medjat.dev",
api_key="mj_live_...",
agent_id="agent_01"
)
client.memory.store("User timezone is UTC+10", type="semantic")
TypeScript
npm install @medjat/sdk
import { MedjatClient } from '@medjat/sdk'
const client = new MedjatClient({
baseUrl: 'https://medjat.dev',
apiKey: 'mj_live_...',
agentId: 'agent_01'
})
await client.memory.store('User timezone is UTC+10', { type: 'semantic' })
Both packages are in pre launch development. The API surface is stable. Packaging and public release follow at launch.
Limits & Access
Early access & quotas
Medjat is pre launch. Early access users get direct runtime access ahead of public release.
Current status
Early access is open. Leave your details and we'll reach out personally. We onboard in small batches so we can actually support you.
Quotas
Free tier limits will be published at launch. Early access runs on preview quotas, generous enough to build with and sized to keep the runtime stable. If you hit a wall, contact us directly.
What you get at access
Memory API, all 5 types: store / recall / forget / stats / summarise
Agent scoping, isolated per agent memory out of the box
Local dev runtime, run the full stack locally with no cloud dependency
Python and TypeScript SDKs, pre release builds
Deletion receipts, signed records on every forget
Runtime telemetry, latency, memory counts, TTL state
Legal
Privacy Policy
Effective date: March 21, 2026 · Contact: privacy@medjat.dev
1. What we collect
When you use our early access form, we may collect your email address, any social handles you provide, and any message or notes you submit. We may also collect basic technical logs (request timestamps, IP metadata) for security and debugging.
2. Why we collect it
We use this information to manage and review early access requests, contact you about access and onboarding, and keep the service secure. We do not sell your personal data.
3. Your rights
Although Medjat operates outside the EU/UK, we provide GDPR-style rights to all users: access, correction, deletion, and objection to processing. To exercise any of these rights, email privacy@medjat.dev.
4. Retention
We keep early access submissions only as long as needed for access operations, product communications, and security recordkeeping. On deletion request, we delete your personal data unless limited retention is legally required.
5. Sharing
We share data only with service providers required to operate the product (hosting, analytics, email tools), under appropriate safeguards.
6. International processing
Your information may be processed in Thailand and in infrastructure regions used by our service providers.
7. Changes
We may update this policy as the product evolves. Updates will be posted here with a new effective date.
Contact
Privacy requests: privacy@medjat.dev
General legal: legal@medjat.dev
Legal
Terms of Use
Effective date: March 21, 2026 · Contact: legal@medjat.dev
1. Pre launch status
Medjat is a pre launch beta product. Features may change, break, or be removed at any time. We do not guarantee uptime, availability, or compatibility during pre launch.
2. Eligibility and access
You must provide accurate information for early access. Access is limited, revocable, and non-transferable unless we explicitly allow otherwise.
3. Acceptable use
You agree not to abuse, disrupt, or interfere with the service; circumvent auth, rate limits, or security controls; use Medjat for illegal content, malware, phishing, or fraud; scrape or attempt unauthorized access to data or systems; or reverse engineer private/internal endpoints.
4. API limits and fair use
Use is subject to rate limits and quotas that may change without notice. We may throttle, suspend, or revoke access to protect reliability and security.
5. Your content
You are responsible for all data and content you submit. You confirm you have rights to submit that content and that your use complies with applicable law.
6. Intellectual property
Medjat's software, branding, and documentation are owned by Medjat and protected by applicable IP laws. These Terms grant a limited right to use the service, not ownership.
7. Suspension and termination
We may suspend or revoke access at any time, including for policy violations, abuse risk, security issues, or capacity constraints.
8. Disclaimers
The service is provided "as is" and "as available." To the maximum extent permitted by law, we disclaim all warranties, express or implied.
9. Limitation of liability
Medjat will not be liable for indirect, incidental, consequential, or punitive damages, or loss of data, profits, or goodwill. Total liability is limited to amounts paid in the prior 12 months, or USD $100 if nothing was paid.
10. Governing law
These Terms are governed by the laws of Thailand, without regard to conflict-of-law rules.
Contact
Legal and terms: legal@medjat.dev
Privacy requests: privacy@medjat.dev
