Problem
Your agent creates things. Documents, reports, code, research. Where does it all go?
Right now: S3 buckets, database blobs, temp directories.
No structure, no semantic understanding, no way to find anything later. Your agent can't even search its own work from yesterday.
Solution
Exabase's Resources API isn't just file storage.
Everything is semantically indexed. Search by meaning, not just filename. Your agent can find what it needs by describing it.
Powerful organisation tools with folders and tags.
Store links, files, notes and more. All context together in one place.
Dynamic self-optimising memory.
Managed for you.
A self-organizing memory engine, purpose-built from the ground up.
Not a vector database. A living, addressable network that interconnects concepts, learning and evolving with every interaction.
Add memories. Store facts, preferences, events. Anything you learn about a user.
Exabase builds a dynamic ontology: tracking relationships, resolving contradictions, evolving as new information comes in.
Search semantically. Find relevant memories by meaning, not keywords.
Get context. One call returns everything relevant for a task, formatted and ready for your prompt.
We handle extraction, indexing, relevance scoring, and retrieval. You focus on building.
Files — PDFs, images, documents, any file type. Uploaded and indexed.
Notes — Markdown notes. Full editor support, version history.
Bookmarks — URLs with metadata. Web pages are fetched and indexed.
Folders — Organize resources hierarchically.
Tags — Cross-cutting labels for flexible organization.
Most memory APIs are black boxes. You send data in, hope the right context comes out.
Exabase is different. We're the infrastructure layer behind Fabric, a knowledge platform where users store millions of notes, files, and links. The Resources API is built on the same foundation.
Full control. Create workspaces for your users, managed entirely by your app. Store and retrieve memories against your own user IDs. Full control, no dependencies.
MCP compatible. Use Exabase Memory as an MCP server. Works with Claude Desktop, Cursor, Windsurf, and any MCP-compatible agent.
Model-agnostic. Framework-agnostic.
SDKs
Python and JavaScript clients. Or call the REST API directly.
CLI
Use Exabase from the command line. Works with Claude Code, shell scripts, or anywhere you can run a terminal.
MCP support
Connect to Claude Desktop, Cursor, Windsurf, Continue, and any MCP-compatible tool.
Ready for scale
Fast
Sub-300ms retrieval. Infrastructure that won't slow your agent down.
Secure
Encrypted in transit (SSL) and at rest (AES-256).
CASA certified.
Reliable
99.9% uptime. Built on Exabase's consumer-grade scaled infrastructure.