gomind.
Docs Start building
START WITH A MEMORY

A little context.
Your first connection.

Gomind stores facts as relationships between entities. Remember something once, then recall it in any session.

Before you begin

Create an organization and an API key in your Gomind dashboard. Set the key as GOMIND_API_KEY in your server environment. Run these examples on your server to keep your credentials private.

Remember. Recall. Repeat.

Choose your SDK, install it, and store your first fact. The same key connects your agent to the same memory across sessions.

SDK / API
$npm install @gomind/sdk
memory.ts
import { GomindClient } from '@gomind/sdk';

const memory = new GomindClient(
  'https://api.gominddb.com',
  process.env.GOMIND_API_KEY!
);

// A little context, remembered.
await memory.remember(
  'Maya', 'has_skill', 'TypeScript'
);

// A new session. A familiar user.
const { facts } = await memory.recall('Maya');
console.log(facts);
Memory persists. Even when the session doesn’t.↵
01 / INGESTION

Start with a conversation.

Already have raw text or a chat history? feed extracts facts and stores their connections. For role-based chat messages, use feedMessages.

await memory.feed(
  'Maya works at Acme and writes TypeScript.',
  'onboarding-conversation'
);
02 / ORGANIZATION

Give each context a home.

Collections are namespaces inside your organization. Create a collection in your dashboard, then pass its code to the SDK. Calls without a collection use the default bucket.

const memory = new GomindClient(
  'https://api.gominddb.com',
  process.env.GOMIND_API_KEY!,
  { collection: 'my-project' }
);

You can also supply collection on individual REST requests and MCP tool calls.

03 / ANY LANGUAGE

One API. Your stack.

Send JSON to https://api.gominddb.com with an Authorization: Bearer YOUR_API_KEY header. Successful responses wrap the returned data in result.

POST/v1/remember

Store a subject, relationship, and object as a connected fact.

POST/v1/remember_many

Store a batch of facts with an optional source for traceability.

POST/v1/recall

Retrieve facts with semantic search, entity matching, and relationship filters.

POST/v1/recall_connections

Explore an entity’s connections, up to five levels deep.

POST/v1/forget

Remove one specific subject–relationship–object fact.

POST/v1/forget_entity

Remove all facts about a particular entity.

POST/v1/feed

Extract connected facts from raw text or chat messages.

POST/v1/mind

Query memory in natural language with structured output.

Beyond a keyword match

Use recall with predicate, entity_type, or related_to to narrow results. Use recall_connections with an entity and depth to traverse relationships. Depth defaults to 2, with a maximum of 5.

04 / BUILT FOR AGENTS

Let your agent use its memory.

Hosted MCP is Streamable HTTP at https://mcp.gominddb.com. Claude, ChatGPT, and Grok connect with OAuth. Custom clients may send Authorization: Bearer with an API key. https://api.gominddb.com/mcp and legacy SSE at /sse still work.

remember

Store a subject, relationship, and object as a connected fact.

remember_many

Store a batch of facts with an optional source for traceability.

recall

Retrieve facts with semantic search, entity matching, and relationship filters.

recall_connections

Explore an entity’s connections, up to five levels deep.

forget

Remove one specific subject–relationship–object fact.

forget_entity

Remove all facts about a particular entity.

list_collections

List organization collections. Pass a code as collection on the other tools.

One memory, across your tools

REST, SDK, and MCP share organization and collection scope. Pass collection on a tool call, or omit it to use the connection default (OAuth consent collection, or the default bucket for API keys).

Back to Gomind