the multi layer memory deck

one memory for every model and agent.

memdeq keeps memory, records and files in one base, with one search across all of it. Any LLM or agent connects over MCP or a plain API, so every system you run works from the same facts.

MCP connectorHTTPS APIsign-in or keys
The memdeq deck Four stacked layers: memory, records, files, and reranking and quick access. LLMs and agents enter from the top through MCP or the API. mcp · api reranking andquick accessone searchfilesstoragerecordsthe databasememorywhat your AIs know

the deck

four layers, one deck.

Most tools give an AI one of these. memdeq keeps all four together, linked, under one set of permissions.

memory

what your AIs know

Short facts your AIs keep and reuse. General memory follows you into every assistant; other memories stay with the collection or the single record they are about.

  • General memory, collection memory, and memory on one record
  • One fact per memory, dated, and replaced when it changes
  • Pin the facts every AI should always see
memoryexample
about you pinnedInvoices go out on the 1st of each month.
about ContactsAdd the VAT number whenever a company is saved.
about Maria Georgiou recordPrefers a call before any offer is sent.

records

the database

Collections of records with real fields: contacts, tasks, knowledge, or anything you describe. Your AI sets one up from a sentence and keeps it tidy.

  • Typed fields, links between records, ready templates
  • Exact lists, filters and totals, never a guess
  • A repeated save updates the record instead of duplicating it
records · Contactsexample
NameCompanyStatus
Maria GeorgiouHalcyon Foodsactive
Andreas PetrouNorthline Freightlead
Elena CostaAtelier Noveactive

files

storage

Documents and photos, stored where they belong: on a record, in a collection, or on their own in general storage.

  • Storage per collection, per record, or general
  • The text inside PDF, Word, Markdown and CSV files is searched
  • Photos are found by what they show, even with no caption
filesexample
on Maria Georgiou text searchedoffer-signed.pdf
in Projects found by what it showskitchen-refit.jpg
general storage text searchedprice-list-2026.csv

reranking and quick access

one search under everything

One search reads all three layers. A name, an email or an id returns its record at once. Everything else is found by words, meaning and spelling together, then reranked.

  • Results come labelled strong or possible, so an AI knows what to trust
  • Fresh and often-used items settle the close calls
  • Most searches answer in under a second
searchexample
who asked for a call before the offer?
Maria Georgiou · Contactsstrongmatched a memory on the record
offer-signed.pdf · Filesstrongmatched text inside the document
Call, 3 November · Interactionspossiblematched by meaning

two doors

connects to every model and agent.

Assistants and agents use MCP, the open standard for giving an AI tools. Bots, automations and your own code use the API. Both doors open the same base.

mcp

For assistants and agents. Nothing to install and no key to paste.

  1. Add the address as a connector in your assistant.
  2. Sign in and approve the connection.
  3. Choose read only or read and write, and which collections it may reach.
connector address
https://memdeq.com/mcp

api

For bots, automations and anything you build. Plain HTTPS and JSON, with a key you can limit or switch off.

search from anywhere
curl https://memdeq.com/v1/search \
  -H "Authorization: Bearer $MEMDEQ_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query": "who asked for a call before the offer?"}'
the same ten actions on both doors guidesearchfindgetsaverememberrecallremovesetupattach

across all systems

the global memory for your operations.

Every system reads and writes the same base. The sales agent saves a contact, the support assistant recalls it, the finance automation totals it. Nothing is copied between tools, and nothing is trapped in one of them.

each connection gets its own rights

Read only or read and write. The whole base or only the collections you choose.

every write is signed

Each record, memory and file carries who wrote it and when.

switch one off, keep the rest

Stop a single bot or assistant at once. What it wrote stays.

One base in the middle of every system A sales agent, a support assistant, automations, your own apps and you in the web view all connect to the same memdeq base. mcp mcp api api web sales agent support assistant automations your own apps you, in the web view

for builders

a database you can build on.

Records are not locked inside a chat. The same collections answer exact questions through the API: lists, filters and totals. Use the base as the database behind your own tools, dashboards and internal systems.

POST /v1/find · open tasks per owner
{
  "collection": "Tasks",
  "where": [
    { "field": "Status", "test": "is not", "value": "done" }
  ],
  "totals": { "by": ["Owner"] }
}
POST /v1/save · add or update a record
{
  "collection": "Contacts",
  "records": [
    { "fields": {
        "Name": "Maria Georgiou",
        "Email": "maria@halcyonfoods.example"
    } }
  ]
}

independent by design

yours to see, control and take away.

see it

a page for everything stored

A web view of what your AIs saved: records, memories and files, with history and a trash you can restore from.

control it

you approve every connection

Nothing connects without your yes. Limit it, switch it off, or delete it, each on its own.

take it

export all of it

One download holds your data in an open format, with every stored file inside. Your AI will change. Your data stays yours.

start with one base.

memdeq is in private use today, and public access is being prepared. If you already have a base, sign in to see what your AIs stored.

sign in to your base