/ ml

/ ml (SlashML) — 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.

Accurate and really fast.

Existing memory tools are wrappers that chain LLM prompt calls over external vector and graph databases—adding seconds of inference lag and stuffing thousands of noisy tokens into every prompt. / ml is a purpose-built native memory engine with zero external LLM calls in the memory loop, recalling exact context in 0.86 ms with 80% lower downstream prompt token bills.

Top-20 Retrieval & P50 Recall Latency

LoCoMo · 94.5% in 0.86ms

/ ml Top-20
94.5%
4,128× faster
0.86 ms
Mem0 Top-200 *
92.5%
3,550 ms
Honcho /chat *
89.0%
2,500 ms
Hindsight 120B *
85.6%
1,500 ms
Zep Graph *
75.1%
1,290 ms
600 Multi-Session Tasks · Accuracy & Task Latency

DolphinBench · 80.8% in 33.9s

/ ml
80.8%
33.9 s
Mem0 *
70.7%
37.7 s
Hindsight *
69.5%
55.3 s
Honcho *
68.5%
44.7 s
Supermemory *
59.2%
52.7 s
1M → 10M Token Horizon · 2.4 min Ingest ($0 LLM) vs. 16–40+ hrs

BEAM Scale · +28.6 pts & 250×+ faster @ 10M

/ ml 1M
83.5%
1.2 ms
/ ml 10M
77.2%
39.8 ms
Mem0 10M *
48.6%
>10,000 ms
Zep 10M *
42.1%
>8,000 ms
* 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 · 3.7× fewer tokens/query & 2.4 min zero-LLM ingest vs. 16–40+ hrs), Hindsight (arXiv:2512.12818).
Read full benchmark methodology, academic citations & vendor audit notes
  • * Mem0 (arXiv:2504.19413) — Top-200 Context-Stuffing, $249/mo Graph Paywall & 10M Scale Bottleneck: In Mem0’s published paper, standard Top-10 Retrieval scores 66.9% (68.4% with Mem0g Graph Memory, locked behind the $249/mo Pro paywall). Their blog’s 92.5% claim uses Top-200 Retrieval (~6,956 tokens/query = half of the entire 16K LoCoMo transcript stuffed into every prompt, multiplying downstream LLM token bills ~5× and pushing 26K-token P50 latency to 3,550 ms). On 10M-token BEAM (12.3M tokens, 20,561 chunks), Mem0 drops to 48.6% with recall latency exceeding >10,000 ms and 16–40+ hours of LLM ingestion calls (vs. / ml: 77.2% in 39.8 ms, 3.7× fewer tokens/query, and 2.4 min zero-LLM ingestion).
  • * Honcho (Plastic Labs) — Query-Time Dialectic LLM Synthesis & Background Dreaming: Honcho’s 89.0% LoCoMo score invokes a query-time /chat Dialectic LLM reasoning endpoint on top of background “dreaming” LLM synthesis workers—adding 1–5s of LLM inference latency (~2,500 ms P50) and secondary token billing on every recall. On 600-task DolphinBench, Honcho scores 68.5% at $142.85 (3.1× higher run cost than / ml).
  • * Hindsight (Vectorize, arXiv:2512.12818) — Backbone Swap & 159s–603s Tail Latency: Hindsight’s paper reports 83.6% (OSS-20B) / 85.6% (OSS-120B) and reaches 89.6% only by swapping the answering backbone to Gemini-3 Pro while running multi-pass agentic reflect loops. On DolphinBench it scores 69.5% ($84.65) with severe tail latency: 158.9s–602.9s (10 min) P95.
  • * Zep / Graphiti (arXiv:2501.13956) — Async Graph Queue Lag & 10M Graph Saturation: Zep scored 58.4% in Mem0’s evaluation (due to async Neo4j graph ingestion queue lag when queried immediately) and 75.1% in Zep’s 4-category re-run, with 1,290 ms P50 graph traversal latency at 26K tokens. On 10M-token BEAM (ICLR 2026), Zep drops to 42.1% with multi-hop graph traversal exceeding >8,000 ms per query and requiring 16–40+ hours of LLM entity/edge extraction (vs. / ml: 77.2% in 39.8 ms and 2.4 min zero-LLM ingestion).
  • * Supermemory — Negative Accuracy Lift (-6.5 pts) & 5.6× Cost Inflation: Supermemory self-reports 81.6%–85.2% on LoCoMo/LongMemEval subsets. On the independent 600-task DolphinBench coding & tool-use suite, Supermemory scores 59.2%—which is 6.5 percentage points worse than the Built-in no-memory baseline (65.7%)—while inflating total benchmark run cost to $345.64 (5.6× baseline cost).

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.