MindLynx
Sign in Contact Professional services Law, accounting, marketing and architecture practices. Growing businesses Answers about sales, cash and customers. Larger organisations A consultative route, governed at scale. Public sector & regulated Sovereign by default, with receipts.
Designed first for SMEs, starting with professional services. See who it's for →
Memory · Cortex
Memory for your agents. Knowledge for your people.
One store, and every line says who wrote it.Cortex is one memory for the whole organisation. Your agents and assistants recall it before they act and write back what they learn. Your people read it as Pages that stay up to date. It plugs in through MCP and an API, and keeps a record of every change.
✓ Any MCP client✓ REST API✓ Outside assistants ask first✓ A record of every change
Organised like a brain
It remembers the way you do.
Your brain doesn't keep everything. It holds what you're using, sleeps on the day, keeps what matters and lets the rest go. Cortex is organised the same way, so what your agents and people find is current, connected and trusted.
Decision Preference Fact Lesson
Run memoryLike sensory memory · seconds
What an agent has just seen or done. Most of it is never needed again. Working memoryLike short-term memory · hours
What is in use right now, held close so answers come quickly. Long-term memoryLike long-term memory · kept
Facts, decisions and lessons that proved useful and were checked, each with its source. SnapshotLike what you just know · ready
Summaries built ahead of time, so the right context is there before anyone asks. Memories arrive from chats, documents, imports and agents
It sleeps on itOvernight, the Weave reviews the day. It promotes what proved useful, merges what overlaps and lets the rest fade.
It changes its mind for good reasonsWhen new evidence disagrees with what it knows, the two are weighed. The stronger one stays, the other is kept with a note saying why, and a person can overrule.
It brings what's needed firstBefore an agent answers, Cortex hands it what it should already know, so nobody has to explain the same thing twice.
Every line says who wrote itEach memory carries its author and its source, whether that was a person, an agent or an assistant.
One memory, two ways in
Agents recall it. People read it.
Most tools give memory to agents or a knowledge base to people. Cortex is both, on one store, so what an agent learns overnight is on the Page your team reads in the morning.
Memory · for agents and assistantsMemory your agents can use
Recall before every answerSearch, ask, or let Cortex surface what matters at the start of each turn.
Write back what's worth keepingAgents store what they learn. Outside assistants ask a person first.
Any MCP client, or the APIAbout thirty tools for memories, Pages, people and files, and a REST API with scoped keys.
Pick up where you stoppedSave a session and carry on later, in the same assistant or another one.
Knowledge · for your peopleA knowledge base your team can read
Pages your team and agents write togetherEvery line shows who wrote it and where it came from.
Ask, and get the answer with its sourcesPlain questions, answered from what your firm actually knows.
See how it all connectsA map of people, clients and projects, one click from any Page.
Bring it in, take it with youImport what you already have. Export everything as Markdown, ready to open in Obsidian.
One store·One set of permissions·Agents and people see only what they're allowed to
Enterprise
Built for the whole organisation.
Cortex keeps every company, team and person apart, records every change and gives you the switches to stay in control. Every plan gets every control.
Each company kept apartYour organisation and each person come from sign-in, and every result is checked against its owner before it is returned.
Personal stays personalPrivate memories are visible only to the person they belong to.
Assistants ask firstWhat an outside assistant wants to keep is checked for injected instructions and waits for a person.
A ledger of every changeEvery read, write and erasure is recorded, without copying the content itself.
Forget means forgottenErase a memory everywhere it was used, and get a receipt to prove it.
Scoped keys and switchesKeys carry only the scopes they need, and every tool can be switched off on its own.
Hosted in EuropeEvery read is checked against the region your data belongs in.
Safety is never an upsellPlans differ in allowance, hosting and support. The controls are the same on all of them.
Where it fits
Memory tools serve agents. Wikis serve people. Cortex serves both.
Each kind of tool does its half well. Cortex keeps both halves in one store, under one set of permissions.
Agent memory layersMemory for agentsGive agents a memory through an API or MCP. Built for developers, and what the agent knows is usually seen through a dashboard.
Notes and wikisPages for peoplePages people write and link by hand, often with a graph to explore. Agents reach them as files or through a connector.
Enterprise searchSearch across systemsFinds what is already in your other systems, using their permissions. It searches knowledge rather than being where it is written.
CortexBoth, on one storeAgents write to it and people read it. Every line says who wrote it, assistants ask first and the ledger records every change.
For developers
Plug it into anything that speaks MCP or HTTP.
Connect an assistant in a minute, or build Cortex into your own product with the API. Here is how it works underneath.
Scoped keys
memory:read memory:write memory:delete pages:read pages:write compliance:admin
Live and test keys, with a sandbox. Pass your own user's ID and their memories stay apart from everyone else's. Sign in, or use a key An MCP client signs you in with your own account, so it only sees what you can see. Services use a scoped key instead.
Limits you can plan for 60 requests a minute per key and 600 per organisation. A spend cap you set, and an off switch for every tool.
How a memory moves Capture fast, understand slowly: the split the brain uses between the hippocampus and the neocortex.
01 Arrives From MCP, the API, imports or Helix. One way in for everything. Fast capture
02 Checked Owner and scope come from sign-in. Outside assistants wait for a person. A gate at the door
03 Understood Typed as a fact, decision, preference or lesson, with its author and source. What it means
04 Linked Joined to people, clients and projects, with links that say supports, contradicts or replaces. What it relates to
05 Woven Overnight the Weave merges, promotes and challenges, and keeps Pages current. Slow integration, like sleep
06 Recalled Search, ask, or surface at the start of a turn, within a budget, with sources. Ready when needed
The tools your agents get The same names over MCP, and the same actions in the API.
MemoriesKeep, find and forget
cortex_memory_storecortex_memory_searchcortex_memory_askcortex_memory_surfacecortex_memory_getcortex_memory_delete
PagesRead and write the knowledge base
cortex_page_createcortex_page_readcortex_page_editcortex_page_searchcortex_page_linkscortex_page_backlinkscortex_page_neighbourscortex_page_indexcortex_page_log
People and thingsWho and what a memory is about
cortex_entity_searchcortex_entity_link
FilesA workspace agents can edit
cortex_fs_viewcortex_fs_createcortex_fs_str_replacecortex_fs_insertcortex_fs_renamecortex_fs_delete
Sessions and sourcesCarry work over and check where it came from
cortex_session_savecortex_session_pick_upcortex_remind_mecortex_source_read
REST API/memory/v1
POST/memories
POST/memories/search
POST/memories/surface
POST/ask
GET/memories/:id
POST/memories/:id/correct
DELETE/memories/:id
GET/knowledge-pages
GET/knowledge/graph
·/export
·/erasure
WS/ws/cortex
It knows how things are done here.
One memory for your agents and your people, with every line traced to who wrote it.