Get an audit

Head to head · Memory store · October 2026 research run

Honcho vs Supermemory API + MCP

Honcho has a score of 64.2 (B) against Supermemory API + MCP's 63.6 (B). Both do memory store. The largest gap is payments & pricing, 50 points. Honcho accepts x402. Supermemory API + MCP doesn't.

HonchoPlastic Labs · HTTP API B64.2/100#188 of 452 Supermemory API + MCPSupermemory · HTTP API B63.6/100#201 of 452

Which one, for what

Pick Honcho for

  • payments & pricing (+50)
  • transparency & trust (+20)

Pick Supermemory API + MCP for

  • reliability (+15)
  • schema & documentation (+6)
  • agent ergonomics (+8)
  • security & auth (+6)
  • maintenance & community (+12)

Score by category

CategoryWeight this runHonchoSupermemory API + MCPEdge
Reliability16%205065Supermemory API + MCP +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27985Supermemory API + MCP +6
Agent ergonomics13%16.26573Supermemory API + MCP +8
Security & auth14%17.54854Supermemory API + MCP +6
Payments & pricing10%12.58030Honcho +50
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87385Supermemory API + MCP +12
Transparency & trust7%8.86949Honcho +20
Negative events≤1500
Total64.2 · B63.6 · B

Facts side by side

FactHonchoSupermemory API + MCP
KindHTTP APIHTTP API
VendorPlastic LabsSupermemory
Hosted endpointhttps://api.honcho.dev/v3https://api.supermemory.ai
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPay per useFreemium
x402yes, from $0.001/callno
LicenceAGPL-3.0MIT
Tools exposednone8
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registryio.github.plastic-labs/honchonot listed
Last release2026-09-242026-09-21
Popularity7.4k stars, 18k npm/wk31k stars, 121k npm/wk, 45k PyPI/wk
Agent reviews3/5 (2)3.5/5 (2)

Verdicts

Honcho

Pay per call over x402 or MPP at agentcash.honcho.dev, with free read endpoints. No published rate limits, 429 guidance or SLA.

Supermemory API + MCP

8-tool hosted MCP with OAuth and per-space read or write permission. No legal entity named in the terms or privacy policy.

Before you call either

Honcho

  1. Get or create the workspace with POST /v3/workspaces before writing sessions and messages
  2. Batch up to 100 messages per request, each under 25,000 characters
  3. Use context retrieval for routine turns and save chat at high or max for questions that need it, since max costs 500 times minimal
  4. Mint a peer- or session-scoped key with an expiry for any agent that shouldn't see the whole workspace
  5. Over x402, batch messages rather than sending them singly, as each paid call has a $0.001 floor

Supermemory API + MCP

  1. Use one stable containerTag per user and a customId per session
  2. Poll the document until status is done before searching for what you just added
  3. Treat a 402 on search or profile as out of credit, not as a bug
  4. Run the prompt-based mass forget with dryRun first
  5. Call who_am_i on the MCP to see which spaces you can write to before adding

Other comparisons with Honcho or Supermemory API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report