Built with Astro, hosted on AWS behind Cloudflare. Domain registered in 2025.
supermemory.link is built with Astro, hosted on AWS behind Cloudflare. It measures traffic with Cloudflare Web Analytics and PostHog.
| Technology | Version | First seen |
|---|---|---|
| JavaScript Frameworks & Libraries1 | ||
| 7.3.1 | 9 Nov 2026 | |
| CDN & Hosting2 | ||
| – | 9 Nov 2026 | |
| – | 9 Nov 2026 | |
| Analytics & Tag Management2 | ||
| – | 9 Nov 2026 | |
| Advertising & Affiliate Tracking1 | ||
| – | 9 Nov 2026 | |
| Fonts & Icon Fonts1 | ||
| – | 9 Nov 2026 | |
| Security, WAF & Bot Protection2 | ||
| – | 9 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
Counted from every stack change we've recorded: of the sites we watched running one of this site's tools, how many went on to add another. A pattern across sites, not a forecast for this one.
ns1.vercel-dns.comns2.vercel-dns.comsectigo.compki.googletsencrypt.orgUser-agent: * Allow: / Sitemap: https://supermemory.ai/sitemap-index.xml Sitemap: https://supermemory.ai/sitemap-blog.xml Sitemap: https://supermemory.ai/sitemap-changelog.xml Sitemap: https://supermemory.ai/docs/sitemap.xml LLMs-Txt: https://supermemory.ai/llms.txt Content-Signal: ai-train=yes, search=yes, ai-input=yes
# supermemory
> Agents need memory. supermemory is building the default engine for memory and continual learning for agents, available through an API, plugins, and MCP.
supermemory builds the learning systems that make continuously improving AI possible. Our model, learner-1, extracts and dreams on the context of every user, task, and tenant, stores it in a vector-graph database, and brings it back to the model by injecting tokens into its context in real time. Learning and memory live outside the model providers, so they carry across any model and any harness. Today supermemory serves the memory and context for 100k+ organizations, with tens of millions of end users, processing over a trillion tokens every month.
## Quick Start
- [API documentation](https://supermemory.ai/docs)
- [Complete documentation index](https://supermemory.ai/docs/llms.txt)
- [Coding agent setup: CLI, skill, and docs MCP](https://supermemory.ai/docs/agents-and-mcp)
- [Quickstart: add, wait for processing, and retrieve](https://supermemory.ai/docs/quickstart)
- [TypeScript and Python SDKs](https://supermemory.ai/docs/integrations/supermemory-sdk)
- [Console: plugins, documents, memories, API keys, and billing](https://console.supermemory.ai)
## Core API Endpoints
Every memory route is scoped to one namespace (https://api.supermemory.ai/ns/{namespace}/...), and a namespace can be any scope: a user, an agent, a project, a team or an organization.
- Add content for memory extraction: POST https://api.supermemory.ai/ns/{namespace}/document
- Read a document and its processing status: GET https://api.supermemory.ai/ns/{namespace}/document/{id}
- Search memories and source passages: POST https://api.supermemory.ai/ns/{namespace}/search (searchMode: hybrid by default, memories, or chunks)
- OpenAPI specification (request schemas and authentication): https://supermemory.ai/openapi.json
- Moving from v3/v4 (they shut down on December 31, 2026): https://supermemory.ai/docs/migration/api-v5.md
API requests require an API key from the console, sent as Authorization: Bearer <SUPERMEMORY_API_KEY>. Keep keys out of browser code and public files.
Adding content is asynchronous: wait for processing to finish before retrieval. For immediate memory tests, the quickstart documents dreaming: "instant" and its additional operation charge.
The docs MCP at https://supermemory.ai/docs/mcp searches documentation for coding agents. The Memory MCP at https://mcp.supermemory.ai/mcp stores and recalls user memories; see https://supermemory.ai/docs/supermemory-mcp/setup for authentication and setup.
## Integrations
Works with: TypeScript, Python, REST API, Claude Code, Cursor, OpenClaw, OpenCode, Windsurf, Hermes, ChatGPT, Claude, Grok, Vercel AI SDK, LangChain, LangGraph, CrewAI, OpenAI SDK, Mastra, Zapier, n8n, Pipecat, LiveKit
- [All integrations](https://supermemory.ai/docs/integrations/supermemory-sdk)
- [Agents and MCP](https://supermemory.ai/docs/agents-and-mcp)
- [supermemory MCP](https://supermemory.ai/docs/supermemory-mcp/setup)
- [Connectors](https://supermemory.ai/docs/connectors/overview)
## What we do
- **Memory that keeps learning**: learner-1 extracts and dreams on the context of every user, task, and tenant, stores it in a vector-graph database, and brings it back to the model by injecting tokens into its context in real time.
- **What the engine does**: a memory graph where facts update, extend and derive from each other and are forgotten automatically; static and dynamic user profiles; namespaces for any scope; and retrieval over your documents (SuperRAG), with connectors and extractors for PDFs, web pages, images, audio and video.
- **Any model, any harness**: learning and memory live outside the model providers, so they carry across models and harnesses and stay interoperable, in context, and yours.
- **The hard infrastructure, done**: dense, interconnected, growing learnings with an understanding of time, already serving 100k+ organizations and over a trillion tokens a month.
- **Advanced document extraction**: Scale and Enterprise include advanced PDF extraction with OCR and descriptions of figures and diagrams. Free, Pro and Max keep standard PDF extraction. [Document support](https://supermemory.ai/docs/concepts/content-types#advanced-document-extraction).
## Research
- [Research](https://supermemory.ai/research/)
- MemoryBench (our open eval platform): https://git.new/membench
- [Blog](https://supermemory.ai/blog/): engineering notes, technical reports, and announcements
- [Learning](https://supermemory.ai/blog/tag/learning.md): guides on building agent memory
- [Engineering](https://supermemory.ai/blog/tag/engineering.md): engineering notes and technical reports
- [News](https://supermemory.ai/blog/tag/news.md): launches and announcements
- [Case studies](https://supermemory.ai/blog/tag/case-study.md): customer stories
## Compare
Pages by supermemory that compare it with other memory and retrieval products. The Mem0 page leads with an independent study; the blog posts spell out their method and workload.
**Head to head**
- [supermemory vs Mem0](https://supermemory.ai/compare/supermemory-vs-mem0/): an independent head-to-head (SWE-ContextBench) plus LongMemEval, features and migration
- [Supermemory vs Mem0: features, benchmarks and evaluation](https://supermemory.ai/blog/supermemory-vs-mem0/): documented capabilities, benchmark methodology, deployment options and a workload-specific cost model
- [Supermemory vs Zep](https://supermemory.ai/blog/supermemory-vs-zep/): Supermemory, managed Zep and Graphiti on the same workflow, evaluation conditions and operating-cost assumptions
- [Supermemory vs Cognee](https://supermemory.ai/blog/supermemory-vs-cognee/): documented capabilities, including managed hosting, multimodal input, memory operations and evaluation methodology
- [Supermemory vs Pinecone](https://supermemory.ai/blog/supermemory-vs-pinecone-which-is-better/): Pinecone Database, Pinecone Assistant and Supermemory at the right product boundary
- [Weaviate vs Supermemory](https://supermemory.ai/blog/weaviate-ai-database-reviews-pricing-alternatives/): Weaviate Database, Engram and Supermemory by application needs, processing behavior, pricing inputs and deployment
- [Mem0 alternatives](https://supermemory.ai/blog/mem0-alternatives/): Cognee, Letta, Supermemory, Zep and a custom stack against your data, lifecycle, hosting and migration requirements
**Choosing an approach**
- [Should I use supermemory?](https://supermemory.ai/docs/overview/comparison.md): how it compares with a DIY vector stack, thin memory layers, pure RAG and building it yourself
- [RAG vs agent memory](https://supermemory.ai/blog/rag-vs-agent-memory/): RAG for knowledge that is the same for every user, agent memory for what the agent should remember about each user
- [AI memory vs vector databases](https://supermemory.ai/blog/ai-memory-vs-vector-databases-complete-guide/): when a vector database is enough and when extraction, profiles, corrections and lifecycle management justify a memory service
**Switching**
- [Migrating from Mem0](https://supermemory.ai/docs/migration/from-mem0.md): move data and applications from Mem0
- [Migrating from Mem0: production playbook for the v5 API](https://supermemory.ai/blog/migrate-from-mem0-to-supermemory/): map entity scopes to namespaces, import with stable IDs, run both systems side by side, with rollback
- [Migrating from Zep](https://supermemory.ai/docs/migration/from-zep.md): move from Zep
## Pricing
Usage-based, with monthly credits included in every plan. Same per-unit rates on every plan; supported updates using the same customId in the same organization bill only the net-new token delta. New document identities and full replacements can incur fresh ingestion charges; search and other operations are metered separately.
- [Product](https://supermemory.ai/product/): what the memory engine does: memories, the graph that infers, updates and forgets, profiles, recall, connectors, SDKs and plugins, hosting (cloud, dedicated, or a local binary)
- [Pricing](https://supermemory.ai/pricing/)
- [Talk to sales](https://cal.com/supermemory/meet?overlayCalendar=true)
## Company
- Website: https://supermemory.ai
- GitHub: https://github.com/supermemoryai
- X/Twitter: https://x.com/supermemory
- Security: https://supermemory.link/security
- Contact: https://cal.com/supermemory/meet?overlayCalendar=true
## Optional
- [llms-full.txt](https://supermemory.ai/llms-full.txt): the long form, with features, endpoints, and pages
- [Changelog](https://supermemory.ai/changelog/)
| – |
| 9 Nov 2026 |
| – |
| 9 Nov 2026 |