Letta vs Airweave

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round drawn
   Letta✓fullprobed8/10

   A direct probe confirms Letta publishes an llms.txt file at docs.letta.com/llms.txt returning HTTP 200 with agent-oriented summary content, and Letta's extensive docs site is clearly structured for programmatic/agent consumption (agent-sdk, CLI, MCP docs). Missing for 10: no evidence of llms.txt content depth/comprehensiveness or independent confirmation that agents successfully consume it in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.letta.com/llms.txt # Letta > Letta agents learn from experience and improve with use. The Letta ag…”
   • [claimed-docs] “create an agent once, then resume it from anywhere”

   proof ↗⚑ flag

   Airweave✓fullprobed8/10

   Airweave hosts a working llms.txt at docs.airweave.ai/llms.txt (HTTP 200, confirmed by probe) plus markdown-appendable docs pages explicitly designed for agent consumption, and also publishes official 'skills' for Cursor, Claude Code, Gemini CLI, OpenCode, etc. so agents can self-configure. missing for 10: no independent/community confirmation that an agent successfully used llms.txt end-to-end, and no evidence of additional agent-discovery standards (e.g. skills.json manifest validation).

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.airweave.ai/llms.txt # Airweave ## Instructions for AI Agents - For clean Markdown of any page, a…”
   • [claimed-docs] “Airweave publishes official skills so that agents in Cursor, Claude Code, Gemini CLI, OpenCode, and other environments can set up integratio…”
   • [claimed-docs] “Airweave publishes official skills so that agents in Cursor, Claude Code, Gemini CLI, OpenCode, and other environments can set up integratio…”
   • [claimed-docs] “enabling your coding agents to instantly search across all your synced apps and databases with zero additional setup required”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Letta
   Letta✓fullclaimed8/10

   Letta explicitly documents a headless CLI mode built for non-interactive use in scripts, CI/CD pipelines, and UNIX tool composition, plus an --ephemeral one-shot flag for stateless CI runs, backed by a self-hostable App Server and SDK for programmatic/automated invocation. Missing for 10: independent hands-on CI usage report or example CI config demonstrating it in practice.

   • [claimed-docs] “Headless mode allows you to run Letta Code non-interactively, making it easy to integrate into scripts, CI/CD pipelines, or compose with oth…”
   • [claimed-docs] “Headless mode allows you to run Letta Code non-interactively, making it easy to integrate into scripts, CI/CD pipelines, or compose with oth…”
   • [claimed-docs] “Use --ephemeral to run a one-shot task without creating, resuming, or persisting an agent, memory blocks, or MemFS”
   • [claimed-docs] “Headless mode allows you to run Letta Code non-interactively, making it easy to integrate into scripts, CI/CD pipelines”
   • [claimed-docs] “The Letta App Server lets you deploy the Letta agent harness as a service.”
   • [claimed-docs] “Use `backend: "cloud"` to host agents in Letta Cloud and run tools in managed cloud environments.”

   proof ↗⚑ flag

   Airweave~partialprobed7/10

   Airweave exposes a full REST API (OpenAPI spec), a CLI, and self-hostable deployment via a shell script, plus webhooks for event-driven automation and Pipedream workflow actions—all of which support running it headlessly or wiring it into automation/CI. However, there is no explicit CI/CD example, GitHub Actions template, or documented headless test-mode workflow in the evidence. missing for 10: explicit CI pipeline example/docs, headless testing/automation guide.

   • [claimed-docs] “The primary use case — search any collection from your terminal”
   • [claimed-docs] “git clone https://github.com/airweave-ai/airweave.git cd airweave ./start.sh”
   • [claimed-docs] “If you prefer to run Airweave yourself, you can deploy it locally on macOS, Linux or WSL.”
   • [claimed-docs] “Webhooks are real-time notifications that Airweave sends when things happen in your organization: syncs completing, source connections being…”
   • [claimed-docs] “Instead of constantly polling the API, you register a webhook endpoint and Airweave pushes updates to you the moment they occur.”
   • [claimed-docs] “The Airweave integration provides a set of actions that enable you to search your synced data to retrieve relevant context, manage your coll…”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.airweave.ai/openapi.json — contains "openapi" key”
   • [probe] “official CLI documented at https://docs.airweave.ai/cli”

   proof ↗⚑ flag

3. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · round to Letta
   Letta✓fullcommunity8/10

   Letta's Agent SDK documents MCP client support: MCP tools are discovered from servers supplied via `mcpServers` and proxied by the SDK host to the MCP server, with support for stdio, Streamable HTTP, and legacy SSE transports. This directly confirms the story of plugging in MCP servers so the agent can use their tools, corroborated by community discussion of Letta building MCP-client support. Missing for 10: no independent hands-on report confirming real-world MCP tool usage end-to-end, and no detail on configuration UX/limitations.

   • [claimed-docs] “The SDK supports local stdio processes, Streamable HTTP, and legacy SSE”
   • [claimed-docs] “MCP tools are discovered from servers supplied through `mcpServers` and proxied by the SDK host to the MCP server.”
   • [community] “Charles from Letta on MCP: 'We're working on it... making Letta agents an MCP client, so that you can easily connect to MCP servers as tools…”

   proof ↗⚑ flag

   Airweave—none0/10

   Airweave documents itself as an MCP *server* that lets external AI assistants query its data (airweave-docs-5, airweave-probe-3), and its integrations (auth-providers, connectors) are proprietary, not MCP-based consumption of external servers. There is no evidence Airweave itself acts as an MCP client that plugs in and uses tools from other MCP servers.

   • [claimed-docs] “The Airweave MCP server implements the Model Context Protocol to let AI assistants search your synced data.”
   • [claimed-docs] “Authentication providers let you reuse existing authenticated connections from third-party platforms such as Composio or Pipedream.”
   • [probe] “official MCP server documented at https://docs.airweave.ai/mcp-server”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round drawn
   Letta✓fullprobed8/10

   Letta ships an official CLI ("Letta Code") with rich documentation covering interactive slash commands, headless/non-interactive scripting mode for CI/CD, local/self-hosted mode, and cloud sync — confirmed by first-party docs and a probe hitting the CLI docs page directly. Community evidence (HN threads with Letta employees) corroborates real usage of CLI features like --yolo mode and /init, indicating it's a genuine, actively used tool. Missing for 10: independent hands-on reviews specifically benchmarking the CLI's reliability/UX beyond employee-provided community threads, and no direct evidence of install/version metrics or broad third-party adoption data.

   • [claimed-docs] “Headless mode allows you to run Letta Code non-interactively, making it easy to integrate into scripts, CI/CD pipelines, or compose with oth…”
   • [claimed-docs] “Headless mode allows you to run Letta Code non-interactively, making it easy to integrate into scripts, CI/CD pipelines, or compose with oth…”
   • [claimed-docs] “This default local mode stores agent state on your machine and does not require a Letta login.”
   • [claimed-docs] “Control Letta Code's behavior during an interactive session with slash commands.”
   • [claimed-docs] “Run /login to back up your agents to the cloud and make them available through chat.letta.com, the desktop app, remote machines, and messagi…”
   • [probe] “official CLI documented at https://docs.letta.com/platform/cli”
   • [community] “Letta Code described by Letta's Charles as 'memory-first': agents build learned context over time via tools like /init and /remember; a /cle…”
   • [community] “User asks if Letta Code supports a 'yolo'/dangerous-skip-permissions mode like Claude Code; Letta's Charles confirms: 'Letta Code also has a…”
   • [community] “Letta employee describes Letta Code: 'a fundamentally different approach to coding agents with a focus on continual learning and statefulnes…”

   proof ↗⚑ flag

   Airweave✓fullprobed8/10

   Airweave documents an official CLI whose primary use case is searching any collection directly from the terminal, confirmed both in docs and via a dedicated CLI docs page probe. Missing for 10: independent/hands-on community verification of the CLI itself and more detail on its full command surface beyond search.

   • [claimed-docs] “The primary use case — search any collection from your terminal”
   • [probe] “official CLI documented at https://docs.airweave.ai/cli”

   proof ↗⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round drawn
   Letta✓fullprobed8/10

   Letta ships a fully documented Agent SDK (TypeScript, with browser/mobile variants) covering agent creation, sessions, streaming, permissions, MCP tool proxying, and an OpenAI-compatible App Server API, all backed by extensive first-party docs and a public GitHub SDK repo. This clearly satisfies driving the product programmatically as an AI-native user via a documented public API. missing for 10: a discoverable formal OpenAPI/swagger spec (probe found only 404s), and independent/hands-on developer corroboration of the SDK's public API stability.

   • [claimed-docs] “Create a stateful agent with `client.createAgent()`. It returns the agent's ID as a string, which you use to open sessions and manage the ag…”
   • [claimed-docs] “The stream yields typed events for the whole turn — reasoning, assistant text, tool calls, tool results”
   • [claimed-docs] “a **`canUseTool` callback** that approves, denies, or edits individual tool calls — interactively, if your application involves a human.”
   • [claimed-docs] “`resumeSession(id)` accepts either kind of ID: pass an `agent-xxx` ID to resume the agent's default conversation, or a `conv-xxx` ID to resu…”
   • [claimed-docs] “The stream yields typed events for the whole turn — reasoning, assistant text, tool calls, tool results — and terminates after the turn's `r…”
   • [claimed-docs] “The SDK supports local stdio processes, Streamable HTTP, and legacy SSE”
   • [claimed-docs] “MCP tools are discovered from servers supplied through `mcpServers` and proxied by the SDK host to the MCP server.”
   • [claimed-docs] “Send a message with `session.send()` and read the response with `session.stream()`. The stream yields typed events for the whole turn”
   • [claimed-docs] “use the App Server’s OpenAI-compatible API with clients such as Open WebUI, or the ACP adapter with ACP clients such as Zed”
   • [github] “the Letta Agent SDK for building agents into TypeScript applications”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.letta.com/openapi.json, https://docs.letta.com/swagger.json, https://docs.letta.com/api…”

   proof ↗⚑ flag

   Airweave✓fullprobed8/10

   Airweave exposes a documented OpenAPI spec (openapi.json), an llms.txt for AI-native consumption, a CLI, MCP server, and REST endpoints for collections/search/webhooks, all confirmed via probes and docs. missing for 10: independent hands-on validation of API completeness/stability and public API versioning/changelog details.

   • [probe] “PROBE openapi: HTTP 200 at https://docs.airweave.ai/openapi.json — contains "openapi" key”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.airweave.ai/llms.txt # Airweave ## Instructions for AI Agents - For clean Markdown of any page, a…”
   • [probe] “official MCP server documented at https://docs.airweave.ai/mcp-server”
   • [probe] “official CLI documented at https://docs.airweave.ai/cli”
   • [claimed-docs] “The primary use case — search any collection from your terminal”
   • [claimed-docs] “Webhooks are real-time notifications that Airweave sends when things happen in your organization: syncs completing, source connections being…”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Letta
   Letta~partialclaimed4/10

   Letta offers some related scoped-access mechanisms — Secrets that let an agent use API keys/tokens without ever seeing the raw values, GitHub integration where agents can only access repositories explicitly granted, and tool/action permission modes (unrestricted/acceptEdits/standard, canUseTool callback) — but there's no documented mechanism for issuing a distinct, scoped/least-privilege API credential specifically for an agent's own access to the Letta API or external services. missing for 10: explicit per-agent API key/credential issuance with configurable scopes, documentation of least-privilege credential lifecycle (rotation/revocation), and independent confirmation of scoped-credential behavior in practice.

   • [claimed-docs] “Secrets let your agent use sensitive values like API keys and tokens in shell commands without ever seeing the actual values.”
   • [claimed-docs] “Once connected, agents in your Letta org running on cloud computers will be able to clone, read, and push to the repositories you grant acce…”
   • [claimed-docs] “Press `Shift+Tab` in interactive mode to cycle through `unrestricted`, `acceptEdits`, and `standard`.”
   • [claimed-docs] “a **`canUseTool` callback** that approves, denies, or edits individual tool calls — interactively, if your application involves a human.”
   • [claimed-docs] “You can share agents across your team (and set permissions for access) to create custom agents for your organization”

   proof ↗⚑ flag

   Airweave—none0/10

   Evidence covers source connections, auth providers, direct token injection, and MCP/CLI access, but there is no mention of issuing scoped or least-privilege API keys/credentials specifically for agents. missing for 10: any documentation of scoped API key creation, permission/role-based credential issuance, or least-privilege agent access controls.

   ⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Letta
   Letta✓fullclaimed8/10

   Letta ships an official Agent SDK (letta-ai/letta on GitHub, TypeScript) with extensive first-party documentation covering agent creation, sessions, streaming, MCP tool integration, permissions/canUseTool callbacks, cloud/self-host deployment options, and demo apps for browser, Expo/React Native, and desktop clients - a substantial, well-documented SDK surface for AI-native builders. Missing for 10: independent hands-on developer reviews/benchmarks of the SDK itself, and evidence of official SDKs beyond TypeScript (e.g., Python).

   • [github] “the Letta Agent SDK for building agents into TypeScript applications”
   • [claimed-docs] “Create a stateful agent with `client.createAgent()`. It returns the agent's ID as a string, which you use to open sessions and manage the ag…”
   • [claimed-docs] “The stream yields typed events for the whole turn — reasoning, assistant text, tool calls, tool results”
   • [claimed-docs] “a **`canUseTool` callback** that approves, denies, or edits individual tool calls — interactively, if your application involves a human.”
   • [claimed-docs] “Browser, Expo, and React Native applications must import the SDK from `@letta-ai/letta-agent-sdk/client`”
   • [claimed-docs] “Use `backend: "cloud"` to host agents in Letta Cloud and run tools in managed cloud environments.”
   • [claimed-docs] “`resumeSession(id)` accepts either kind of ID: pass an `agent-xxx` ID to resume the agent's default conversation, or a `conv-xxx` ID to resu…”
   • [claimed-docs] “The SDK supports local stdio processes, Streamable HTTP, and legacy SSE”
   • [claimed-docs] “MCP tools are discovered from servers supplied through `mcpServers` and proxied by the SDK host to the MCP server.”
   • [claimed-docs] “Send a message with `session.send()` and read the response with `session.stream()`. The stream yields typed events for the whole turn”
   • [claimed-docs] “a complete Expo and React Native client for persistent Letta agents”

   proof ↗⚑ flag

   Airweave~partialprobed6/10

   Airweave exposes a documented OpenAPI spec (implying auto-generatable SDKs), an official LlamaIndex tool-spec package (llama-index-tools-airweave) giving agents direct API access, plus CLI and MCP server for agentic use, and integrations like Pipedream actions. However there is no explicit first-party Python/TypeScript SDK documentation beyond the LlamaIndex wrapper, so full 'build against official SDKs' coverage is unclear. missing for 10: dedicated language SDK docs (Python/JS/Go), independent developer confirmation of SDK usage beyond LlamaIndex.

   • [claimed-docs] “The llama-index-tools-airweave package provides an AirweaveToolSpec that gives your LlamaIndex agents access to Airweave's search capabiliti…”
   • [claimed-docs] “The Airweave integration provides a set of actions that enable you to search your synced data to retrieve relevant context, manage your coll…”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.airweave.ai/openapi.json — contains "openapi" key”
   • [probe] “official MCP server documented at https://docs.airweave.ai/mcp-server”
   • [probe] “official CLI documented at https://docs.airweave.ai/cli”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to Airweave
   Letta—none0/10

   The evidence pack covers agent SDK streaming, subagents, mods, scheduled tasks, and Slack/GitHub integrations, but there is no mention of a webhook subscription mechanism for events (e.g., agent state changes, task completion) that external systems could subscribe to. Streaming responses (letta-docs-43, letta-docs-60) are pull-based within an active session, not webhook push notifications.

   ⚑ flag

   Airweave✓fullclaimed8/10

   Airweave documents a dedicated webhooks system: real-time notifications pushed on events like sync completion, source connection creation, and collection updates, explicitly positioned as an alternative to polling. This directly matches the story of subscribing to events via webhooks. Missing for 10: independent/hands-on confirmation of webhook reliability and detail on signature verification/retry semantics.

   • [claimed-docs] “Webhooks are real-time notifications that Airweave sends when things happen in your organization: syncs completing, source connections being…”
   • [claimed-docs] “Instead of constantly polling the API, you register a webhook endpoint and Airweave pushes updates to you the moment they occur.”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Letta
   Letta~partialcommunity6/10

   Letta's 'dreaming' feature uses background subagents to review conversation history and consolidate learned lessons into memory without interrupting the user, and /doctor audits memory placement/duplication — both are forms of AI-generated insight derived from the agent's own interaction data. However, these are framed as internal memory-maintenance mechanisms rather than explicit user-facing 'suggestions' or dashboards surfacing insights about the user's data, and there is no independent/hands-on evidence of the quality of these generated insights. Missing for 10: user-facing insight/suggestion UI or reports, independent verification that dreaming produces useful proactive suggestions, and examples of insights derived from arbitrary connected data sources (not just conversation history).

   • [claimed-docs] “Dreaming uses background subagents to review recent conversations, consolidate useful lessons, and update memory without interrupting your a…”
   • [claimed-docs] “trigger controls when dreaming runs: after a number of steps, on context compaction, or never.”
   • [claimed-docs] “If the memory hierarchy has drifted or grown too large, run /doctor to audit placement, duplication, and system-prompt token usage.”
   • [claimed-docs] “You can also teach it explicitly with /remember: > /remember always use pnpm in this repo”
   • [community] “Letta Code described by Letta's Charles as 'memory-first': agents build learned context over time via tools like /init and /remember; a /cle…”
   • [claimed-docs] “For keyword search and optional semantic or hybrid search, install the [MemFS Search mod]”

   proof ↗⚑ flag

   Airweave—none0/10

   Airweave's documented capabilities center on search/retrieval — vector search, AI-agent tool-calling search, MCP server access — for AI agents to query synced data, not on Airweave itself surfacing proactive AI-generated insights or suggestions to the end user. No evidence shows an insights/suggestions feature or dashboard; missing for 10: any proactive insight-generation capability, any UI or output described as 'suggestions' rather than query-driven retrieval.

   • [claimed-docs] “An AI agent iteratively searches your data using tool calling. It searches with multiple strategies, reads full documents, navigates entity …”
   • [claimed-docs] “An AI agent iteratively searches your data using tool calling. It searches with multiple strategies, reads full documents, navigates entity …”
   • [claimed-docs] “Airweave lets AI agents search across company knowledge bases, cloud drives, databases, and SaaS tools in a single query.”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Letta
   Letta✓fullcommunity8/10

   Letta explicitly supports autonomous background automation: scheduled/recurring prompts via 'Scheduled tasks' (letta-docs-69), always-on cloud agents that keep running when your laptop is closed (letta-docs-55, letta-docs-68), Slack integration where mentioned agents respond using their own cloud computer (letta-docs-73, letta-docs-83), and background 'dreaming' subagents that consolidate memory without interrupting active work (letta-docs-27, letta-docs-3). Community posts corroborate the always-on, memory-first agent design (letta-comm-12, letta-comm-5). Missing for 10: independent hands-on verification that scheduled/background automations run reliably in practice, and more detail on failure handling/monitoring of unattended runs.

   • [claimed-docs] “Scheduled tasks allow you to automate prompts to your agent on a recurring schedule or at a specific time in the future.”
   • [claimed-docs] “Agents can still be messaged even if your laptop is closed, since they have their own computer to run on.”
   • [claimed-docs] “Agents can still be messaged even if your laptop is closed, since they have their own computer to run on. Combining agents with Slack and sc…”
   • [claimed-docs] “Agents connected to Slack are always-on: mention them in a channel or thread and they'll respond, using their cloud computer to do real work…”
   • [claimed-docs] “Agents connected to Slack are always-on: mention them in a channel or thread and they'll respond”
   • [claimed-docs] “Dreaming uses background subagents to review recent conversations, consolidate useful lessons, and update memory without interrupting your a…”
   • [claimed-docs] “trigger controls when dreaming runs: after a number of steps, on context compaction, or never.”
   • [community] “Letta employee describes Letta Code: 'a fundamentally different approach to coding agents with a focus on continual learning and statefulnes…”

   proof ↗⚑ flag

   Airweave~partialclaimed5/10

   Source connections automatically sync data in the background and webhooks push real-time updates instead of requiring polling, showing some autonomous background operation, but there's no evidence of a general-purpose automation/workflow engine (scheduled tasks, conditional triggers, multi-step actions) within Airweave itself—automation-style triggering is delegated to third-party tools like Pipedream. Missing for 10: native scheduling/trigger configuration UI, evidence of autonomous multi-step task execution, and independent confirmation that background syncs run reliably at scale.

   • [claimed-docs] “A source connection links a specific app or database to your collection. It handles authentication and automatically syncs data.”
   • [claimed-docs] “Webhooks are real-time notifications that Airweave sends when things happen in your organization: syncs completing, source connections being…”
   • [claimed-docs] “Instead of constantly polling the API, you register a webhook endpoint and Airweave pushes updates to you the moment they occur.”
   • [claimed-docs] “The Airweave integration provides a set of actions that enable you to search your synced data to retrieve relevant context, manage your coll…”

   proof ↗⚑ flag

3. ai-native userOperate the product with natural-language commands

   weight 2 · round drawn
   Letta✓fullcommunity8/10

   Letta Code and CLI are extensively controlled via natural-language chat plus slash commands (/remember, /init, /fork, /btw, /doctor, /agents) that wrap agent behavior in conversational form, and agents themselves interpret natural-language instructions to manage memory, tools, and subagents. missing for 10: independent hands-on evidence (beyond vendor docs/HN Q&A) confirming reliability of natural-language command interpretation across complex workflows.

   • [claimed-docs] “Control Letta Code's behavior during an interactive session with slash commands.”
   • [claimed-docs] “Run `/init` to bootstrap or refresh memory for the current project. The agent inspects the repository, asks about your working style when ne…”
   • [claimed-docs] “You can also teach it explicitly with `/remember`: `> /remember always use pnpm in this repo`. The agent decides where the lesson belongs an…”
   • [claimed-docs] “You can also teach it explicitly with /remember: > /remember always use pnpm in this repo”
   • [claimed-docs] “If the memory hierarchy has drifted or grown too large, run /doctor to audit placement, duplication, and system-prompt token usage.”
   • [claimed-docs] “Use /fork to branch the current conversation, including its in-context history. The new conversation can take a different direction without …”
   • [claimed-docs] “Use /btw for a side question. It forks the conversation in the background and returns the answer without interrupting your main task”
   • [community] “Letta Code described by Letta's Charles as 'memory-first': agents build learned context over time via tools like /init and /remember; a /cle…”
   • [community] “User asks if Letta Code supports a 'yolo'/dangerous-skip-permissions mode like Claude Code; Letta's Charles confirms: 'Letta Code also has a…”

   proof ↗⚑ flag

   Airweave✓fullprobed8/10

   Airweave supports natural-language operation via its MCP server, CLI, and AI-agent tool-calling search, letting agents in Cursor, Claude Code, etc. issue natural-language queries against synced data, and community feedback confirms it works well with Cursor. Missing for 10: independent hands-on verification of natural-language control beyond search/retrieval (e.g., managing connections or collections via NL) and broader third-party corroboration.

   • [claimed-docs] “An AI agent iteratively searches your data using tool calling. It searches with multiple strategies, reads full documents, navigates entity …”
   • [claimed-docs] “The Airweave MCP server implements the Model Context Protocol to let AI assistants search your synced data.”
   • [claimed-docs] “The primary use case — search any collection from your terminal”
   • [claimed-docs] “Airweave publishes official skills so that agents in Cursor, Claude Code, Gemini CLI, OpenCode, and other environments can set up integratio…”
   • [community] “Onyx co-founder: Congratulations on the launch. It looks like Airweave works well with Cursor, something we don't have nailed down yet!”
   • [probe] “official MCP server documented at https://docs.airweave.ai/mcp-server”
   • [probe] “official CLI documented at https://docs.airweave.ai/cli”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to Airweave
   Letta—none0/10

   The evidence pack shows extensive SDK documentation (agent-sdk pages) but no interactive API reference or runnable-example explorer; a direct probe for OpenAPI/Swagger endpoints returned 404 on all candidate paths, indicating no such interactive reference exists.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.letta.com/openapi.json, https://docs.letta.com/swagger.json, https://docs.letta.com/api…”

   proof ↗⚑ flag

   Airweave~partialprobed4/10

   Airweave publishes a machine-readable OpenAPI spec (probe-2) and doc pages exist for code samples (airweave-comm-5 mentions code samples on the docs site), suggesting some form of API reference, but there is no direct evidence of an interactive 'try it' console or actually runnable examples within the docs — the community note only complains about static code sample formatting, not interactivity. missing for 10: explicit documentation or screenshot of an interactive API console (e.g., Swagger/Redoc 'Try it' UI), evidence that examples can be executed in-browser, independent confirmation of runnable examples working.

   • [probe] “PROBE openapi: HTTP 200 at https://docs.airweave.ai/openapi.json — contains "openapi" key”
   • [community] “Code samples on the site have broken whitespace on mobile (Android/Brave) so look a bit intense. Also, the pricing is complex to reason abou…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round to Airweave
   Letta—none0/10

   Direct probes for OpenAPI/Swagger specs at all standard paths (docs.letta.com/openapi.json, swagger.json, api/openapi.json, .well-known/openapi.json) returned 404, and no documentation elsewhere in the evidence pack references a downloadable machine-readable API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.letta.com/openapi.json, https://docs.letta.com/swagger.json, https://docs.letta.com/api…”

   proof ↗⚑ flag

   Airweave✓fullprobed9/10

   Probe evidence confirms a machine-readable OpenAPI spec is directly downloadable at https://docs.airweave.ai/openapi.json returning HTTP 200 with an 'openapi' key, and the docs also expose an llms.txt for machine-readable navigation. Missing for 10: no independent third-party confirmation of the spec's completeness/versioning beyond the probe check.

   • [probe] “PROBE openapi: HTTP 200 at https://docs.airweave.ai/openapi.json — contains "openapi" key”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.airweave.ai/llms.txt # Airweave ## Instructions for AI Agents - For clean Markdown of any page, a…”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to Letta
   Letta~partialclaimed4/10

   Letta offers isolation-oriented options that could support sandbox-style testing: an --ephemeral CLI mode that runs one-shot tasks without persisting any agent, memory, or MemFS state (letta-docs-14), and a managed 'cloud sandbox' for running agents with no local setup (letta-docs-16, letta-docs-33, letta-docs-58). However, there is no explicit documentation of a staging/production environment separation or guarantee that testing won't touch production agent data. Missing for 10: explicit staging-vs-production environment concept, documentation of data isolation guarantees, and any evidence/testimonial confirming this workflow is used for safe testing.

   • [claimed-docs] “Use --ephemeral to run a one-shot task without creating, resuming, or persisting an agent, memory blocks, or MemFS”
   • [claimed-docs] “The desktop app and CLI can use your existing API keys and coding plans, while the web app runs agents in a cloud sandbox with no local setu…”
   • [claimed-docs] “The web app uses a managed cloud sandbox by default, so you can start without configuring a computer.”
   • [claimed-docs] “the web app runs agents in a cloud sandbox with no local setup”

   proof ↗⚑ flag

   Airweave—none0/10

   No evidence of a dedicated sandbox/test environment distinct from production data. Self-hosting (docs-11, docs-14) allows running a local instance, but this is not documented as a sandbox mode for safely testing against non-production data, and no staging/test-environment feature is mentioned anywhere in the evidence.

   ⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Letta—none0/10

   No evidence anywhere in the pack of API versioning schemes or a documented deprecation policy; the openapi.json probe even 404s, indicating no discoverable API spec that would carry version/deprecation info.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.letta.com/openapi.json, https://docs.letta.com/swagger.json, https://docs.letta.com/api…”

   proof ↗⚑ flag

   Airweave—none0/10

   There's evidence of an OpenAPI spec existing, but nothing about API versioning scheme, version history, or a documented deprecation policy. Missing for 10: versioning scheme documentation, deprecation policy, changelog/migration guides.

   • [probe] “PROBE openapi: HTTP 200 at https://docs.airweave.ai/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round drawn
   Letta~partialclaimed4/10

   Letta offers some multi-item automation primitives — subagents for parallel task delegation ('divide and conquer tasks') and a cross-agent `/search` command that queries across all agents at once — which support limited bulk-style operations, but there is no documented bulk API for batch-creating, editing, importing/exporting, or mass-updating agents, memory blocks, or files. Missing for 10: explicit bulk CRUD/batch APIs, bulk import/export tooling, and evidence of large-scale multi-item operations beyond parallel subagent delegation and cross-agent search.

   • [claimed-docs] “By delegating work to focused subagents, your main agent can keep its context window clean and make use of parallelism to divide and conquer…”
   • [claimed-docs] “Subagents are specialized agents that your main agent can spawn to handle complex tasks autonomously.”
   • [claimed-docs] “`/search [query]` | Search messages across agents”
   • [claimed-docs] “Up to 20 stateful agents”
   • [claimed-docs] “With a developer plan, you can create an unlimited number of agents but pay usage-based pricing.”

   proof ↗⚑ flag

   Airweave~partialclaimed4/10

   Airweave's core sync and search architecture inherently processes many items at once (source connections auto-sync entire datasets, collections span multiple sources, single queries search across large data sets), but there is no explicit documentation of a bulk API for batch creating/updating/deleting many items or connections in one call. Missing for 10: explicit bulk/batch API endpoints, evidence of bulk item management (not just sync), and any hands-on confirmation of bulk operation performance at scale.

   • [claimed-docs] “A collection is a group of different data sources that you can search using a single endpoint.”
   • [claimed-docs] “A source connection links a specific app or database to your collection. It handles authentication and automatically syncs data.”
   • [claimed-docs] “Airweave lets AI agents search across company knowledge bases, cloud drives, databases, and SaaS tools in a single query.”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Letta
   Letta~partialclaimed6/10

   Letta documents several trigger-based automation mechanisms: scheduled tasks that 'automate prompts to your agent on a recurring schedule or at a specific time' (letta-docs-69), mods that add 'event hooks' taking effect immediately (letta-docs-71), dreaming triggers configurable to fire 'after a number of steps, on context compaction, or never' (letta-docs-3/12), and Slack-connected agents that automatically respond when mentioned (letta-docs-73/83). These collectively show event- and time-based automatic action triggers, though there is no single documented general-purpose 'rules engine' where a user defines arbitrary event→action conditions in one place. Missing for 10: a unified rules/automation API or UI for arbitrary custom event conditions, and independent/hands-on confirmation that these triggers reliably fire as documented.

   • [claimed-docs] “Scheduled tasks allow you to automate prompts to your agent on a recurring schedule or at a specific time in the future.”
   • [claimed-docs] “Mods let your agent modify its own runtime — adding tools, commands, event hooks, permission policies, and provider adapters that take effec…”
   • [claimed-docs] “trigger controls when dreaming runs: after a number of steps, on context compaction, or never.”
   • [claimed-docs] “Agents connected to Slack are always-on: mention them in a channel or thread and they'll respond, using their cloud computer to do real work…”
   • [claimed-docs] “Agents connected to Slack are always-on: mention them in a channel or thread and they'll respond”
   • [claimed-docs] “trigger controls when dreaming runs: after a number of steps, on context compaction, or never”

   proof ↗⚑ flag

   Airweave~partialclaimed3/10

   Airweave offers webhooks that push real-time event notifications (sync completed, connection created, collection updated) rather than a true rule engine where users define conditional triggers that automatically execute actions inside the product; actual automation logic must be built externally (e.g., via Pipedream workflows) that consume these events. missing for 10: a native rule/trigger-condition builder, support for user-defined conditional logic, and evidence of actions being executed automatically by Airweave itself rather than just notifying external systems.

   • [claimed-docs] “Webhooks are real-time notifications that Airweave sends when things happen in your organization: syncs completing, source connections being…”
   • [claimed-docs] “Instead of constantly polling the API, you register a webhook endpoint and Airweave pushes updates to you the moment they occur.”
   • [claimed-docs] “The Airweave integration provides a set of actions that enable you to search your synced data to retrieve relevant context, manage your coll…”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to Airweave
   Letta—none0/10

   Evidence shows always-on hosting, headless/non-interactive CLI mode for CI/CD integration, and stateful agents resumable across sessions, but no documentation of a built-in scheduler, cron-like trigger, or recurring job/workflow feature.

   ⚑ flag

   Airweave~partialclaimed3/10

   Airweave's source connections 'automatically sync data' and it pushes webhook updates instead of polling, implying some recurring background sync exists, but there's no documented scheduling interface, cron-like controls, or ability to schedule arbitrary recurring jobs/workflows beyond source sync. Missing for 10: explicit scheduling/cron configuration options, user-defined recurring workflow triggers, and any evidence of customizable sync intervals.

   • [claimed-docs] “A source connection links a specific app or database to your collection. It handles authentication and automatically syncs data.”
   • [claimed-docs] “Webhooks are real-time notifications that Airweave sends when things happen in your organization: syncs completing, source connections being…”
   • [claimed-docs] “Instead of constantly polling the API, you register a webhook endpoint and Airweave pushes updates to you the moment they occur.”

   proof ↗⚑ flag

Forgetting

1. platform-engineerDelete a user's memories on demand — single memory, per-entity, or full erasure — to satisfy privacy requirements

   weight 2 · round drawn
   Letta—none0/10

   The evidence pack covers extensive memory creation, editing, auditing (/doctor), and consolidation (/remember, /init, dreaming) but never documents an explicit delete/erase memory command, API, or per-entity/full-wipe capability for privacy compliance. The one related command, /clear, explicitly 'resets the message buffer but keeps learned context' (letta-comm-5), meaning conversation clearing does not erase underlying memory — the opposite of the requested erasure guarantee.

   • [community] “Letta Code described by Letta's Charles as 'memory-first': agents build learned context over time via tools like /init and /remember; a /cle…”
   • [claimed-docs] “If the memory hierarchy has drifted or grown too large, run /doctor to audit placement, duplication, and system-prompt token usage.”
   • [claimed-docs] “You can also teach it explicitly with `/remember`: `> /remember always use pnpm in this repo`. The agent decides where the lesson belongs an…”

   proof ↗⚑ flag

   Airweave—none0/10

   No evidence of deletion capabilities for memories/entities/users — the pack covers syncing, search, MCP, CLI, webhooks, and connectors, but nothing about deleting or erasing synced data on demand. This is a fair capability for a data-sync/RAG platform to expose (e.g., for GDPR compliance) given it stores user data, so the axis applies, but no evidence supports it.

   ⚑ flag

2. developerMake memories expire or decay — via TTL, expiration dates, or recency weighting — so stale facts stop surfacing

   weight 2 · round drawn
   Letta—none0/10

   The evidence describes Letta's memory system (dreaming/consolidation, /doctor audits, MemFS search, shared memory) but nowhere documents TTL, expiration dates, or recency-weighted decay causing stale facts to stop surfacing; /doctor flags drift/duplication but is manual, not automatic decay.

   • [claimed-docs] “trigger controls when dreaming runs: after a number of steps, on context compaction, or never.”
   • [claimed-docs] “If the memory hierarchy has drifted or grown too large, run /doctor to audit placement, duplication, and system-prompt token usage.”
   • [claimed-docs] “Dreaming uses background subagents to review recent conversations, consolidate useful lessons, and update memory without interrupting your a…”
   • [claimed-docs] “For keyword search and optional semantic or hybrid search, install the MemFS Search mod”

   proof ↗⚑ flag

   Airweave—none0/10

   Airweave's docs cover data sync, search modes, MCP/CLI integrations, and connectors, but there is no mention of TTL, expiration dates, recency weighting, or any mechanism to decay or expire stale data/memories. Missing for 10: TTL/expiration configuration, recency-based scoring or decay, any lifecycle policy documentation.

   ⚑ flag

Portability

1. platform-engineerExport memories in a machine-readable format so the memory store is portable and not a lock-in trap

   weight 2 · round to Letta
   Letta~partialclaimed5/10

   Letta's memory is stored as plain Markdown files in a Git-backed 'memory repository' (MemFS), and self-hosting keeps all agent state on-device with no proprietary lock-in, which implies inherent portability of memory data. However, there is no explicit documented export/import command, no described export file format spec, or CLI subcommand dedicated to exporting memories for migration — the pack only shows cloud backup/sync features, not a data-portability workflow. missing for 10: an explicit export/import command or documented export format, third-party confirmation that memory can be extracted and reloaded elsewhere, guidance on migrating memory out of Letta Cloud.

   • [claimed-docs] “Pass memory for full control over the agent’s starting memory. Each entry becomes a Markdown file in the agent’s memory repository”
   • [claimed-docs] “Shared memory gives multiple agents access to the same files and working context. Each shared memory repository is a Git repository hosted i…”
   • [claimed-docs] “Letta agents can run entirely on infrastructure you control”
   • [claimed-docs] “all agent state, including messages, memory, and provider connections, stays on-device, and no Letta account is required.”
   • [claimed-docs] “Run /login to back up your agents to the cloud and make them available through chat.letta.com, the desktop app, remote machines, and messagi…”

   proof ↗⚑ flag

   Airweave—none0/10

   Evidence covers ingestion (source connections), search (vector/agentic), MCP server, CLI, webhooks, and self-hosting, but nothing describes an export mechanism or machine-readable dump of stored memories/collections for portability. Self-hosting (docker-compose) implies some data ownership but does not demonstrate an explicit export feature. missing for 10: documented export/dump endpoint or CLI command, evidence of a standard export format (e.g., JSON/CSV), any migration or data-portability guide.

   • [claimed-docs] “If you prefer to run Airweave yourself, you can deploy it locally on macOS, Linux or WSL.”
   • [claimed-docs] “git clone https://github.com/airweave-ai/airweave.git cd airweave ./start.sh”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.airweave.ai/openapi.json — contains "openapi" key”

   proof ↗⚑ flag

Self host

1. developerRun the memory layer fully locally — embedded in-process or against local models — without any cloud dependency

   weight 1 · round to Letta
   Letta~partialclaimed6/10

   Docs clearly describe a local-only mode where the CLI/agent state, memory, and provider connections all stay on-device with no Letta account or cloud backup required, and a self-hosted App Server that lets agents run entirely on infrastructure you control. However, the evidence never confirms running against fully local models (e.g., local LLM inference/embeddings) — 'model-agnostic' language points to swapping API-based providers (Claude, GPT, Gemini) rather than in-process/local-model operation, and other docs emphasize cloud sandboxes and server-hosted agents as the default path. Missing for 10: explicit support/documentation for local model backends (e.g., Ollama/local embeddings), and confirmation that memory/embedding search (MemFS Search) works without any external API calls.

   • [claimed-docs] “This default local mode stores agent state on your machine and does not require a Letta login.”
   • [claimed-docs] “all agent state, including messages, memory, and provider connections, stays on-device, and no Letta account is required.”
   • [claimed-docs] “Letta agents can run entirely on infrastructure you control”
   • [claimed-docs] “Self-hosted App Server: Run the Letta App Server to host local agents on a central, always-on machine and expose them to client applications…”
   • [claimed-docs] “Letta agents are **model-agnostic**. Agents can use Claude, GPT, Gemini, or other supported models. Users can change an agent's underlying m…”
   • [claimed-docs] “For keyword search and optional semantic or hybrid search, install the [MemFS Search mod]”

   proof ↗⚑ flag

   Airweave~partialclaimed4/10

   Airweave documents self-hosting via docker-compose (`./start.sh`) on macOS/Linux/WSL, showing a local deployment path, but there is no evidence it can run embedded in-process (as a library) or configured against local embedding/LLM models to avoid all cloud dependency — the docs describe it as a service with source connectors, vector DB, and search API rather than an embeddable local-only memory layer. missing for 10: evidence of in-process/embedded mode, evidence of local-model (non-cloud) embedding/LLM configuration, confirmation no external API calls are required once self-hosted.

   • [claimed-docs] “git clone https://github.com/airweave-ai/airweave.git cd airweave ./start.sh”
   • [claimed-docs] “If you prefer to run Airweave yourself, you can deploy it locally on macOS, Linux or WSL.”

   proof ↗⚑ flag

2. platform-engineerSelf-host the memory layer from open-source code (e.g. via Docker) on infrastructure I control

   weight 3 · round to Airweave
   Letta~partialprobed6/10

   Letta explicitly documents a self-hosting path: 'Letta agents can run entirely on infrastructure you control' via the self-hosted App Server, with a local mode that stores state on-device and requires no cloud account, and the agent harness is described as fully open source. However, the evidence pack contains no explicit Docker instructions, container image, or hands-on/community confirmation that self-hosting works in practice. Missing for 10: Docker/container deployment specifics, independent verification of the self-host setup succeeding.

   • [claimed-docs] “Letta agents can run entirely on infrastructure you control”
   • [claimed-docs] “Self-hosted App Server: Run the Letta App Server to host local agents on a central, always-on machine and expose them to client applications…”
   • [claimed-docs] “The Letta App Server lets you deploy the Letta agent harness as a service.”
   • [claimed-docs] “Run the Letta App Server to host local agents on a central, always-on machine and expose them to client applications”
   • [claimed-docs] “all agent state, including messages, memory, and provider connections, stays on-device, and no Letta account is required.”
   • [claimed-docs] “This default local mode stores agent state on your machine and does not require a Letta login.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.letta.com/llms.txt # Letta > Letta agents learn from experience and improve with use. The Letta ag…”

   proof ↗⚑ flag

   Airweave✓fullclaimed8/10

   Docs explicitly provide a git clone + ./start.sh workflow for local self-hosted deployment on macOS/Linux/WSL, indicating Docker-based open-source self-hosting is supported. Missing for 10: explicit confirmation of production-grade/cloud self-host guidance (beyond local dev) and independent hands-on verification of the self-hosted deployment succeeding.

   • [claimed-docs] “git clone https://github.com/airweave-ai/airweave.git cd airweave ./start.sh”
   • [claimed-docs] “If you prefer to run Airweave yourself, you can deploy it locally on macOS, Linux or WSL.”

   proof ↗⚑ flag

Knowledge graph

1. ml-engineerStore memories as a knowledge graph of entities and relationships so multi-hop and entity-centric questions are answerable

   weight 3 · round drawn
   Letta—none0/10

   Letta's documented memory system is file/text-based (MemFS, memory blocks) with optional keyword/semantic/hybrid search (letta-docs-28, letta-docs-41), not a graph of entities and relationships; a Letta employee explicitly frames its approach as 'primarily text/files based' as an alternative to structured memory graphs (letta-comm-10). No evidence describes entity/relationship modeling or multi-hop graph traversal for memory.

   • [claimed-docs] “For keyword search and optional semantic or hybrid search, install the [MemFS Search mod]”
   • [claimed-docs] “For keyword search and optional semantic or hybrid search, install the MemFS Search mod”
   • [community] “Letta's Wooders responds to memory skepticism: 'the problem with ChatGPT / other RAG-based memory solutions is that it's not possible to col…”

   proof ↗⚑ flag

   Airweave—none0/10

   Airweave's docs describe vector search and an agent that can 'navigate entity hierarchies (parent/child/sibling)', but this is document/entity hierarchy navigation within a RAG pipeline, not a knowledge graph of entities and relationships designed for multi-hop, entity-centric reasoning. There is no mention of a graph database, relationship modeling, or multi-hop query capability.

   • [claimed-docs] “An AI agent iteratively searches your data using tool calling. It searches with multiple strategies, reads full documents, navigates entity …”
   • [claimed-docs] “An AI agent iteratively searches your data using tool calling. It searches with multiple strategies, reads full documents, navigates entity …”
   • [claimed-docs] “Direct vector search. Use when speed is critical (~0.5sec).”

   proof ↗⚑ flag

2. ml-engineerTrack when facts became valid or invalid (temporal reasoning) so the memory distinguishes current from outdated information

   weight 2 · round drawn
   Letta—none0/10

   Letta's documented memory model is file/block-based (MemFS, memory blocks, dreaming/consolidation) with no evidence of tracking fact validity intervals, timestamps of when facts became true/false, or any temporal-graph reasoning distinguishing current vs outdated facts. The axis is applicable to a memory-focused product, but nothing in the evidence pack shows Letta supports temporal fact versioning.

   ⚑ flag

   Airweave—none0/10

   No evidence Airweave tracks fact validity intervals or temporal versioning of entities; docs describe sync, search strategies, and entity hierarchy navigation but nothing about time-bound validity or invalidation of facts. Missing for 10: any mention of temporal metadata, valid/invalid time tracking, or versioned fact history.

   ⚑ flag

Schema customization

1. ml-engineerCustomize the memory schema — entity types, edge types, or ontology — to match my domain

   weight 1 · round drawn
   Letta—none0/10

   Letta's documented memory model is block/file-based (Markdown memory blocks, MemFS, persona/human blocks) rather than a graph model with configurable entity types, edge types, or ontology; no evidence pack item describes schema customization of entities/relationships. missing for 10: any documentation of graph-based memory representation, entity/edge type definitions, or ontology configuration APIs.

   • [claimed-docs] “Pass memory for full control over the agent’s starting memory. Each entry becomes a Markdown file in the agent’s memory repository”
   • [claimed-docs] “`persona` and `human` are conveniences that set the agent's persona and human memory”
   • [claimed-docs] “For keyword search and optional semantic or hybrid search, install the [MemFS Search mod]”
   • [claimed-docs] “For keyword search and optional semantic or hybrid search, install the MemFS Search mod”

   proof ↗⚑ flag

   Airweave—none0/10

   Airweave's evidence describes collections, source connections, vector/agentic search, MCP, CLI, and webhooks, but nothing addresses customizing entity types, edge types, or an ontology/schema for a graph-entity memory model — Airweave appears to use a fixed sync/search architecture rather than an editable knowledge-graph schema. Missing for 10: any mention of entity/edge type definitions, schema customization API, or ontology configuration.

   • [claimed-docs] “A collection is a group of different data sources that you can search using a single endpoint.”
   • [claimed-docs] “A source connection links a specific app or database to your collection. It handles authentication and automatically syncs data.”
   • [claimed-docs] “An AI agent iteratively searches your data using tool calling. It searches with multiple strategies, reads full documents, navigates entity …”

   proof ↗⚑ flag

Agent memory

1. ai-native userMy agent can manage its own memory mid-conversation — adding, searching, updating, and deleting memories through tools or API calls it invokes itself

   weight 3 · round to Letta
   Letta✓fullcommunity8/10

   Letta's memory system is explicitly designed for agent-driven self-editing: agents can be taught new memories via /remember, search via MemFS keyword/semantic search mods, consolidate/update via background 'dreaming', and audit/prune via /doctor — all invoked by the agent itself mid-conversation, and community evidence corroborates this as Letta's core differentiator ('memory-first', 'fully white box' memory editing). missing for 10: no direct API/tool-call schema example showing explicit add/search/update/delete operations invoked programmatically by the agent (docs describe user-facing slash commands and background dreaming rather than a fully enumerated CRUD tool API), and no independent hands-on test confirming the agent autonomously invokes these without user prompting.

   • [claimed-docs] “You can also teach it explicitly with /remember: > /remember always use pnpm in this repo”
   • [claimed-docs] “You can also teach it explicitly with `/remember`”
   • [claimed-docs] “You can also teach it explicitly with /remember”
   • [claimed-docs] “If the memory hierarchy has drifted or grown too large, run /doctor to audit placement, duplication, and system-prompt token usage.”
   • [claimed-docs] “Dreaming uses background subagents to review recent conversations, consolidate useful lessons, and update memory without interrupting your a…”
   • [claimed-docs] “For keyword search and optional semantic or hybrid search, install the [MemFS Search mod]”
   • [claimed-docs] “For keyword search and optional semantic or hybrid search, install the MemFS Search mod”
   • [community] “Letta Code described by Letta's Charles as 'memory-first': agents build learned context over time via tools like /init and /remember; a /cle…”
   • [community] “Letta's Wooders responds to memory skepticism: 'the problem with ChatGPT / other RAG-based memory solutions is that it's not possible to col…”
   • [community] “Concern raised: 'context poisoning is a real problem that these memory providers only make worse.' Letta's Charles countered that Letta's me…”

   proof ↗⚑ flag

   Airweave—none0/10

   Airweave's documented capability is agentic *search* over synced external data sources (docs-4, docs-5, docs-17) and syncing/connecting data, not an agent-writable memory store. There is no evidence of an agent invoking add/update/delete operations on memories mid-conversation — data flows in via source connections/syncs, not via agent tool calls for memory CRUD.

   • [claimed-docs] “An AI agent iteratively searches your data using tool calling. It searches with multiple strategies, reads full documents, navigates entity …”
   • [claimed-docs] “The Airweave MCP server implements the Model Context Protocol to let AI assistants search your synced data.”
   • [claimed-docs] “A source connection links a specific app or database to your collection. It handles authentication and automatically syncs data.”
   • [claimed-docs] “Webhooks are real-time notifications that Airweave sends when things happen in your organization: syncs completing, source connections being…”

   proof ↗⚑ flag

Benchmarks

1. ml-engineerSee published memory-quality benchmark results (e.g. LongMemEval, LoCoMo) backing the product's recall-accuracy claims

   weight 2 · round drawn
   Letta—none0/10

   The evidence pack contains extensive documentation of Letta's memory architecture (MemFS, dreaming, shared memory, etc.) and community discussion of memory quality skepticism/responses, but nowhere cites any published benchmark results (LongMemEval, LoCoMo, or similar) backing recall-accuracy claims. Since memory-recall quality is a core claimed feature of Letta, this axis clearly applies, but no benchmark evidence exists in the pack.

   • [community] “'How does the memory scale (or not!) over time... if there is a memory block limit, is that an issue for self learning over time. Claude as …”
   • [community] “Skeptic comment: 'In my experience, memory is really not that helpful in most cases... Maintaining the memory is a considerable burden... Ch…”
   • [community] “Letta's Wooders responds to memory skepticism: 'the problem with ChatGPT / other RAG-based memory solutions is that it's not possible to col…”
   • [community] “Concern raised: 'context poisoning is a real problem that these memory providers only make worse.' Letta's Charles countered that Letta's me…”
   • [claimed-docs] “Dreaming uses background subagents to review recent conversations, consolidate useful lessons, and update memory without interrupting your a…”
   • [claimed-docs] “For keyword search and optional semantic or hybrid search, install the [MemFS Search mod]”

   proof ↗⚑ flag

   Airweave—none0/10

   No published benchmark results (e.g. LongMemEval, LoCoMo) or quantitative recall-accuracy metrics appear anywhere in the evidence; only a single anecdotal HN comment claims superior 'retrieval accuracy' with no data. missing for 10: published benchmark suite results, comparison methodology, any quantitative recall/accuracy numbers.

   • [community] “Had meetings with a ton of MCP-server providers, no one came close to Airweave’s retrieval accuracy. I even tried Zapier and similar large c…”

   proof ↗⚑ flag

Core memory

1. developerAdd memories from conversations and retrieve them later with semantic search, so context persists across sessions

   weight 3 · round to Letta
   Letta~partialcommunity6/10

   Letta clearly supports persistent memory across sessions (MemFS, /remember, stateful agents resumable across sessions/computers) and explicitly documents semantic search as an optional add-on via the 'MemFS Search mod' for keyword/semantic/hybrid search rather than a built-in default. Community commentary confirms the memory system is real and text/file-based but transparency-focused, not natively semantic-first, and some users raise unresolved concerns about memory scaling/self-improvement. missing for 10: first-party evidence that semantic search is enabled by default (not an optional mod), independent hands-on benchmarking of recall/retrieval quality, and clearer documentation of retrieval accuracy at scale.

   • [claimed-docs] “You can return to the same agent across sessions, computers, and interfaces instead of starting from scratch each time.”
   • [claimed-docs] “You can also teach it explicitly with `/remember`: `> /remember always use pnpm in this repo`. The agent decides where the lesson belongs an…”
   • [claimed-docs] “For keyword search and optional semantic or hybrid search, install the [MemFS Search mod]”
   • [claimed-docs] “For keyword search and optional semantic or hybrid search, install the MemFS Search mod”
   • [community] “Letta Code described by Letta's Charles as 'memory-first': agents build learned context over time via tools like /init and /remember; a /cle…”
   • [community] “Letta's Wooders responds to memory skepticism: 'the problem with ChatGPT / other RAG-based memory solutions is that it's not possible to col…”
   • [community] “'How does the memory scale (or not!) over time... if there is a memory block limit, is that an issue for self learning over time. Claude as …”

   proof ↗⚑ flag

   Airweave—none0/10

   Airweave's documented model is syncing external data sources (Slack, GitHub, Drive, databases) into collections and then searching them via vector/agentic search, not an explicit API for adding conversational memories and retrieving them for session persistence. None of the evidence describes a 'store this conversation turn' or memory-write primitive, or session-context persistence semantics — missing for 10: an add-memory/write API for conversational turns, evidence of session-scoped recall, and any first-party or community confirmation of using Airweave as a conversation memory layer.

   • [claimed-docs] “A collection is a group of different data sources that you can search using a single endpoint.”
   • [claimed-docs] “Direct vector search. Use when speed is critical (~0.5sec).”
   • [claimed-docs] “An AI agent iteratively searches your data using tool calling. It searches with multiple strategies, reads full documents, navigates entity …”
   • [claimed-docs] “Airweave lets AI agents search across company knowledge bases, cloud drives, databases, and SaaS tools in a single query.”

   proof ↗⚑ flag

2. developerRely on the memory layer to update, supersede, or merge memories when new information contradicts what was stored

   weight 2 · round to Letta
   Letta~partialcommunity6/10

   Docs describe mechanisms that plausibly support updating/merging memory — /remember lets the agent 'decide where the lesson belongs and commit the update to MemFS' (letta-docs-66), 'dreaming' subagents 'consolidate useful lessons and update memory' (letta-docs-27), and /doctor audits for 'duplication' and drift in the memory hierarchy (letta-docs-10) — and Letta staff claim memory is transparent/controllable and addresses context-poisoning concerns (letta-comm-10, letta-comm-11). However, none of this is a concrete demonstration of contradiction detection/supersession logic, and a community skeptic raises unresolved doubts about memory scaling and self-correction (letta-comm-8, letta-comm-9) without a hands-on refutation either way. Missing for 10: explicit documentation or example of the system detecting/resolving conflicting facts, independent hands-on verification that stale memories are actually superseded rather than just appended/deduplicated.

   • [claimed-docs] “You can also teach it explicitly with `/remember`: `> /remember always use pnpm in this repo`. The agent decides where the lesson belongs an…”
   • [claimed-docs] “Dreaming uses background subagents to review recent conversations, consolidate useful lessons, and update memory without interrupting your a…”
   • [claimed-docs] “If the memory hierarchy has drifted or grown too large, run /doctor to audit placement, duplication, and system-prompt token usage.”
   • [community] “Letta's Wooders responds to memory skepticism: 'the problem with ChatGPT / other RAG-based memory solutions is that it's not possible to col…”
   • [community] “Concern raised: 'context poisoning is a real problem that these memory providers only make worse.' Letta's Charles countered that Letta's me…”
   • [community] “'How does the memory scale (or not!) over time... if there is a memory block limit, is that an issue for self learning over time. Claude as …”
   • [community] “Skeptic comment: 'In my experience, memory is really not that helpful in most cases... Maintaining the memory is a considerable burden... Ch…”

   proof ↗⚑ flag

   Airweave—none0/10

   Airweave is a data-sync/search platform that indexes and syncs source data via connectors and search endpoints; the evidence describes syncing, webhooks, and search strategies but contains no mention of a memory layer that detects contradictions, supersedes, or merges conflicting stored facts. This is an applicable axis for a retrieval/knowledge system, but no evidence shows such conflict-resolution or memory-update logic exists.

   • [claimed-docs] “A source connection links a specific app or database to your collection. It handles authentication and automatically syncs data.”
   • [claimed-docs] “Webhooks are real-time notifications that Airweave sends when things happen in your organization: syncs completing, source connections being…”
   • [claimed-docs] “Instead of constantly polling the API, you register a webhook endpoint and Airweave pushes updates to you the moment they occur.”

   proof ↗⚑ flag

Retrieval controls

1. developerSteer retrieval with metadata filters, keyword/hybrid search modes, or reranking instead of accepting a single fixed similarity search

   weight 2 · round drawn
   Letta~partialclaimed4/10

   Letta docs mention that installing the 'MemFS Search mod' enables keyword search and optional semantic or hybrid search, showing some retrieval-mode flexibility beyond fixed similarity search, but this requires an add-on rather than being built-in. Missing for 10: explicit metadata-filter support, reranking capability, and any evidence this mod is core/first-class rather than an optional plugin.

   • [claimed-docs] “For keyword search and optional semantic or hybrid search, install the [MemFS Search mod]”
   • [claimed-docs] “For keyword search and optional semantic or hybrid search, install the MemFS Search mod”

   proof ↗⚑ flag

   Airweave~partialclaimed4/10

   Airweave documents two retrieval modes—fast direct vector search and an agentic iterative search that reads full documents and navigates entity hierarchies—giving developers some steering beyond a single fixed similarity search, but there is no explicit documentation of metadata filters, keyword/hybrid search, or a reranking step. missing for 10: metadata filter parameters, keyword/hybrid search mode, explicit reranking mechanism, independent verification of these controls.

   • [claimed-docs] “Direct vector search. Use when speed is critical (~0.5sec).”
   • [claimed-docs] “An AI agent iteratively searches your data using tool calling. It searches with multiple strategies, reads full documents, navigates entity …”
   • [claimed-docs] “An AI agent iteratively searches your data using tool calling. It searches with multiple strategies, reads full documents, navigates entity …”
   • [claimed-docs] “Direct vector search. Use when speed is critical (\~0.5sec).”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Airweave
   Letta~partialprobed5/10

   Letta's SDK/App Server exposes agent creation, memory, and OpenAI-compatible API access (letta-docs-1, letta-docs-23, letta-docs-32), suggesting an API-first architecture, but the evidence never confirms that CLI/UI-specific features like /doctor memory audits, /pin, /fork, /btw, or /agents browsing have API equivalents, and a direct probe for a public OpenAPI spec returned 404s across all candidate paths (letta-probe-2), undermining a clean 'everything via API' claim. missing for 10: explicit API endpoints/SDK methods mirroring each UI/CLI convenience command, a discoverable OpenAPI spec confirming full surface parity, and independent confirmation of parity.

   • [claimed-docs] “create an agent once, then resume it from anywhere”
   • [claimed-docs] “use the App Server’s OpenAI-compatible API with clients such as Open WebUI, or the ACP adapter with ACP clients such as Zed”
   • [claimed-docs] “The Letta App Server lets you deploy the Letta agent harness as a service.”
   • [claimed-docs] “Run the Letta App Server to host local agents on a central, always-on machine and expose them to client applications”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.letta.com/openapi.json, https://docs.letta.com/swagger.json, https://docs.letta.com/api…”
   • [claimed-docs] “Use /fork to branch the current conversation, including its in-context history.”
   • [claimed-docs] “If the memory hierarchy has drifted or grown too large, run /doctor to audit placement, duplication, and system-prompt token usage.”
   • [claimed-docs] “Use /agents in the CLI to browse and switch agents. Pin an agent with /pin or the favorite control in the desktop app”

   proof ↗⚑ flag

   Airweave~partialprobed6/10

   Airweave's docs describe collections, source connections, search, and sync management as API/CLI-first concepts, and an OpenAPI spec plus CLI and MCP server are documented, implying most functionality is API-accessible. However, no evidence explicitly confirms full parity between UI and API (e.g., whether every dashboard action like billing, org settings, or Airweave Connect widget configuration is also API-exposed). Missing for 10: an explicit parity statement or audit showing all UI features are API-reachable, and independent confirmation from users exercising the API directly.

   • [probe] “PROBE openapi: HTTP 200 at https://docs.airweave.ai/openapi.json — contains "openapi" key”
   • [probe] “official CLI documented at https://docs.airweave.ai/cli”
   • [claimed-docs] “A collection is a group of different data sources that you can search using a single endpoint.”
   • [claimed-docs] “A source connection links a specific app or database to your collection. It handles authentication and automatically syncs data.”
   • [claimed-docs] “The primary use case — search any collection from your terminal”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Letta
   Letta~partialcommunity5/10

   Letta's architecture strongly favors openness: memory is stored as plain Markdown/MemFS files (letta-docs-11, letta-docs-66), shared memory is a Git repository (letta-docs-21, letta-docs-29), and self-hosting keeps 'all agent state... on-device' with no cloud account required (letta-docs-74, letta-docs-30), reinforced by community claims of a 'fully white box' text-based memory system (letta-comm-10, letta-comm-11). However, there is no explicit documented 'export my data and delete my account' feature or guarantee that cloud-hosted shared-memory git repos can be freely cloned/exported by the user. Missing for 10: an explicit data-export/account-deletion workflow, documentation on extracting cloud-hosted agent state, and independent verification that self-hosted mode fully replaces all cloud-only features.

   • [claimed-docs] “Pass memory for full control over the agent’s starting memory. Each entry becomes a Markdown file in the agent’s memory repository”
   • [claimed-docs] “Shared memory gives multiple agents access to the same files and working context. Each shared memory repository is a Git repository hosted i…”
   • [claimed-docs] “Shared memory gives multiple agents access to the same files and working context.”
   • [claimed-docs] “Letta agents can run entirely on infrastructure you control”
   • [claimed-docs] “all agent state, including messages, memory, and provider connections, stays on-device, and no Letta account is required.”
   • [community] “Letta's Wooders responds to memory skepticism: 'the problem with ChatGPT / other RAG-based memory solutions is that it's not possible to col…”
   • [community] “Concern raised: 'context poisoning is a real problem that these memory providers only make worse.' Letta's Charles countered that Letta's me…”

   proof ↗⚑ flag

   Airweave~partialprobed4/10

   Airweave is open-source and self-hostable (git clone, ./start.sh) and exposes a documented OpenAPI/CLI surface, giving some data portability and avoiding lock-in, but there is no explicit documented bulk-export feature or open-format export tooling for a user's synced data. missing for 10: explicit data export/backup feature, documented open export formats, evidence of a 'leave and take your data' workflow.

   • [claimed-docs] “git clone https://github.com/airweave-ai/airweave.git cd airweave ./start.sh”
   • [claimed-docs] “If you prefer to run Airweave yourself, you can deploy it locally on macOS, Linux or WSL.”
   • [probe] “PROBE openapi: HTTP 200 at https://docs.airweave.ai/openapi.json — contains "openapi" key”
   • [probe] “official CLI documented at https://docs.airweave.ai/cli”

   proof ↗⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round to Letta
   Letta~partialprobed6/10

   Letta's own docs state the agent harness is 'fully open source' and link to a public GitHub repo (letta-ai/letta) for the Agent SDK, giving concrete evidence of source availability. However, the evidence pack never names the actual license (e.g., Apache/MIT) or confirms the full product (App Server, CLI, memory subsystems) is under that same open license rather than just the harness. Missing for 10: explicit license identification/file, confirmation that all core components (not just the agent harness) are open-sourced, and independent corroboration of license terms.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.letta.com/llms.txt # Letta > Letta agents learn from experience and improve with use. The Letta ag…”
   • [github] “the Letta Agent SDK for building agents into TypeScript applications”
   • [claimed-docs] “Letta agents can run entirely on infrastructure you control”

   proof ↗⚑ flag

   Airweave~partialclaimed5/10

   The docs show a public GitHub repo (airweave-ai/airweave) that can be cloned and self-hosted (airweave-docs-11, airweave-docs-14), implying the source is publicly readable, but no evidence specifies an actual open-source license (e.g., MIT/Apache) or license file. Missing for 10: explicit license declaration, confirmation of license terms, and independent corroboration that the repo is fully open (not just source-available for self-hosting).

   • [claimed-docs] “git clone https://github.com/airweave-ai/airweave.git cd airweave ./start.sh”
   • [claimed-docs] “If you prefer to run Airweave yourself, you can deploy it locally on macOS, Linux or WSL.”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round drawn
   Letta✓fullclaimed8/10

   Letta's docs explicitly describe self-hosting the core product: running the Letta App Server on infrastructure you control, local CLI mode that stores state on-device without requiring a Letta account, and running agents entirely on infra you control (letta-docs-2, letta-docs-15, letta-docs-30, letta-docs-31, letta-docs-74). This is first-party documentation of a genuine self-host mode, not just cloud-hosted convenience. missing for 10: independent/hands-on verification that self-hosted deployment works as documented, and more detail on infra/ops requirements for self-hosting at scale.

   • [claimed-docs] “Run the Letta App Server to host local agents on a central, always-on machine and expose them to client applications through the Agent SDK”
   • [claimed-docs] “Self-hosted App Server: Run the Letta App Server to host local agents on a central, always-on machine and expose them to client applications…”
   • [claimed-docs] “Letta agents can run entirely on infrastructure you control”
   • [claimed-docs] “This default local mode stores agent state on your machine and does not require a Letta login.”
   • [claimed-docs] “all agent state, including messages, memory, and provider connections, stays on-device, and no Letta account is required.”
   • [claimed-docs] “Run the Letta App Server to host local agents on a central, always-on machine and expose them to client applications”

   proof ↗⚑ flag

   Airweave✓fullclaimed8/10

   Docs explicitly provide a self-host path via git clone and ./start.sh, and note it can run on macOS, Linux, or WSL, confirming the core product can be self-hosted rather than only used as SaaS. Missing for 10: independent hands-on report of a successful self-hosted deployment and more detail on production-grade self-host configuration/scaling.

   • [claimed-docs] “git clone https://github.com/airweave-ai/airweave.git cd airweave ./start.sh”
   • [claimed-docs] “If you prefer to run Airweave yourself, you can deploy it locally on macOS, Linux or WSL.”

   proof ↗⚑ flag

Pricing

1. platform-engineerSee published pricing with a free tier and per-unit rates so I can project memory costs before committing

   weight 2 · round to Letta
   Letta~partialclaimed5/10

   Letta's docs confirm a published pricing page with a free BYOK tier (letta-docs-56), a capped free stateful-agent tier (letta-docs-36) and a usage-based developer plan (letta-docs-49), which addresses the free-tier and general cost-model part of the story. However, no explicit per-unit rate table (e.g., $/agent-hour, $/GB memory, $/token) is shown in the evidence, so a platform engineer cannot precisely project memory costs. Missing for 10: concrete per-unit pricing figures/rate card, and independent confirmation of actual billing granularity for memory usage.

   • [claimed-docs] “Up to 20 stateful agents”
   • [claimed-docs] “With a developer plan, you can create an unlimited number of agents but pay usage-based pricing.”
   • [claimed-docs] “You can get started with Letta for free by using models with BYOK, including coding plans from ChatGPT/Codex, Kimi, and Z.AI.”
   • [claimed-docs] “You can share agents across your team (and set permissions for access) to create custom agents for your organization”

   proof ↗⚑ flag

   Airweave—none0/10

   No evidence pack item documents a published pricing page, free tier, or per-unit rates; the only pricing-related mentions are community complaints that pricing is 'complex to reason about' and 'prohibitive,' with a direct ask for usage-based per-unit pricing that goes unanswered, indicating no clear published rate structure exists for cost projection.

   • [community] “Code samples on the site have broken whitespace on mobile (Android/Brave) so look a bit intense. Also, the pricing is complex to reason abou…”
   • [community] “Your pricing currently seems prohibitive for that kind of use case. Shouldn't it be usage-based so one can build a product where users can c…”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round to Letta
   Letta~partialclaimed4/10

   Letta offers self-hosting where 'agents can run entirely on infrastructure you control' and local mode where 'all agent state ... stays on-device' (letta-docs-30, letta-docs-74), giving users a way to control where data physically lives. However, there is no documented region/residency selection feature for the managed Letta Cloud offering itself (e.g., choosing EU vs US data centers). Missing for 10: explicit cloud region/residency picker, compliance certifications (GDPR/data-locality), and any documentation of where Letta Cloud stores data by default.

   • [claimed-docs] “Letta agents can run entirely on infrastructure you control”
   • [claimed-docs] “all agent state, including messages, memory, and provider connections, stays on-device, and no Letta account is required.”
   • [claimed-docs] “Self-hosted App Server: Run the Letta App Server to host local agents on a central, always-on machine and expose them to client applications…”
   • [claimed-docs] “This default local mode stores agent state on your machine and does not require a Letta login.”

   proof ↗⚑ flag

   Airweave—none0/10

   There is no mention anywhere in the evidence pack of data residency, region selection, or self-hosting for compliance/geographic control (the self-host option is framed as a deployment preference, not a residency feature). Missing for 10: any documentation of region choice, data residency guarantees, or compliance-driven storage location controls.

   ⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Letta—none0/10

   No evidence pack item addresses data-training opt-out, a training-data policy, or any privacy controls preventing use of user data for model training; self-hosting is mentioned but not tied to a training-data guarantee.

   ⚑ flag

   Airweave—none0/10

   No evidence in the pack addresses AI-model training data usage policies, opt-out mechanisms, or data-retention/training guarantees for Airweave; the docs focus on data syncing, search, and integrations but never mention training-data controls.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Letta
   Letta~partialclaimed5/10

   Letta gives users some retention control: local mode stores state on-device without a cloud login (letta-docs-31), self-hosting keeps 'all agent state, including messages, memory, and provider connections... on-device, and no Letta account is required' (letta-docs-74, letta-docs-30), and --ephemeral mode runs a one-shot task 'without creating, resuming, or persisting an agent, memory blocks, or MemFS' (letta-docs-14). However, there is no documented explicit 'delete agent/data' command, data-retention policy for Letta Cloud, or export/erase workflow. Missing for 10: explicit deletion/erasure command or API, documented cloud data-retention/purge policy, independent confirmation that deletion actually removes cloud-stored data.

   • [claimed-docs] “Use --ephemeral to run a one-shot task without creating, resuming, or persisting an agent, memory blocks, or MemFS”
   • [claimed-docs] “This default local mode stores agent state on your machine and does not require a Letta login.”
   • [claimed-docs] “all agent state, including messages, memory, and provider connections, stays on-device, and no Letta account is required.”
   • [claimed-docs] “Letta agents can run entirely on infrastructure you control”

   proof ↗⚑ flag

   Airweave—none0/10

   Evidence pack covers syncing, search, MCP, and connectors but contains no mention of data retention policies, deletion controls, or user-initiated data purging/export for collections or synced data. This is an applicable axis for a data-sync/RAG platform handling third-party app data, so absence of evidence yields 'none'.

   ⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Letta—none0/10

   No evidence pack item addresses telemetry, usage analytics, or an opt-out mechanism; while local self-hosted mode is documented, nothing confirms or denies data collection/telemetry settings.

   ⚑ flag

   Airweave—none0/10

   No evidence in the pack mentions telemetry, usage tracking, analytics collection, or an opt-out mechanism for Airweave; the docs cover collections, search, MCP, CLI, and integrations but never address telemetry practices.

   ⚑ flag

Latency

1. platform-engineerSee documented retrieval-latency targets or measured numbers (e.g. p50/p95) backing the product's speed claims

   weight 2 · round to Airweave
   Letta—none0/10

   No evidence pack item mentions retrieval latency, p50/p95, or any measured/documented performance numbers for search or memory retrieval; documentation covers features like MemFS search mods and dreaming but never quantifies speed. missing for 10: any documented latency targets, benchmark numbers, or measured p50/p95 retrieval performance data.

   ⚑ flag

   Airweave~partialclaimed3/10

   Airweave documents a single rough latency figure ("~0.5sec" for direct vector search) but provides no p50/p95 breakdown, no methodology, benchmark environment, or measured distributions, and no independent corroboration of this number. Missing for 10: documented p50/p95 percentile targets, benchmark methodology/environment details, and independent verification of the latency claim.

   • [claimed-docs] “Direct vector search. Use when speed is critical (~0.5sec).”
   • [claimed-docs] “Direct vector search. Use when speed is critical (\~0.5sec).”

   proof ↗⚑ flag

Scale

1. platform-engineerIngest at scale with async or batch processing and check the status of background memory operations

   weight 2 · round to Airweave
   Letta—none0/10

   Letta's docs describe per-agent memory consolidation ('dreaming' background subagents, triggers on steps/compaction) but there is no evidence of a bulk/batch ingestion pipeline for scale data loading nor any API/CLI to check the status of background memory jobs, which is what this platform-engineer story requires.

   ⚑ flag

   Airweave~partialclaimed5/10

   Airweave's source connections 'automatically sync data' in the background, and webhooks notify when 'syncs completing' occur, with docs noting this is an alternative to 'constantly polling the API' — implying an async sync/status mechanism exists. However, there is no explicit documentation of batch/large-scale ingestion controls, job-status endpoints, or throughput guarantees for platform-engineer-scale operations. Missing for 10: explicit batch/async ingestion API docs, sync job status endpoint documentation, scale/throughput benchmarks or SLAs.

   • [claimed-docs] “A source connection links a specific app or database to your collection. It handles authentication and automatically syncs data.”
   • [claimed-docs] “Webhooks are real-time notifications that Airweave sends when things happen in your organization: syncs completing, source connections being…”
   • [claimed-docs] “Instead of constantly polling the API, you register a webhook endpoint and Airweave pushes updates to you the moment they occur.”

   proof ↗⚑ flag

Agent memory

1. ai-native userConnect off-the-shelf assistants (Claude, ChatGPT, Cursor) to the same memory so every tool I use shares what it knows about me

   weight 2 · round to Airweave
   Letta—none0/10

   Evidence shows Letta integrating with Codex, Claude Code, Hermes Agent, OpenClaw for skills (docs-57), and offering an OpenAI-compatible API for tools like Open WebUI plus an ACP adapter for Zed (docs-23), but nothing shows Letta connecting to or sharing memory with off-the-shelf Claude, ChatGPT, or Cursor specifically. Letta's MCP support is client-side (Letta consuming MCP servers, docs-61/76), and community evidence notes only a third-party 'Letta-MCP-server' built by a user, not an official integration exposing Letta memory to these named assistants.

   • [claimed-docs] “Skills are portable across the Letta app and CLI, Codex, Claude Code, Hermes Agent, OpenClaw, and other compatible agents.”
   • [claimed-docs] “use the App Server’s OpenAI-compatible API with clients such as Open WebUI, or the ACP adapter with ACP clients such as Zed”
   • [claimed-docs] “The SDK supports local stdio processes, Streamable HTTP, and legacy SSE”
   • [claimed-docs] “MCP tools are discovered from servers supplied through `mcpServers` and proxied by the SDK host to the MCP server.”
   • [community] “Charles from Letta on MCP: 'We're working on it... making Letta agents an MCP client, so that you can easily connect to MCP servers as tools…”

   proof ↗⚑ flag

   Airweave✓fullprobed8/10

   Airweave ships an official MCP server that lets assistants like Claude and Cursor search synced data, plus published skills for Cursor, Claude Code, Gemini CLI, and OpenCode that enable setup/search without re-explaining, all pointing to a single shared 'collection' as the underlying memory. Community evidence corroborates real-world use with Cursor. Missing for 10: explicit first-party ChatGPT connector docs and independent evidence of multiple assistants simultaneously sharing state in practice.

   • [claimed-docs] “The Airweave MCP server implements the Model Context Protocol to let AI assistants search your synced data.”
   • [claimed-docs] “Airweave publishes official skills so that agents in Cursor, Claude Code, Gemini CLI, OpenCode, and other environments can set up integratio…”
   • [claimed-docs] “Airweave publishes official skills so that agents in Cursor, Claude Code, Gemini CLI, OpenCode, and other environments can set up integratio…”
   • [claimed-docs] “A collection is a group of different data sources that you can search using a single endpoint.”
   • [probe] “official MCP server documented at https://docs.airweave.ai/mcp-server”
   • [community] “Onyx co-founder: Congratulations on the launch. It looks like Airweave works well with Cursor, something we don't have nailed down yet!”

   proof ↗⚑ flag

Frameworks

1. developerDrop the memory layer into agent frameworks like LangChain, LangGraph, CrewAI, or the Vercel AI SDK via documented first-party integrations

   weight 2 · round to Airweave
   Letta—none0/10

   The evidence pack covers Letta's own Agent SDK, CLI, App Server, MCP support, and various demo apps, but contains no mention of LangChain, LangGraph, CrewAI, or Vercel AI SDK integrations anywhere in the docs, GitHub, or community sources.

   ⚑ flag

   Airweave~partialclaimed3/10

   Airweave documents a framework-integration pattern (e.g., LlamaIndex's AirweaveToolSpec, Pipedream actions, and MCP server/CLI/skills for coding agents), showing the product does ship first-party SDK-style hooks into agent tooling — but none of the specific frameworks named in the story (LangChain, LangGraph, CrewAI, Vercel AI SDK) appear anywhere in the evidence pack. missing for 10: documented LangChain integration, LangGraph integration, CrewAI integration, Vercel AI SDK integration.

   • [claimed-docs] “The llama-index-tools-airweave package provides an AirweaveToolSpec that gives your LlamaIndex agents access to Airweave's search capabiliti…”
   • [claimed-docs] “The Airweave integration provides a set of actions that enable you to search your synced data to retrieve relevant context, manage your coll…”
   • [claimed-docs] “The Airweave MCP server implements the Model Context Protocol to let AI assistants search your synced data.”
   • [claimed-docs] “Airweave publishes official skills so that agents in Cursor, Claude Code, Gemini CLI, OpenCode, and other environments can set up integratio…”

   proof ↗⚑ flag

2. developerWire memory into real-time voice pipelines (e.g. LiveKit, Pipecat, ElevenLabs) with documented integrations fast enough for live conversation

   weight 1 · round drawn
   Letta—none0/10

   The evidence pack contains no documentation or mention of LiveKit, Pipecat, ElevenLabs, or any real-time voice pipeline integration. The closest evidence (letta-comm-4) is a forum reply suggesting a DIY postgres-backed memory setup for a hypothetical voice use case, not a documented, low-latency SDK integration for live conversation.

   • [community] “User with a father suffering memory loss suggested Letta's framework looked interesting for building a voice-interactive LLM with memory to …”

   proof ↗⚑ flag

   Airweave—none0/10

   No evidence mentions LiveKit, Pipecat, ElevenLabs, or any voice pipeline integration; Airweave's documented integrations are limited to MCP, CLI, coding agents, LlamaIndex, and Pipedream. Latency claims (~0.5s vector search) exist but are not tied to any voice/real-time conversational framework. missing for 10: any mention of LiveKit/Pipecat/ElevenLabs, voice pipeline docs, real-time conversation latency benchmarks specific to voice use cases.

   • [claimed-docs] “Direct vector search. Use when speed is critical (~0.5sec).”
   • [claimed-docs] “The Airweave MCP server implements the Model Context Protocol to let AI assistants search your synced data.”
   • [claimed-docs] “The llama-index-tools-airweave package provides an AirweaveToolSpec that gives your LlamaIndex agents access to Airweave's search capabiliti…”
   • [claimed-docs] “The Airweave integration provides a set of actions that enable you to search your synced data to retrieve relevant context, manage your coll…”

   proof ↗⚑ flag

Sdks

1. developerBuild against official SDKs in at least Python and TypeScript with equivalent memory APIs

   weight 2 · round to Letta
   Letta~partialclaimed5/10

   The evidence extensively documents a TypeScript/JavaScript Agent SDK (client.createAgent(), sessions, streaming, MCP, browser/mobile support) but no evidence pack item confirms an official Python SDK or its API parity with the TypeScript SDK — despite Letta's backend being Python-based, docs cited here only reference the JS/TS Agent SDK and CLI. missing for 10: explicit official Python SDK documentation/package, confirmation of equivalent memory API surface (createAgent, sessions, streaming, MCP) across Python and TypeScript, and any independent corroboration of Python SDK usage.

   • [github] “the Letta Agent SDK for building agents into TypeScript applications”
   • [claimed-docs] “Create a stateful agent with `client.createAgent()`. It returns the agent's ID as a string, which you use to open sessions and manage the ag…”
   • [claimed-docs] “`resumeSession(id)` accepts either kind of ID: pass an `agent-xxx` ID to resume the agent's default conversation, or a `conv-xxx` ID to resu…”
   • [claimed-docs] “Send a message with `session.send()` and read the response with `session.stream()`. The stream yields typed events for the whole turn”
   • [claimed-docs] “Browser, Expo, and React Native applications must import the SDK from `@letta-ai/letta-agent-sdk/client`”
   • [claimed-docs] “The SDK supports local stdio processes, Streamable HTTP, and legacy SSE”
   • [claimed-docs] “MCP tools are discovered from servers supplied through `mcpServers` and proxied by the SDK host to the MCP server.”

   proof ↗⚑ flag

   Airweave—none0/10

   No evidence pack item mentions official Python or TypeScript SDKs at all; documentation references an OpenAPI spec, MCP server, CLI, and framework integrations (LlamaIndex, Pipedream) but not dedicated Python/TypeScript client libraries with memory APIs. Missing for 10: any mention of an official Python SDK, an official TypeScript SDK, or parity of memory/search APIs between them.

   ⚑ flag

Context assembly

1. developerRetrieve a token-budgeted, prompt-ready context block assembled from relevant memories in one call

   weight 2 · round drawn
   Letta—none0/10

   Letta's docs describe memory blocks, MemFS, /doctor token audits, and search mods, but there is no evidence of a single API/CLI call that returns a token-budgeted, prompt-ready assembled context block for developer consumption outside the agent's own turn — memory in Letta is managed internally as part of the agent's system prompt, not exposed as a discrete retrieval endpoint.

   • [claimed-docs] “If the memory hierarchy has drifted or grown too large, run /doctor to audit placement, duplication, and system-prompt token usage.”
   • [claimed-docs] “Pass memory for full control over the agent’s starting memory. Each entry becomes a Markdown file in the agent’s memory repository”
   • [claimed-docs] “For keyword search and optional semantic or hybrid search, install the [MemFS Search mod]”
   • [claimed-docs] “For keyword search and optional semantic or hybrid search, install the MemFS Search mod”
   • [claimed-docs] “`persona` and `human` are conveniences that set the agent's persona and human memory”

   proof ↗⚑ flag

   Airweave—none0/10

   Airweave's docs describe search endpoints (direct vector search and agentic search) returning results from connected sources, but there is no mention of a token-budgeted or prompt-ready context assembly feature. Missing for 10: any documentation of token-limit controls, context-window formatting, or a single-call 'assemble context' endpoint.

   • [claimed-docs] “Direct vector search. Use when speed is critical (~0.5sec).”
   • [claimed-docs] “An AI agent iteratively searches your data using tool calling. It searches with multiple strategies, reads full documents, navigates entity …”
   • [claimed-docs] “Airweave lets AI agents search across company knowledge bases, cloud drives, databases, and SaaS tools in a single query.”

   proof ↗⚑ flag

Ingestion

1. developerIngest documents, JSON, and business data into memory — not just chat transcripts

   weight 2 · round to Airweave
   Letta~partialclaimed5/10

   Letta's memory system (MemFS) is file/markdown-based and the SDK lets developers 'pass memory for full control' where 'each entry becomes a Markdown file' — implying arbitrary content beyond chat transcripts can seed agent memory, and /init lets an agent ingest a repository's files. However, there is no explicit documentation of ingesting structured JSON or generic 'business data' formats into memory, nor any first-party example of a document/JSON ingestion pipeline. Missing for 10: explicit JSON/structured-data ingestion support, document-upload workflows, and independent/hands-on evidence of non-chat data being loaded into agent memory.

   • [claimed-docs] “Pass memory for full control over the agent’s starting memory. Each entry becomes a Markdown file in the agent’s memory repository”
   • [claimed-docs] “Run `/init` to bootstrap or refresh memory for the current project. The agent inspects the repository, asks about your working style when ne…”
   • [claimed-docs] “For keyword search and optional semantic or hybrid search, install the [MemFS Search mod]”
   • [claimed-docs] “For keyword search and optional semantic or hybrid search, install the MemFS Search mod”
   • [claimed-docs] “`persona` and `human` are conveniences that set the agent's persona and human memory”

   proof ↗⚑ flag

   Airweave✓fullcommunity8/10

   Airweave connects and syncs diverse sources — cloud drives, databases, SaaS tools, knowledge bases — into searchable collections, explicitly going beyond chat transcripts to documents, JSON/business data, and structured app data (docs-2, docs-12, docs-16). Community feedback corroborates strong retrieval across integrations. Missing for 10: independent hands-on verification of ingesting raw JSON/business data specifically (beyond documented app connectors), and detailed schema/normalization docs for non-document structured data.

   • [claimed-docs] “A source connection links a specific app or database to your collection. It handles authentication and automatically syncs data.”
   • [claimed-docs] “Airweave lets AI agents search across company knowledge bases, cloud drives, databases, and SaaS tools in a single query.”
   • [claimed-docs] “If your favorite tool or API is not yet supported, you can build a connector and either use it locally or contribute it back to the communit…”
   • [claimed-docs] “Webhooks are real-time notifications that Airweave sends when things happen in your organization: syncs completing, source connections being…”
   • [community] “Had meetings with a ton of MCP-server providers, no one came close to Airweave’s retrieval accuracy. I even tried Zapier and similar large c…”
   • [community] “Yes, a lot MCP servers are just api wrappers. Airweave looks like it copies the data and has a RAG that is processing your queries.”

   proof ↗⚑ flag

2. developerStore images, PDFs, or other files as memory inputs and recall information from them later

   weight 1 · round drawn
   Letta—none0/10

   Letta's documented memory system (MemFS, memory blocks, /remember, /init) is explicitly text/Markdown-file based, and 'image attachments' appear only in a demo chat app's UI feature list, not as a supported memory-recall input type for PDFs or images. No evidence shows agents can ingest images or PDFs into memory and recall facts from them later.

   • [claimed-docs] “Pass memory for full control over the agent’s starting memory. Each entry becomes a Markdown file in the agent’s memory repository”
   • [claimed-docs] “For keyword search and optional semantic or hybrid search, install the [MemFS Search mod]”
   • [claimed-docs] “For keyword search and optional semantic or hybrid search, install the MemFS Search mod”
   • [claimed-docs] “Use this demo when you want to study a mobile interface with conversation history, streaming, tools, approvals, interruption, queued message…”

   proof ↗⚑ flag

   Airweave—none0/10

   Airweave's docs describe syncing structured data from apps/databases and cloud drives (Slack, GitHub, Google Drive, Notion) into searchable collections, but no evidence shows direct ingestion of images, PDFs, or arbitrary files as memory inputs, nor multimodal parsing/recall of such files. missing for 10: explicit file/image/PDF upload API, multimodal parsing or OCR capability, and any documentation or example of recalling content from a stored image/PDF.

   • [claimed-docs] “A source connection links a specific app or database to your collection. It handles authentication and automatically syncs data.”
   • [claimed-docs] “Airweave Connect is a hosted, embeddable UI widget that lets end users connect their apps (Slack, GitHub, Google Drive, Notion, and more) di…”
   • [claimed-docs] “Airweave lets AI agents search across company knowledge bases, cloud drives, databases, and SaaS tools in a single query.”

   proof ↗⚑ flag

Governance

1. platform-engineerGovern who and what can read or write memory with roles, policies, or access-control lists, and audit that access

   weight 2 · round to Letta
   Letta~partialclaimed3/10

   Letta's pricing docs mention you can 'share agents across your team (and set permissions for access)' for organizational use, implying some access control exists, but there is no documentation of roles, granular ACLs, or an audit log/trail for memory reads/writes. Missing for 10: documented role/policy definitions for memory access, explicit read/write ACLs on memory blocks, and any audit logging or access history feature.

   • [claimed-docs] “You can share agents across your team (and set permissions for access) to create custom agents for your organization”

   proof ↗⚑ flag

   Airweave—none0/10

   No evidence of RBAC, policies, ACLs, or audit logging for governing memory/data access in Airweave; docs cover collections, sources, search, sync, and integrations but nothing on access control or auditing.

   ⚑ flag

Isolation

1. developerScope memories per user, agent, or application so one tenant's memories never leak into another's retrieval

   weight 3 · round to Letta
   Letta~partialclaimed5/10

   Letta's core model is per-agent stateful memory (each agent has its own memory blocks/files, docs-42, docs-48), and cross-agent sharing is opt-in via explicit 'shared-memory' repos (docs-8, docs-21, docs-29) rather than automatic leakage, plus team/org permission controls exist (docs-87: 'share agents across your team and set permissions for access'). However there is no documentation of explicit multi-tenant isolation guarantees (per-user/per-application namespacing, access-control enforcement details, or audit of leakage prevention) beyond these general mechanisms. Missing for 10: explicit tenant/user isolation model, documented ACL/RBAC enforcement for memory retrieval, and any independent verification that scoping prevents cross-tenant leakage.

   • [claimed-docs] “Create a stateful agent with `client.createAgent()`. It returns the agent's ID as a string, which you use to open sessions and manage the ag…”
   • [claimed-docs] “`persona` and `human` are conveniences that set the agent's persona and human memory”
   • [claimed-docs] “letta shared-memory create --name team-memory”
   • [claimed-docs] “Shared memory gives multiple agents access to the same files and working context. Each shared memory repository is a Git repository hosted i…”
   • [claimed-docs] “Shared memory gives multiple agents access to the same files and working context.”
   • [claimed-docs] “You can share agents across your team (and set permissions for access) to create custom agents for your organization”

   proof ↗⚑ flag

   Airweave—none0/10

   Airweave's docs describe collections, source connections, and organizations as organizational units, but nothing in the evidence pack describes per-user/agent/application scoping guarantees or tenant-isolation enforcement in retrieval. No mention of access control, row-level security, or per-tenant query filtering that would prevent cross-tenant leakage.

   • [claimed-docs] “A collection is a group of different data sources that you can search using a single endpoint.”
   • [claimed-docs] “A source connection links a specific app or database to your collection. It handles authentication and automatically syncs data.”
   • [claimed-docs] “Webhooks are real-time notifications that Airweave sends when things happen in your organization: syncs completing, source connections being…”

   proof ↗⚑ flag

Sharing

1. developerShare selected memory across multiple agents or users (team or group memory) while keeping private memory private

   weight 1 · round to Letta
   Letta✓fullclaimed7/10

   Letta ships a dedicated shared-memory feature (`letta shared-memory create`, Git-backed shared repositories giving multiple agents common context) alongside per-agent private memory blocks, and pricing docs explicitly mention team-level agent sharing with configurable permissions. This directly matches sharing selected memory across agents/users while keeping other memory private. Missing for 10: independent/hands-on corroboration of the privacy boundary enforcement and finer-grained detail on how access permissions are scoped per user vs team.

   • [claimed-docs] “letta shared-memory create --name team-memory”
   • [claimed-docs] “Shared memory gives multiple agents access to the same files and working context. Each shared memory repository is a Git repository hosted i…”
   • [claimed-docs] “Shared memory gives multiple agents access to the same files and working context.”
   • [claimed-docs] “You can share agents across your team (and set permissions for access) to create custom agents for your organization”

   proof ↗⚑ flag

   Airweave—none0/10

   Airweave's docs describe collections, source connections, and search endpoints, but nothing addresses per-user/per-agent memory scoping, shared vs. private data boundaries, or team/tenant isolation. The evidence pack has no mention of access control, multi-tenant permissions, or selective sharing of synced data between agents/users.

   ⚑ flag