TypeScript SDK
Use ConceptmemClient to submit observations and query memory from application code.
For builders
Shared memory for the agents you build.
Connect your application through the TypeScript SDK, HTTP API, or MCP. Let agents contribute observations and retrieve knowledge from the same workspace.
In practice
Carry a project update into the next task.
Illustrative integration. Agents use the workspace connection and credentials you configure.
- Planning agent
- Proposes a new project deadline.
- ConceptMem
- Consolidates the update under workspace policy.
- Delivery agent
- Reads the current deadline before planning work.
- Your team
- Inspects the source and change history in the console.
Built into the workflow
Choose how your agent connects.
HTTP API
Integrate with other languages through the /api/v1 endpoints and a workspace access key.
MCP tools
Expose memory operations to a compatible client through Streamable HTTP.
One set of memory rules across clients.
Every observation carries provenance and passes through consolidation. Agent writes follow the same ontology checks and policies as console writes.
Explore the MCP connectionCOMMON QUESTIONS
Agent integration, answered.
How does my application connect?
Three ways, against the same workspace: the TypeScript SDK for application code, the HTTP API for any other language, and MCP for a compatible agent or IDE client. Each authenticates with a workspace access key.
Do agent writes follow the same rules as console writes?
Yes. Every observation, regardless of the client it came from, passes through consolidation with the same ontology checks, policy resolution, and provenance requirement.
Can several agents share one memory?
That is the intent. A planning agent can propose an update and a delivery agent can read the consolidated result, without either replaying the other conversation.
How do I know whether a write actually landed?
A write result carries three lists: the operations applied, the writes skipped, and the violations found. A successful call with a non-empty skipped list means part of the payload was not stored.
Make your next update count
Start with one useful memory.
Create a workspace, define a type, and see your first observation become a traceable record.