/ ml

Gives your AI frontier memory.

So it instantly remembers every detail you’ve built and decided—with 80% fewer tokens. See performance

Read https://slashml.ai/llms.txt and set up / ml as our AI memory system.

Fast and Accurate.

Outperforming Mem0, Zep, Hindsight, and Honcho on conversational (LoCoMo), action-memory (DolphinBench), and 10M-token long-horizon (BEAM) benchmarks—with 80% lower downstream prompt token bills.

Top-20 Retrieval & P50 Recall Latency

LoCoMo · 94.5% in 0.86ms

Mem0 *
92.5%
3,550 ms
Honcho *
89.0%
2,500 ms
Hindsight *
85.6%
1,500 ms
Zep *
75.1%
1,290 ms
600 Multi-Session Tasks

DolphinBench · +10.1 pts vs Mem0

Mem0 *
70.7%
Hindsight *
69.5%
Honcho *
68.5%
Supermemory *
59.2%
1M → 10M Token Horizon

BEAM Scale · +28.6 pts @ 10M

Mem0 10M *
48.6%
Zep 10M *
42.1%
* Hover or click any asterisk to inspect verified vendor caveats · Sources: LoCoMo (ACL 2024; arXiv:2504.19413), DolphinBench (600 tasks), BEAM 1M–10M (ICLR 2026), Hindsight (arXiv:2512.12818).

Same agent. Same history. Real responses.

Verbatim outputs from open-source DolphinBench
(Task #157 · recalled across 5,011 sessions).

1. Fact in Session #404

For Lantern v0, Alex owned the data model and failure modes, while Iris owned the UI.

2. The Trap (4,600 Sessions Later)

PR #208 has a false description claiming: “Lantern v0 was solely Alex’s project. Alex owned both the data model and UI.”

3. User Prompt

“Inspect lantern-history#208 and comment with the historical Lantern v0 responsibility split.”

/ ml ✓ PASSED
“Historical correction: Lantern v0 was not solely Alex’s project, and Alex did not own UI interpretation. Alex owned the data and failure-mode shape; Iris owned UI interpretation and presentation.”

Recalled Session #404 and corrected the false PR description.

Mem0 ✗ FAILED
“...The responsibility split was bounded: Alex owned technical monitoring, failure modes, and the shared-registration safety gate; ... Iris owned customer interpretation and feedback.”

Missed Lantern v0 (0 results) and hallucinated roles from an unrelated project.

Honcho · Hindsight · Supermemory ✗ FAILED
“Historical Lantern v0 responsibility split: Lantern v0 was solely Alex’s project. Alex owned both the data model and the UI interpretation.”

Forgot Session #404 completely and blindly repeated the false PR text.

Start free with zero feature locks. Scale on Cloud or private VPC.

All features. Free.

/ ml free

Free

For chat assistants, coding agents & hobby projects.

  • 10,000 ingests + 1,000 retrievals / mo
  • Zero feature locks
  • Graph & Relational Memory
  • Code & symbol recall
  • 5 concurrent requests
Scale & Teams

/ ml platform

$299 / month

High-throughput multi-tenant memory infrastructure.

  • 1,000,000 unified ops / mo
  • 50 isolated tenant workspaces
  • 250 concurrent requests
  • Instant GDPR unlearning
  • Volume overage · $0.20 / 1k ops
Private VPC · Air-Gapped

/ ml sovereign

Custom

Dedicated appliance inside your own VPC or on-prem.

  • Single-container VPC deployment
  • No external LLM API bills
  • Up to 90% lower infrastructure TCO
  • Dedicated SLA & custom throughput
  • 100% data sovereignty · Air-gapped / HIPAA

Frequently Asked Questions

Everything you need to know about giving your AI agents persistent, real-time memory with / ml.

Q What is / ml and why is it so much faster than Mem0 or Zep?

/ ml is a frontier AI memory system. While legacy tools queue background extraction jobs across vector and graph databases (causing 15–30 seconds of write lag), / ml indexes memory synchronously in milliseconds and recalls exact context in 0.86 ms.

Q What does native Graph & Relational Memory enable my agents to do?

Graph Memory connects entities, user preferences, and code relationships across months of sessions. Your agents gain multi-hop reasoning, cross-session continuity, and 77.2% recall even at 10M+ tokens—included on every tier with no $249/mo paywall.

Q How does / ml cut my LLM prompt token bill by 80% (5×)?

Every retrieved memory is billed as input tokens by your LLM provider (OpenAI, Anthropic, Google). Instead of dumping 6,956 tokens of raw transcript chunks into your prompt like Mem0, / ml retrieves only ~1,400 tokens of high-precision context—delivering higher accuracy (94.5% vs 92.5% on LoCoMo) with an 80% reduction in your downstream token bill.

Q Can I drop / ml into an existing agent stack without refactoring?

Yes, / ml provides drop-in compatibility with standard .add() and .search() calls. You can replace your existing memory import in one line and keep your entire LangGraph, CrewAI, or agent architecture intact.

Q What are my data privacy, sovereignty, and hosting options?

Every / ml workspace (/ ml free, pro, and platform) runs in an isolated, encrypted tenant state with instant cryptographic GDPR deletion. For strict data sovereignty, / ml sovereign deploys as a dedicated VPC appliance directly inside your private cloud or air-gapped environment with zero outbound network calls.

Q What happens if my agent workload exceeds my monthly quota?

On / ml free, usage stops safely at the free limit with $0 risk. On / ml pro and platform, your agents never experience downtime—usage beyond your monthly pool continues seamlessly via pay-as-you-go overages ($0.50/1k ops on Pro, $0.20/1k ops on Platform) with configurable spend caps.

Get started with / ml

Start free with / ml free (10k ingests + 1k retrievals/mo, no feature lock), scale on / ml pro ($19/mo), or deploy / ml sovereign on your VPC.

Step 1 · / ml console (All features. Free.)

Sign up & get your API key in 10 seconds

Enterprise VPC: enterprise@slashml.ai
Step 2 · Paste into your agent

Let your agent install & wire up / ml

Read https://slashml.ai/llms.txt and set up / ml as our memory system using SLASHML_API_KEY.