Mem0 scores Band A on The Headless Index and rates AI-Ready on JAIRF (81.8/100). Its strongest area for agent use is schema observability; its weakest is webhooks and events.

Does Mem0 publish an OpenAPI spec?

Yes. Mem0 publishes an OpenAPI specification, scored under JAIRF v1.0.0. A published spec is what makes an API discoverable and callable by agents rather than only by developers reading docs.

What is Mem0's Headless Index score?

Mem0 scores 81/100 on the Headless Index thesis-fit rubric and sits in Band A in the AI Platforms category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.

03 / Scorecard / AI Platforms

Mem0

Headless Index

81/100

JAIRF

81.8/100

AI-Ready

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

Mem0 earns Band A in the AI Platforms category of The Headless Index, with a thesis-fit score of 81/100 and a JAIRF rating of 81.8/100 (AI-Ready). Its strongest dimension is schema observability (18/20); its weakest scored dimension is webhooks and events (15/20). Mem0 publishes a machine-readable OpenAPI specification, which is what lets an agent discover and operate it without human glue code.

Editorial verdict

Mem0 is reference-class for machine consumption. The Headless Index thesis-fit score of 81/100 places it in the top tier of the index, and JAIRF v1.0.0 puts it at 81.8/100 (Level 3, AI-Ready). In practice, vendors at this tier publish enough machine-readable surface that agents can discover, authenticate, operate, and react to events without bespoke scaffolding, and the rest of this verdict explains where Mem0 lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. The hosted API at api.mem0.ai is versioned with visible intent: v1, v2 and v3 memory endpoints coexist beside /v1/entities, /v1/exports and /v1/memories/{memory_id}/history. Clients ship on both registries under the same name (mem0ai on npm at 3.1.6, mem0ai on PyPI). Authentication is one header token, which is simple but offers no scoping. The open-source core doubles as the SDK. An agent can drive this product end to end, and the published evidence supports that without unusual scaffolding. On headless operability: Because mem0 is Apache-licensed and the server is the same code you self-host (github.com/mem0ai/mem0), no dashboard-only tier guards the core memory operations. Projects, webhooks, entities and exports are all API-managed. What is missing sits around the edges: no CLI, no Terraform provider, and organization billing still lives in the hosted console.^[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: Mem0-mcp (github.com/mem0ai/mem0-mcp) is a first-party server with meaningful adoption, and OpenMemory extends the same idea into a local-first store that several agents can share. Memory is a natural MCP primitive and mem0 recognised that early. The server has not been committed to since March, which is a maintenance concern rather than an architectural one.^[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Webhooks are declared in the spec rather than buried in prose: a project-scoped endpoint (/api/v1/webhooks/projects/{project_id}) creates subscriptions with an enumerated event_types list covering memory_add, memory_update, memory_delete, memory_categorize and ingest_job_failed. Agents can manage their own subscriptions programmatically. What the spec never carries is a signing scheme or a stated retry policy, leaving payload authenticity unverifiable. Net assessment: Mem0 is among the cleanest agent-targets in its category. The lightest of the criteria in this run is webhooks and events^[3], and even there the surface area is workable for automated integration. Treat this scorecard as a green light for unattended use. Strong fit for agent-driven use cases.

Verdict by Headless Index pipeline (auto)

// AI-drafted from the evidence layer. Editorial review pending.

Scores

Scorecard detail

Headless Index · 5 sub-criteria

API-first design intent16/20

scored

The hosted API at api.mem0.ai is versioned with visible intent: v1, v2 and v3 memory endpoints coexist beside /v1/entities, /v1/exports and /v1/memories/{memory_id}/history. Clients ship on both registries under the same name (mem0ai on npm at 3.1.6, mem0ai on PyPI). Authentication is one header token, which is simple but offers no scoping. The open-source core doubles as the SDK.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
+OpenAPI specPublished, 55 operations
·GraphQL endpointDiscovered at https://mem0.ai/graphql, introspection disabled or scoped
−SDKs maintainedNone detected in vendor org

cite (1)

github.sdks@2026-08-19

Headless operation16/20

scored

Because mem0 is Apache-licensed and the server is the same code you self-host (github.com/mem0ai/mem0), no dashboard-only tier guards the core memory operations. Projects, webhooks, entities and exports are all API-managed. What is missing sits around the edges: no CLI, no Terraform provider, and organization billing still lives in the hosted console.

signals (9)

+AI review appliedReviewer: Editorial review on 2026-08-19
·API operations exposed55 operations in OpenAPI spec
·Docs pages crawled0 pages (crawler: none)
·Auth schemes documentedAuth documentation page not reached by crawler
·Setup / quickstart docsNot reached by crawler
·Billing docsNot reached by crawler
·Teams / org docsNot reached by crawler
·CLI docsNot reached by crawler
·Schema / data model docsNot reached by crawler

cite (1)

ai_review_browser.topics_found@2026-08-19

MCP & agent posture16/20

scored

mem0-mcp (github.com/mem0ai/mem0-mcp) is a first-party server with meaningful adoption, and OpenMemory extends the same idea into a local-first store that several agents can share. Memory is a natural MCP primitive and mem0 recognised that early. The server has not been committed to since March, which is a maintenance concern rather than an architectural one.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
+Official MCP serverhttps://github.com/mem0ai/mem0-mcp (659 stars, last commit 148 days ago)
−Community MCP serversNone found
−Agent-friendly SDKsNo TypeScript/JavaScript SDK published (agents commonly run in TS/JS)

cite (1)

ai_review_browser.mcp@2026-08-19

Schema observability18/20

scored

A complete OpenAPI 3.0.1 document sits unauthenticated at a stable docs URL (docs.mem0.ai/openapi.json), describing 36 paths with request bodies, enums and the ApiKeyAuth token scheme. An agent can generate a client and work out the v2 versus v3 search differences without reading prose. That places mem0 ahead of most AI infrastructure vendors, where specs usually stay locked inside the SDK build.

signals (3)

+AI review appliedReviewer: Editorial review on 2026-08-19
+OpenAPIPublished at https://docs.mem0.ai/openapi.json (OpenAPI 3.0.1, 55 operations)
·GraphQL introspectionGraphQL endpoint at https://mem0.ai/graphql but introspection is disabled, scoped, or behind authentication

cite (1)

ai_review_browser.schema@2026-08-19

Webhooks & events15/20

scored

Webhooks are declared in the spec rather than buried in prose: a project-scoped endpoint (/api/v1/webhooks/projects/{project_id}) creates subscriptions with an enumerated event_types list covering memory_add, memory_update, memory_delete, memory_categorize and ingest_job_failed. Agents can manage their own subscriptions programmatically. What the spec never carries is a signing scheme or a stated retry policy, leaving payload authenticity unverifiable.

signals (2)

+AI review appliedReviewer: Editorial review on 2026-08-19
·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.

cite (1)

ai_review_browser.pages_fetched@2026-08-19

JAIRF · 6 dimensions

FCFoundational Compliance

100/100

Structural validity, standards conformance, and parsability of the OpenAPI specification.

DXJDeveloper Experience & Tooling Compatibility

69.5/100

Documentation clarity, example coverage, response completeness, and ingestion health.

ARAXAI-Readiness & Agent Experience

74.6/100

Semantic clarity, intent expression, datatype specificity, and error standardization.

AUAgent Usability

90/100

Operational composability, complexity comfort, navigation affordances, and safety patterns.

SECSecurity

80/100

Authentication strength, transport security, secret hygiene, and OWASP risk posture.

AIDAI Discoverability

65/100

Descriptive richness, intent phrasing, workflow context, and registry signals.

Band rationale:A band: JAIRF=81.8 HeadlessIndex=81

04 / Embed

Show Mem0's score on your site.

Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.

Get embed code

Calibration

How THI compares to external scorers

Source	Score	Measures	Last checked
Fern Agent Score	not found	Documentation completeness and SDK shape (~22 checks)	—
CLIRank Agent Friendliness	not found	CLI readiness, docs quality, and overall agent affordances	—
Cloudflare Is It Agent Ready?	blocked	Cloudflare's manual agent-readiness heuristic per vendor URL	—
Jentic Scorecard	—	JAIRF-based scorecard requiring a public OpenAPI specification	—

THI 81 vs external median 0

No external scores available to calibrate against.

Peers in AI Platforms

LiteLLMB

Headless Index 77/100

ReplicateB

Headless Index 76/100

OpenAIB

Headless Index 86/100

See full AI Platforms ranking →

FAQ

Mem0 and agent readiness

Is Mem0 agent-ready?: Mem0 scores Band A on The Headless Index and rates AI-Ready on JAIRF (81.8/100). Its strongest area for agent use is schema observability; its weakest is webhooks and events.
Does Mem0 publish an OpenAPI spec?: Yes. Mem0 publishes an OpenAPI specification, scored under JAIRF v1.0.0. A published spec is what makes an API discoverable and callable by agents rather than only by developers reading docs.
What is Mem0's Headless Index score?: Mem0 scores 81/100 on the Headless Index thesis-fit rubric and sits in Band A in the AI Platforms category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.