Logseq vs Anytype

Agent access

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

   weight 2 · round to Anytype
   Logseq—none0/10

   There is no llms.txt file (probe returned 404) and no evidence of agent-oriented docs formatted for LLM consumption; the docs are standard human-facing markdown/wiki pages.

   • [probe] “PROBE llms.txt: HTTP 404 at https://plugins-doc.logseq.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plugins-doc.logseq.com/openapi.json, https://plugins-doc.logseq.com/swagger.json, https://pl…”

   proof ↗⚑ flag

   Anytype✓fullprobed8/10

   A direct probe confirms Anytype hosts an llms.txt file at doc.anytype.io/llms.txt returning HTTP 200 with organized links to agent-oriented docs, and the developer docs explicitly provide an 'anytype-agents-skill' page meant to be dropped into Claude Code, Cursor, Gemini CLI, etc. so agents can operate on Anytype data directly. This shows both a machine-readable llms.txt entrypoint and human-authored agent-oriented documentation designed for pointing coding agents at. missing for 10: no independent/community confirmation that agents actually consume llms.txt successfully in practice beyond the vendor's own docs and probe.

   • [probe] “PROBE llms.txt: HTTP 200 at https://doc.anytype.io/llms.txt # Anytype Docs ## English - [Welcome](https://doc.anytype.io/anytype/getting-s…”
   • [claimed-docs] “Drop it into Claude Code, Cursor, Gemini CLI, GitHub Copilot, or any other agent-capable tool, and the agent can run scripts against your An…”
   • [claimed-docs] “the agent can run scripts against your Anytype data — programmatically — to handle bulk edits, transformations, and repetitive tasks”
   • [claimed-docs] “an open-source toolkit that gives AI assistants a safe way to read, search, and modify Objects in your Anytype Channels”

   proof ↗⚑ flag

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

   weight 2 · round to Anytype
   Logseq—none0/10

   Logseq is a desktop/mobile Electron app with a local HTTP API and plugin system, but nothing in the evidence describes a headless mode, CLI, or CI-runnable binary for automation — the HTTP API requires the desktop app to be running interactively. Missing for 10: any documented headless/CLI mode, CI examples, or automation-oriented server mode.

   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [claimed-docs] “Logseq: A privacy-first, open-source knowledge base”

   proof ↗⚑ flag

   Anytype~partialprobed5/10

   Anytype's docs explicitly claim a CLI that can run Anytype as a headless server for automation and scripting (anytype-docs-2), and a Docker image is maintained for self-hosted network use (anytype-docs-19). However, the only runtime evidence available is for the MCP integration, which requires the desktop GUI app to be actively running and reachable ('Can't connect to API... ensure Anytype is running'), undercutting a fully headless story for the primary automation surface, and there is no independent corroboration of the CLI's headless-server behavior itself. Missing for 10: hands-on verification that the CLI truly runs without any GUI/app dependency, CI-pipeline examples, and independent reports of headless automation in production.

   • [claimed-docs] “Anytype CLI is now available - run Anytype as a headless server for automation and scripting.”
   • [claimed-docs] “There's also a docker image that's maintained by the team.”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Anytype MCP server (npm @anyproto/anytype-mcp 1.2.10) launched keylessly via `npx -y @anyp…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Logseq—none0/10

   Logseq documents a plugin system, HTTP API, and URL protocol for third-party integration, but nothing in the evidence pack mentions MCP servers or any mechanism for Logseq to consume MCP tools. Community comments even lament that AI tools like Claude/Codex can't be used to update pages, reinforcing the absence of MCP support.

   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated…”
   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [community] “I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as poss…”

   proof ↗⚑ flag

   Anytype—none0/10

   All evidence describes Anytype exposing its own local API as an MCP server for external AI assistants (Claude, Cursor, etc.) to consume — the reverse direction of this story, which asks whether Anytype itself can plug in and use external MCP servers' tools. No evidence shows Anytype acting as an MCP client that consumes third-party MCP servers.

   ⚑ flag

4. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Anytype
   Logseq—none0/10

   Logseq documents a local HTTP API and a plugin ecosystem for third-party integrations, but there is no mention anywhere in the evidence of an official Model Context Protocol (MCP) server or endpoint. Since Logseq is a knowledge-base platform (not itself an AI agent), shipping an official MCP server is a fair axis to ask about, but no such capability is evidenced.

   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated…”

   proof ↗⚑ flag

   Anytype✓fullprobed8/10

   Anytype ships an official MCP server (npm @anyproto/anytype-mcp) documented at developers.anytype.io, confirmed via runtime probe to launch and connect to the local Anytype API, enabling AI assistants to read/search/modify Objects through natural language. missing for 10: independent third-party review of the MCP server in production use beyond the vendor's own probe/docs.

   • [claimed-docs] “enabling AI assistants to seamlessly interact with Anytype's API through natural language.”
   • [claimed-docs] “enabling AI assistants to seamlessly interact with Anytype's API through natural language”
   • [probe] “official MCP server documented at https://developers.anytype.io/docs/examples/featured/mcp/”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Anytype MCP server (npm @anyproto/anytype-mcp 1.2.10) launched keylessly via `npx -y @anyp…”
   • [claimed-docs] “gives AI assistants a safe way to read, search, and modify Objects in your Anytype Channels”
   • [claimed-docs] “an open-source toolkit that gives AI assistants a safe way to read, search, and modify Objects in your Anytype Channels”

   proof ↗⚑ flag

5. ai-native userUse an official CLI

   weight 2 · round to Anytype
   Logseq—none0/10

   No evidence of an official Logseq CLI; the product exposes a local HTTP API, a URL protocol scheme, and plugins, but nothing about a command-line interface for AI-native automation. Missing for 10: any mention of an official CLI tool, its command set, or installation/usage docs.

   ⚑ flag

   Anytype✓fullclaimed7/10

   Anytype explicitly ships an official CLI ('Anytype CLI is now available - run Anytype as a headless server for automation and scripting'), positioned for scripting/automation use cases relevant to AI-native/agentic workflows. However, evidence is limited to a single doc mention with no independent hands-on verification of the CLI itself (as opposed to the API/MCP server, which is separately corroborated). Missing for 10: independent/community confirmation of the CLI in use, detailed CLI command reference or examples.

   • [claimed-docs] “Anytype CLI is now available - run Anytype as a headless server for automation and scripting.”

   proof ↗⚑ flag

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

   weight 3 · round to Anytype
   Logseq~partialprobed6/10

   Logseq documents a local HTTP APIs server explicitly for 'external access to the database through authorization' and a separate community-maintained plugin API reference, plus a logseq:// protocol for third-party invocation — all documented, public interfaces for programmatic control. However, there's no formal machine-readable spec (probes show 404s for openapi.json/llms.txt) and a community report explicitly states losing the ability to use Claude/codex to write/update pages after a version change, indicating real-world friction for AI-driven API use. Missing for 10: a formal OpenAPI/machine spec, first-party confirmation of AI-agent compatibility, and independent corroboration that the HTTP API reliably supports agentic write workflows.

   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [claimed-docs] “This is a community-driven documentation for Logseq plugin APIs.”
   • [claimed-docs] “Logseq provides a protocol `logseq://` to allow third party applications to invoke actions within Logseq.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://plugins-doc.logseq.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plugins-doc.logseq.com/openapi.json, https://plugins-doc.logseq.com/swagger.json, https://pl…”
   • [community] “I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as poss…”

   proof ↗⚑ flag

   Anytype✓fullprobed8/10

   Anytype ships a documented local REST API (OpenAPI 3.1.0 spec, 22 paths, generated developer reference) plus an official MCP server package that fronts it, and a CLI/headless server mode for automation — all confirmed by both docs and runtime probes. missing for 10: independent third-party developer testimonials building against the API beyond the vendor's own probes, and no public hosted/remote API (localhost-only).

   • [claimed-docs] “Our API is now available and directly included with the desktop app, running entirely on localhost. It operates fully offline”
   • [claimed-docs] “Anytype CLI is now available - run Anytype as a headless server for automation and scripting.”
   • [claimed-docs] “enabling AI assistants to seamlessly interact with Anytype's API through natural language.”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Anytype MCP server (npm @anyproto/anytype-mcp 1.2.10) launched keylessly via `npx -y @anyp…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the local API's machine-readable OpenAPI 3.1.0 spec (22 paths) was fetched keylessly from the vendor's …”
   • [github] “Extensible through a gRPC API and AI "Agents" (see AGENTS.md).”
   • [claimed-docs] “Drop it into Claude Code, Cursor, Gemini CLI, GitHub Copilot, or any other agent-capable tool, and the agent can run scripts against your An…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Logseq—none0/10

   Logseq's local HTTP API server requires a single authorization token for full graph access, but there is no evidence of scoped or least-privilege credential issuance (e.g., read-only vs write, per-agent scopes, or permission granularity) for AI agents.

   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [claimed-docs] “local HTTP server to access logseq's graph”

   proof ↗⚑ flag

   Anytype—none0/10

   Anytype's local API and MCP server require a key minted in the desktop app (anytype-probe-rt-1, anytype-docs-1), but nothing in the evidence describes scopes, permission levels, or least-privilege credential issuance for agents — the API/OpenAPI spec is just a flat set of endpoints (anytype-probe-rt-2) with no mention of restricting an agent's key to specific actions or Objects. missing for 10: any documentation of scoped/role-based API keys, per-agent permission restriction, or revocation/least-privilege credential model.

   • [claimed-docs] “Our API is now available and directly included with the desktop app, running entirely on localhost. It operates fully offline”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Anytype MCP server (npm @anyproto/anytype-mcp 1.2.10) launched keylessly via `npx -y @anyp…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the local API's machine-readable OpenAPI 3.1.0 spec (22 paths) was fetched keylessly from the vendor's …”

   proof ↗⚑ flag

8. ai-native userBuild against official SDKs

   weight 2 · round to Anytype
   Logseq~partialprobed6/10

   Logseq exposes a genuine plugin API/SDK (marketplace with hundreds of packages, load-unpacked plugin support) plus a local HTTP APIs server and a logseq:// URL protocol for third-party integration, giving AI-native builders real programmatic surfaces. However, the plugin API documentation is explicitly community-driven rather than official, and probes found no OpenAPI/machine-readable spec or llms.txt for these APIs. Missing for 10: official (not community-maintained) SDK documentation, an OpenAPI/schema spec, and evidence of first-party AI-agent integration guidance.

   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated…”
   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “This is a community-driven documentation for Logseq plugin APIs.”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [claimed-docs] “Logseq provides a protocol `logseq://` to allow third party applications to invoke actions within Logseq.”
   • [probe] “PROBE runtime (recorded 2026-09-05): Logseq's official plugin marketplace registry (logseq/marketplace, one directory per package) counted 6…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://plugins-doc.logseq.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plugins-doc.logseq.com/openapi.json, https://plugins-doc.logseq.com/swagger.json, https://pl…”

   proof ↗⚑ flag

   Anytype✓fullprobed8/10

   Anytype ships an official local REST API (with a machine-readable OpenAPI 3.1.0 spec covering 22 paths) built into the desktop app, a CLI, and an official MCP server (@anyproto/anytype-mcp) verified at runtime to actually connect and mint keys from the app — giving AI-native developers multiple official, documented SDK-like surfaces. Missing for 10: independent third-party SDK wrappers or client libraries beyond the official API/CLI/MCP, and broader language-specific SDK docs (only OpenAPI + CLI + MCP confirmed).

   • [claimed-docs] “Our API is now available and directly included with the desktop app, running entirely on localhost. It operates fully offline”
   • [claimed-docs] “Anytype CLI is now available - run Anytype as a headless server for automation and scripting.”
   • [claimed-docs] “enabling AI assistants to seamlessly interact with Anytype's API through natural language.”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Anytype MCP server (npm @anyproto/anytype-mcp 1.2.10) launched keylessly via `npx -y @anyp…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the local API's machine-readable OpenAPI 3.1.0 spec (22 paths) was fetched keylessly from the vendor's …”
   • [probe] “official MCP server documented at https://developers.anytype.io/docs/examples/featured/mcp/”

   proof ↗⚑ flag

9. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Logseq—none0/10

   Logseq offers a local HTTP API and a plugin system, but the evidence pack shows no webhook subscription mechanism (outbound event notifications) — only a local HTTP server for pull-based access and a custom URI protocol for inbound invocation. No documentation or community evidence describes subscribing to events via webhooks.

   ⚑ flag

   Anytype—none0/10

   No evidence of webhook subscription support anywhere in Anytype's API/local-API docs; the local API is a localhost REST/gRPC surface with an MCP server for AI assistant access, but nothing indicates event-driven webhook callbacks. Missing for 10: any documentation of webhook registration, event subscription endpoints, or push-notification mechanism.

   • [claimed-docs] “Our API is now available and directly included with the desktop app, running entirely on localhost. It operates fully offline”
   • [probe] “PROBE runtime (recorded 2026-09-05): the local API's machine-readable OpenAPI 3.1.0 spec (22 paths) was fetched keylessly from the vendor's …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://doc.anytype.io/openapi.json, https://doc.anytype.io/swagger.json, https://doc.anytype.io/api…”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to Anytype
   Logseq—none0/10

   Logseq's docs describe queries, plugins, journaling, sync, and export, but nowhere document a native AI-generated insights or suggestion feature. The only AI-adjacent mention is a community complaint that a user could no longer use Claude/codex to write/update pages, which points to third-party integration loss, not a first-party AI feature.

   • [community] “I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as poss…”
   • [claimed-docs] “Simple queries by using `{{query }}`, the format is something like this: {{query Something you're looking for}}”
   • [claimed-docs] “Queries are for asking questions from your knowledge base and the outside world (in the future).”

   proof ↗⚑ flag

   Anytype~partialprobed5/10

   Anytype doesn't ship a native in-app AI-insights feature, but its local API + official MCP server + 'Agents Skill' let external AI assistants (Claude, Cursor, Gemini CLI, etc.) read, search, and run scripts against a user's Anytype data to generate insights/suggestions, and Queries provide auto-updating views of the knowledge base. This is enablement via integration rather than a built-in 'AI-generated insights' feature inside the product itself. Missing for 10: no evidence of a native, first-party AI panel/chat that autonomously surfaces insights without wiring up an external agent, and no independent hands-on account of the agent-generated insights actually working well.

   • [claimed-docs] “enabling AI assistants to seamlessly interact with Anytype's API through natural language.”
   • [claimed-docs] “the agent can run scripts against your Anytype data — programmatically — to handle bulk edits, transformations, and repetitive tasks”
   • [claimed-docs] “gives AI assistants a safe way to read, search, and modify Objects in your Anytype Channels”
   • [claimed-docs] “an open-source toolkit that gives AI assistants a safe way to read, search, and modify Objects in your Anytype Channels”
   • [claimed-docs] “Drop it into Claude Code, Cursor, Gemini CLI, GitHub Copilot, or any other agent-capable tool, and the agent can run scripts against your An…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Anytype MCP server (npm @anyproto/anytype-mcp 1.2.10) launched keylessly via `npx -y @anyp…”
   • [claimed-docs] “A Query is a question you ask your knowledge base—answered instantly and kept up to date automatically.”
   • [claimed-docs] “Rather than manually curating a list of things you're looking for, you define the criteria and the Query assembles the result for you as a V…”

   proof ↗⚑ flag

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

   weight 2 · round to Anytype
   Logseq—none0/10

   Evidence shows Logseq has a plugin system, local HTTP API, and a custom URL protocol for third-party integration, but nothing describes autonomous, unattended background automations (e.g., schedulers, triggers, agent workflows) running without user action.

   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated…”
   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [claimed-docs] “Logseq provides a protocol `logseq://` to allow third party applications to invoke actions within Logseq.”

   proof ↗⚑ flag

   Anytype~partialprobed4/10

   Anytype exposes a local API, CLI (headless server), and an official MCP server plus an 'agents-skill' that lets external AI agents (Claude Code, Cursor, etc.) run scripts against Anytype data, giving building blocks for automation. However there is no documented scheduler, trigger, or persistent background-running agent inside Anytype itself — all examples describe an external agent tool invoked on-demand, not autonomous background operation. Missing for 10: evidence of a built-in scheduler/trigger system, proof that agents can run unattended over time rather than per-invocation, and independent confirmation of autonomous background execution.

   • [claimed-docs] “Anytype CLI is now available - run Anytype as a headless server for automation and scripting.”
   • [claimed-docs] “the agent can run scripts against your Anytype data — programmatically — to handle bulk edits, transformations, and repetitive tasks”
   • [claimed-docs] “Drop it into Claude Code, Cursor, Gemini CLI, GitHub Copilot, or any other agent-capable tool, and the agent can run scripts against your An…”
   • [probe] “official MCP server documented at https://developers.anytype.io/docs/examples/featured/mcp/”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Anytype MCP server (npm @anyproto/anytype-mcp 1.2.10) launched keylessly via `npx -y @anyp…”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round drawn
   Logseq—none0/10

   No evidence in the docs or community pack of a built-in AI assistant inside Logseq; only third-party plugins, HTTP API, and protocol integrations exist, and one community comment references using external tools like Claude/Codex to edit pages, not a native assistant.

   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated…”
   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [community] “I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as poss…”

   proof ↗⚑ flag

   Anytype—none0/10

   Evidence shows Anytype exposes a local API, CLI, and MCP server that let *external* AI assistants (Claude Code, Cursor, Gemini CLI, etc.) read/write Anytype data — this is Anytype acting as a data backend for outside agents, not a built-in AI assistant living inside the product that a user can delegate tasks to. No docs mention an in-app chat/assistant feature.

   • [claimed-docs] “enabling AI assistants to seamlessly interact with Anytype's API through natural language.”
   • [claimed-docs] “the agent can run scripts against your Anytype data — programmatically — to handle bulk edits, transformations, and repetitive tasks”
   • [claimed-docs] “Drop it into Claude Code, Cursor, Gemini CLI, GitHub Copilot, or any other agent-capable tool, and the agent can run scripts against your An…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Anytype MCP server (npm @anyproto/anytype-mcp 1.2.10) launched keylessly via `npx -y @anyp…”
   • [github] “Extensible through a gRPC API and AI "Agents" (see AGENTS.md).”

   proof ↗⚑ flag

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

   weight 2 · round to Anytype
   Logseq—none0/10

   No evidence of a native natural-language command interface, chat-based control, or AI assistant in Logseq's docs; the product is described as a block/outline-based knowledge base with query syntax and plugin APIs, not NL commands. One community comment (logseq-comm-11) references losing the ability to use Claude/Codex to edit pages, implying such capability existed only via third-party plugin integration, not a first-party feature, and it's now broken in the new DB version.

   • [community] “I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as poss…”
   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated…”
   • [claimed-docs] “Queries are for asking questions from your knowledge base and the outside world (in the future).”

   proof ↗⚑ flag

   Anytype✓fullprobed8/10

   Anytype ships an official MCP server (npm @anyproto/anytype-mcp) that fronts its local API, explicitly documented as 'enabling AI assistants to seamlessly interact with Anytype's API through natural language,' verified working at runtime against the local app. Additionally an 'agents skill' lets agent-capable tools (Claude Code, Cursor, Gemini CLI, Copilot) run natural-language-driven scripts against Anytype data. missing for 10: independent third-party review of natural-language command accuracy/robustness beyond vendor docs and a single runtime probe.

   • [claimed-docs] “enabling AI assistants to seamlessly interact with Anytype's API through natural language.”
   • [claimed-docs] “enabling AI assistants to seamlessly interact with Anytype's API through natural language”
   • [claimed-docs] “an open-source toolkit that gives AI assistants a safe way to read, search, and modify Objects in your Anytype Channels”
   • [claimed-docs] “Drop it into Claude Code, Cursor, Gemini CLI, GitHub Copilot, or any other agent-capable tool, and the agent can run scripts against your An…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Anytype MCP server (npm @anyproto/anytype-mcp 1.2.10) launched keylessly via `npx -y @anyp…”
   • [probe] “official MCP server documented at https://developers.anytype.io/docs/examples/featured/mcp/”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round to Anytype
   Logseq—none0/10

   There is a plugin API doc site and a local HTTP API, but no evidence of an interactive API reference with runnable examples; probes explicitly show no OpenAPI/swagger spec and no llms.txt found at the plugin docs site.

   • [claimed-docs] “This is a community-driven documentation for Logseq plugin APIs.”
   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [probe] “PROBE llms.txt: HTTP 404 at https://plugins-doc.logseq.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plugins-doc.logseq.com/openapi.json, https://plugins-doc.logseq.com/swagger.json, https://pl…”

   proof ↗⚑ flag

   Anytype~partialprobed5/10

   Anytype ships a genuine local REST API with a machine-readable OpenAPI 3.1 spec (22 paths) and a developer reference site (developers.anytype.io) generated from it, which documents endpoints like chat/messages with version tags — this is the backbone of an API reference. However, there's no direct evidence of an interactive 'try it out' console or runnable code examples embedded in the docs; probes only confirm the spec's existence and doc generation, not interactivity. Missing for 10: explicit evidence of a live 'try it' widget or runnable code snippets, independent confirmation of interactive testing within the docs UI.

   • [probe] “PROBE runtime (recorded 2026-09-05): the local API's machine-readable OpenAPI 3.1.0 spec (22 paths) was fetched keylessly from the vendor's …”
   • [claimed-docs] “Create chats, send and stream messages, react, and search chat history (anytype-heart v0.50.7)”
   • [probe] “PROBE openapi: all candidate paths 404 (https://doc.anytype.io/openapi.json, https://doc.anytype.io/swagger.json, https://doc.anytype.io/api…”
   • [claimed-docs] “enabling AI assistants to seamlessly interact with Anytype's API through natural language.”

   proof ↗⚑ flag

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

   weight 2 · round to Anytype
   Logseq—none0/10

   Logseq documents a local HTTP API server and a plugin API, but there is no evidence of a downloadable machine-readable spec (OpenAPI/Swagger) for either; explicit probes for openapi.json/swagger.json at the plugin docs site returned 404s.

   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “This is a community-driven documentation for Logseq plugin APIs.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://plugins-doc.logseq.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plugins-doc.logseq.com/openapi.json, https://plugins-doc.logseq.com/swagger.json, https://pl…”

   proof ↗⚑ flag

   Anytype✓fullprobed9/10

   A genuine machine-readable OpenAPI 3.1.0 spec (22 paths) for Anytype's local API is confirmed to exist and was fetched directly from the vendor's core repo, and developers.anytype.io's API reference is generated from this same spec — i.e. a real downloadable API spec exists and is used to power official docs. Missing for 10: the spec isn't hosted at a stable public URL on the main docs domain (doc.anytype.io openapi.json paths returned 404), so discovery requires knowing the GitHub repo path rather than a standard /openapi.json convention.

   • [probe] “PROBE runtime (recorded 2026-09-05): the local API's machine-readable OpenAPI 3.1.0 spec (22 paths) was fetched keylessly from the vendor's …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://doc.anytype.io/openapi.json, https://doc.anytype.io/swagger.json, https://doc.anytype.io/api…”
   • [claimed-docs] “Our API is now available and directly included with the desktop app, running entirely on localhost. It operates fully offline”
   • [claimed-docs] “Create chats, send and stream messages, react, and search chat history (anytype-heart v0.50.7)”

   proof ↗⚑ flag

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

   weight 1 · round drawn
   Logseq—none0/10

   The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)

   ⚑ flag

   Anytype—none0/10

   Anytype's docs describe local-only mode, self-hosting, and a local API/MCP server that operates directly on the user's real Anytype data, but there is no mention of a dedicated sandbox/test space, staging environment, or mock-data mode that lets an AI agent test actions without touching production content. Evidence shows agents run scripts 'against your Anytype data' directly, with no isolation layer.

   • [claimed-docs] “the agent can run scripts against your Anytype data — programmatically — to handle bulk edits, transformations, and repetitive tasks”
   • [claimed-docs] “Drop it into Claude Code, Cursor, Gemini CLI, GitHub Copilot, or any other agent-capable tool, and the agent can run scripts against your An…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Anytype MCP server (npm @anyproto/anytype-mcp 1.2.10) launched keylessly via `npx -y @anyp…”
   • [claimed-docs] “If you prefer to fully keep your data on your device without any server to sync between your desktop and mobile, you can enable local-only m…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Logseq—none0/10

   Logseq documents a local HTTP API and a plugin API, but there is no evidence of API versioning or a documented deprecation policy anywhere in the docs; probes for openapi/llms.txt specs return 404s, and community comments (e.g., DB-version migration breaking AI tool integrations) suggest breaking changes without clear versioning guarantees.

   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://plugins-doc.logseq.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plugins-doc.logseq.com/openapi.json, https://plugins-doc.logseq.com/swagger.json, https://pl…”
   • [community] “I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as poss…”

   proof ↗⚑ flag

   Anytype—none0/10

   Evidence confirms Anytype ships a local API with an OpenAPI spec that is date-versioned (2025-04-22), but nowhere in the docs or probes is there any documented deprecation policy, versioning guarantees, or migration/sunset process for API changes. Absence of evidence for this applicable axis (a real, documented, self-hosted API exists) means the story is not delivered.

   • [probe] “PROBE runtime (recorded 2026-09-05): the local API's machine-readable OpenAPI 3.1.0 spec (22 paths) was fetched keylessly from the vendor's …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://doc.anytype.io/openapi.json, https://doc.anytype.io/swagger.json, https://doc.anytype.io/api…”
   • [claimed-docs] “Our API is now available and directly included with the desktop app, running entirely on localhost. It operates fully offline”

   proof ↗⚑ flag

Agent ops

1. ai-native userMy coding agent or assistant can read AND write my notes headlessly — through a documented local API, vendor API, or MCP server — without me touching the GUI

   weight 3 · round to Anytype
   Logseq!disputedcontradicted5/10

   Logseq documents a local HTTP APIs server explicitly built 'to support external access to the database through authorization,' which would let an agent read/write notes headlessly, plus a plugin API and logseq:// protocol for third-party invocation. However, a hands-on community report directly contradicts this working capability, stating 'Not being able to use Claude or codex anymore to write or update pages is a real deal breaker for me' — indicating the API-based read/write access broke (likely in the newer DB version). Missing for 10: confirmation the HTTP API still supports write access post-DB-migration, an official MCP server, and independent corroboration that agent read/write works reliably today.

   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “local HTTP server to access logseq's graph”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [claimed-docs] “Logseq provides a protocol `logseq://` to allow third party applications to invoke actions within Logseq.”
   • [community] “I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as poss…”

   proof ↗⚑ flag

   Anytype✓fullprobed9/10

   Anytype documents a local API and an official MCP server (@anyproto/anytype-mcp) that fronts that API, allowing AI assistants like Claude Code, Cursor, etc. to read, search, and modify Objects entirely headlessly without touching the GUI, and this was verified at runtime to actually launch and connect. The OpenAPI spec (22 paths) confirms concrete read/write endpoints beyond marketing claims. Missing for 10: independent third-party (non-vendor) hands-on report confirming write operations succeed end-to-end via the MCP server.

   • [claimed-docs] “Our API is now available and directly included with the desktop app, running entirely on localhost. It operates fully offline”
   • [claimed-docs] “enabling AI assistants to seamlessly interact with Anytype's API through natural language.”
   • [claimed-docs] “gives AI assistants a safe way to read, search, and modify Objects in your Anytype Channels”
   • [claimed-docs] “an open-source toolkit that gives AI assistants a safe way to read, search, and modify Objects in your Anytype Channels”
   • [claimed-docs] “Drop it into Claude Code, Cursor, Gemini CLI, GitHub Copilot, or any other agent-capable tool, and the agent can run scripts against your An…”
   • [probe] “official MCP server documented at https://developers.anytype.io/docs/examples/featured/mcp/”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Anytype MCP server (npm @anyproto/anytype-mcp 1.2.10) launched keylessly via `npx -y @anyp…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the local API's machine-readable OpenAPI 3.1.0 spec (22 paths) was fetched keylessly from the vendor's …”

   proof ↗⚑ flag

Ai assist

1. ai-native userConnect external LLMs and AI tools to my notes through first-party connectors or an ecosystem of AI plugins

   weight 2 · round to Anytype
   Logseq~partialprobed5/10

   Logseq has no documented first-party AI/LLM connector, but its open plugin marketplace (617 registered packages), local HTTP API for external graph access, and logseq:// protocol for third-party app integration provide an ecosystem pathway for AI plugins/tools to connect to notes. Community evidence confirms some users did integrate LLMs like Claude/codex to write/update pages, but also that this broke in the newer DB version, showing fragility rather than a robust first-party AI integration story. Missing for 10: an official AI/LLM connector or documented AI plugin category, first-party docs mentioning LLM integration, and confirmation that AI plugin workflows are stable across versions.

   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated…”
   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [claimed-docs] “Logseq provides a protocol `logseq://` to allow third party applications to invoke actions within Logseq.”
   • [probe] “PROBE runtime (recorded 2026-09-05): Logseq's official plugin marketplace registry (logseq/marketplace, one directory per package) counted 6…”
   • [community] “I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as poss…”

   proof ↗⚑ flag

   Anytype✓fullprobed8/10

   Anytype ships a first-party local API plus an official MCP server (npm @anyproto/anytype-mcp) confirmed working at runtime, enabling AI assistants like Claude, Cursor, Gemini CLI, GitHub Copilot to read/search/modify Objects, alongside an 'Agents Skill' toolkit for agent-capable tools. missing for 10: no broader third-party AI plugin marketplace/ecosystem beyond the official MCP server and agents-skill, and no independent community review of the MCP integration's real-world reliability.

   • [claimed-docs] “enabling AI assistants to seamlessly interact with Anytype's API through natural language.”
   • [claimed-docs] “enabling AI assistants to seamlessly interact with Anytype's API through natural language”
   • [claimed-docs] “gives AI assistants a safe way to read, search, and modify Objects in your Anytype Channels”
   • [claimed-docs] “an open-source toolkit that gives AI assistants a safe way to read, search, and modify Objects in your Anytype Channels”
   • [claimed-docs] “Drop it into Claude Code, Cursor, Gemini CLI, GitHub Copilot, or any other agent-capable tool, and the agent can run scripts against your An…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Anytype MCP server (npm @anyproto/anytype-mcp 1.2.10) launched keylessly via `npx -y @anyp…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the local API's machine-readable OpenAPI 3.1.0 spec (22 paths) was fetched keylessly from the vendor's …”
   • [github] “Extensible through a gRPC API and AI "Agents" (see AGENTS.md).”

   proof ↗⚑ flag

2. ai-native userA built-in AI assistant can answer questions, summarize, and draft grounded in my own notes — with clear controls over what data it sees

   weight 2 · round drawn
   Logseq—none0/10

   Logseq's own docs describe journals, queries, plugins, HTTP API, and sync, but there is no evidence of a built-in first-party AI assistant that answers/summarizes/drafts grounded in notes with data-visibility controls. A community comment even references losing the ability to use Claude/Codex on notes after a version change, implying any AI usage was via external plugins/tools rather than a native assistant.

   • [community] “I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as poss…”
   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated…”
   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”

   proof ↗⚑ flag

   Anytype—none0/10

   Anytype ships a local API and an MCP server that let external AI assistants (Claude, Cursor, etc.) read/search/modify Objects, but there is no evidence of a built-in in-app AI assistant that itself answers questions, summarizes, or drafts grounded in the user's notes with UI-level data-scope controls — the docs describe it as a toolkit for external agents, not a native assistant feature. Missing for 10 (or even partial credit): a first-party in-app assistant UI, summarization/drafting features, and explicit data-scope/consent controls within Anytype itself.

   • [claimed-docs] “enabling AI assistants to seamlessly interact with Anytype's API through natural language.”
   • [claimed-docs] “enabling AI assistants to seamlessly interact with Anytype's API through natural language”
   • [claimed-docs] “gives AI assistants a safe way to read, search, and modify Objects in your Anytype Channels”
   • [claimed-docs] “an open-source toolkit that gives AI assistants a safe way to read, search, and modify Objects in your Anytype Channels”
   • [claimed-docs] “Drop it into Claude Code, Cursor, Gemini CLI, GitHub Copilot, or any other agent-capable tool, and the agent can run scripts against your An…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Anytype MCP server (npm @anyproto/anytype-mcp 1.2.10) launched keylessly via `npx -y @anyp…”

   proof ↗⚑ flag

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

   weight 2 · round to Anytype
   Logseq~partialclaimed4/10

   Logseq exposes a local HTTP API and plugin system that could be used to script bulk edits across many blocks/pages, and its query language ({{query}}) can surface many items at once, but there is no documented native bulk-operation feature (e.g., mass rename, bulk tag, batch move) demonstrated in the evidence pack. missing for 10: explicit bulk-edit/bulk-update API or UI feature, evidence of an AI agent actually performing bulk operations via the HTTP API, independent hands-on confirmation of scale.

   • [claimed-docs] “Simple queries by using `{{query }}`, the format is something like this: {{query Something you're looking for}}”
   • [claimed-docs] “Simple queries by using `{{query }}`... You can type `/query` to create a simple query.”
   • [claimed-docs] “Queries are for asking questions from your knowledge base and the outside world (in the future).”
   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [claimed-docs] “This is a community-driven documentation for Logseq plugin APIs.”

   proof ↗⚑ flag

   Anytype~partialprobed6/10

   Anytype documents an agent skill where an AI agent can run scripts against Anytype data to handle bulk edits transformations and repetitive tasks using the local API and MCP server plus a CLI for headless automation. However this relies entirely on external scripting and agent tooling rather than a native bulk edit UI and a community report flags friction with bulk CSV merges into databases. missing for 10: native in-app bulk edit selection tools, independent hands-on verification of large-scale bulk script runs, resolution of the community reported CSV merge gap

   • [claimed-docs] “the agent can run scripts against your Anytype data — programmatically — to handle bulk edits, transformations, and repetitive tasks”
   • [claimed-docs] “Drop it into Claude Code, Cursor, Gemini CLI, GitHub Copilot, or any other agent-capable tool, and the agent can run scripts against your An…”
   • [claimed-docs] “gives AI assistants a safe way to read, search, and modify Objects in your Anytype Channels”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Anytype MCP server (npm @anyproto/anytype-mcp 1.2.10) launched keylessly via `npx -y @anyp…”
   • [community] “I consistently find myself in need of a 'merge feature' when re-importing cleaned CSV data into Anytype database objects - the larger the da…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Logseq—none0/10

   Logseq's docs describe journaling, queries, plugins, HTTP APIs, and protocol handlers, but nowhere document a rules/trigger system where user-defined events automatically fire actions (e.g., 'when block tagged X, do Y'). The plugin API and marketplace could theoretically enable such automation, but no evidence shows a first-party or documented feature for event-triggered rules.

   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated…”
   • [claimed-docs] “This is a community-driven documentation for Logseq plugin APIs.”
   • [claimed-docs] “Logseq provides a protocol `logseq://` to allow third party applications to invoke actions within Logseq.”

   proof ↗⚑ flag

   Anytype—none0/10

   Evidence shows Queries (auto-updating saved views) and an 'Agents skill' letting an external AI agent run scripts against Anytype data on request, plus an MCP/local API for AI assistants to read/write objects — but none of this describes user-defined rules that automatically trigger actions on events (e.g. 'when X happens, do Y'). There is no workflow/automation-rule engine, webhook trigger, or event-based action system documented anywhere in the pack.

   • [claimed-docs] “the agent can run scripts against your Anytype data — programmatically — to handle bulk edits, transformations, and repetitive tasks”
   • [claimed-docs] “A Query is a question you ask your knowledge base—answered instantly and kept up to date automatically.”
   • [claimed-docs] “Rather than manually curating a list of things you're looking for, you define the criteria and the Query assembles the result for you as a V…”
   • [claimed-docs] “Drop it into Claude Code, Cursor, Gemini CLI, GitHub Copilot, or any other agent-capable tool, and the agent can run scripts against your An…”
   • [claimed-docs] “gives AI assistants a safe way to read, search, and modify Objects in your Anytype Channels”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Logseq—none0/10

   No evidence of any scheduling, cron-like, or recurring workflow/automation capability in Logseq's docs or community discussion; the docs cover journaling, queries, plugins, HTTP API, and sync but nothing about triggering recurring jobs or automated workflows.

   ⚑ flag

   Anytype—none0/10

   Evidence shows Anytype exposes a local API, MCP server, and an 'agents skill' letting external agents run one-off scripts against Anytype data, but nothing describes any built-in scheduler, cron-like trigger, or recurring/automated workflow execution within Anytype itself. Automation-depth is a fair axis for an AI-native knowledge tool, so absence of evidence yields 'none' rather than 'na'.

   • [claimed-docs] “the agent can run scripts against your Anytype data — programmatically — to handle bulk edits, transformations, and repetitive tasks”
   • [claimed-docs] “Drop it into Claude Code, Cursor, Gemini CLI, GitHub Copilot, or any other agent-capable tool, and the agent can run scripts against your An…”
   • [claimed-docs] “enabling AI assistants to seamlessly interact with Anytype's API through natural language.”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Anytype MCP server (npm @anyproto/anytype-mcp 1.2.10) launched keylessly via `npx -y @anyp…”

   proof ↗⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round drawn
   Logseq—none0/10

   Logseq's evidence covers notes, queries, plugins, HTTP API, and sync, but there is no mention of any 'automation' construct (workflows, macros, agent actions) that could be versioned, reviewed, or rolled back — plugins are installed/updated/removed, not versioned as automations, and markdown files aren't presented as an automation history mechanism.

   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated…”
   • [claimed-docs] “From this dashboard, third-party plugins from the [[Marketplace]], can be searched, installed, updated and removed.”
   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the [[Marketplace]], can be searched, installed, upd…”
   • [claimed-docs] “third-party plugins from the [[Marketplace]], can be searched, installed, updated and removed.”

   proof ↗⚑ flag

   Anytype—none0/10

   Anytype documents AI agent scripting/automation capabilities (agents running scripts against Anytype data) and general object version history is not mentioned anywhere in the evidence, nor is any mechanism to version, review, or roll back automations/scripts themselves. Since Anytype does support automation via its agents-skill and API, this axis is applicable, but no evidence shows versioning, review workflows, or rollback for those automations.

   • [claimed-docs] “the agent can run scripts against your Anytype data — programmatically — to handle bulk edits, transformations, and repetitive tasks”
   • [claimed-docs] “Drop it into Claude Code, Cursor, Gemini CLI, GitHub Copilot, or any other agent-capable tool, and the agent can run scripts against your An…”
   • [claimed-docs] “gives AI assistants a safe way to read, search, and modify Objects in your Anytype Channels”

   proof ↗⚑ flag

Capture

1. researcherClip web pages, articles, and highlights from my browser straight into my notes with an official clipper or capture flow

   weight 2 · round to Logseq
   Logseq~partialclaimed4/10

   Logseq documents a 'Quick capture' feature via the logseq:// protocol that can be added as a browser bookmarklet or invoked from command line, letting users capture short text and links into notes (logseq-docs-11, logseq-docs-17, logseq-docs-27, logseq-docs-22). However, this is a lightweight bookmarklet, not a dedicated official browser-extension web clipper capable of capturing full articles, page content, or highlights as many competing tools offer. Missing for 10: an official browser extension/clipper product, support for capturing full article content or highlighted text with metadata, and any independent/hands-on evidence of researchers using this capture flow for web clipping.

   • [claimed-docs] “logseq://x-callback-url/quickCapture? ... Quick capture for short text and links. Can be added as a bookmark link to modern browser”
   • [claimed-docs] “logseq://x-callback-url/quickCapture? - Quick capture for short text and links.”
   • [claimed-docs] “Logseq provides a protocol `logseq://` to allow third party applications to invoke actions within Logseq.”
   • [claimed-docs] “Quick capture for short text and links. Can be added as a bookmark link to modern browser or opened from command line shell”

   proof ↗⚑ flag

   Anytype—none0/10

   No evidence of a browser clipper extension or web-capture flow for Anytype; import features cover Markdown/Any-Block/Obsidian migration, not web page/article clipping. Missing for 10: official browser extension, article/highlight capture flow, bookmarklet or share-to-Anytype integration.

   ⚑ flag

Daily notes

1. power-userI get an automatic daily note for each day, pre-filled from a template, as the default landing place for journaling and capture

   weight 3 · round to Logseq
   Logseq✓fullclaimed8/10

   Docs confirm Logseq opens to the Journals page every time you launch it ([logseq-docs-24]), that a new dated journal page is auto-created daily at midnight ([logseq-docs-2]), and that this page serves as the equivalent of a daily-notes capture landing page ([logseq-docs-1]). Missing for 10: explicit documentation of a customizable 'journal template' pre-fill mechanism and independent/hands-on confirmation that templates apply automatically to new daily notes.

   • [claimed-docs] “Every time you open Logseq, you start on the Journals page.”
   • [claimed-docs] “Every day at midnight a new Journals page is created with that day's date, making it easy to see when you've added what information.”
   • [claimed-docs] “For people familiar with Roam Research: the Journals page in Logseq is the same as the Daily Notes Page in Roam.”

   proof ↗⚑ flag

   Anytype—none0/10

   Anytype documents general Templates and Types (docs-13, docs-22, docs-32) but nowhere describes an automatic daily/journal note feature that auto-creates a dated entry pre-filled from a template as a default landing page — no evidence of a 'Daily Note' or journaling automation feature exists in the pack.

   • [claimed-docs] “A Template is a saved layout for a page that you can reuse.”
   • [claimed-docs] “you define what a good starting point looks like once and it'll form the base for every new Object you create afterwards”
   • [claimed-docs] “Anytype comes with built-in Types, but you can create your own custom Types to match your needs.”

   proof ↗⚑ flag

Editor

1. power-userDefine reusable templates (with variables like date and title) and apply them when creating recurring kinds of notes

   weight 2 · round to Anytype
   Logseq—none0/10

   The evidence pack contains no documentation or community mentions of Logseq's template feature (e.g. `template::` property, `/template` command, or variable substitution like date/title) — only journals, page/block references, queries, plugins, sync, and publishing are covered. Since template creation is a plausible and well-known capability for a note-taking tool, its complete absence from the evidence means this axis cannot be credited as delivered.

   ⚑ flag

   Anytype~partialclaimed6/10

   Anytype's docs clearly describe reusable Templates ('a saved layout for a page that you can reuse' and 'define what a good starting point looks like once... base for every new Object') including customizable cover/icon, which supports recurring note types via Types+Templates. However, there's no evidence of dynamic variable substitution (e.g., auto-filled date, title placeholders) within templates—only static layout/property definitions are documented. missing for 10: explicit variable/placeholder support (auto-date, auto-title fill), independent hands-on confirmation of template variable behavior.

   • [claimed-docs] “A Template is a saved layout for a page that you can reuse.”
   • [claimed-docs] “you define what a good starting point looks like once and it'll form the base for every new Object you create afterwards”
   • [claimed-docs] “Choose an image from the gallery or upload your own image.”
   • [claimed-docs] “Anytype comes with built-in Types, but you can create your own custom Types to match your needs.”

   proof ↗⚑ flag

2. power-userWrite and format notes with headings, callouts, tables, code blocks, and embedded media in a fast keyboard-driven editor

   weight 2 · round to Anytype
   Logseq!disputedcontradicted4/10

   The evidence pack lacks any first-party documentation specifically describing headings, callouts, tables, code blocks, or media-embedding support, and instead shows only adjacent editor features (page/block references, journals) that imply block-based markdown editing. Concrete hands-on reports contradict the 'fast, keyboard-driven' claim: pasting multi-paragraph text broke formatting into unwanted lists and even crashed on longer pastes, and users report severe UI lag once graphs grow, undermining the 'fast' editing experience for power users. Missing for 10: explicit docs on headings/callouts/tables/code-block syntax, embedded media handling, and independent confirmation that these specific formatting features perform well at scale.

   • [claimed-docs] “Type `[[]]` to create or reference any other page. You can also make a new page in the search bar. - Type `(())` to reference a block on any…”
   • [claimed-docs] “Logseq: A privacy-first, open-source knowledge base”
   • [community] “I used Logseq for a while but the big problem I had with it is how strongly it is focused on bullet points. Posting long form text is cumber…”
   • [community] “Admittedly poor performance has been my primary gripe in the 7mos I've been using LogSeq on a near-daily basis... I'd gladly pay for a subsc…”
   • [community] “Indexing and general responsiveness slows down massively once you have a few million words stored, and you have to break up your data into m…”

   proof ↗⚑ flag

   Anytype~partialcommunity5/10

   Docs and GitHub confirm a block-based editor (text, databases, kanban, calendar, custom Types) and community reports confirm tables exist (though 'simple, no formulas'), plus templates and page icons/covers. However there is no explicit evidence for headings, callouts, or code blocks as first-class formatting elements, nor any documentation of keyboard shortcuts or 'fast keyboard-driven' editing speed, and embedded media support is only implied via cover images. missing for 10: explicit callout/heading/code-block support, documented keyboard-shortcut system, and evidence of rich embedded media (video/audio/files) in the editor.

   • [github] “Composable blocks: text, databases, kanban, calendar & custom Types.”
   • [community] “Anytype has tables now, simple, no formulas yet. Plan to add formulas to databases - it's one of the top requested features on our forum (co…”
   • [claimed-docs] “A Template is a saved layout for a page that you can reuse.”
   • [claimed-docs] “Anytype comes with built-in Types, but you can create your own custom Types to match your needs.”
   • [community] “I've been using this for about a year. It's very polished and been stable for me. The Apple and Android apps work well too... I'm using it a…”

   proof ↗⚑ flag

Migration

1. switcherExport my entire knowledge base at any time in open formats, so leaving is as easy as arriving

   weight 2 · round to Anytype
   Logseq!disputedcontradicted5/10

   Logseq documents a genuine multi-format Export feature (Markdown, HTML, OPML, JSON, EDN, PNG) and historically stores data as local plain Markdown files, supporting easy exit at any time [logseq-docs-8]. However, hands-on community reports contradict the 'open, portable' framing: exported Markdown adds non-standard formatting that breaks compatibility with other Markdown apps like Obsidian [logseq-comm-19], and the newer Logseq DB version reportedly moves away from storing everything as plain markdown files, alarming users who relied on that for portability [logseq-comm-14, logseq-comm-9]. Missing for 10: independent verification that exports are lossless/round-trippable, clarity on whether DB-version graphs can still export to plain markdown, and confirmation the export covers all data (assets, whiteboards, plugins config).

   • [claimed-docs] “The Logseq Export feature allows users to export their data in various formats, including text, HTML, OPML, PNG, EDN, JSON, and standard Mar…”
   • [community] “The MarkDown files it generates aren't compatible with other similar programs (Obsidian for instance). It adds 2 spaces which makes things i…”
   • [community] “Logseq remained a buggy mess, is now on an unmaintained (thus insecure) version of electron. And now after several years of complete stagnat…”
   • [community] “Yeah I felt the same about the decision when they decided to move to database structure. If it had this structure from the start it could've…”

   proof ↗⚑ flag

   Anytype✓fullclaimed8/10

   Docs explicitly state you can import content and export it at any time, with Markdown or Any-Block format choices, plus dedicated import from Obsidian and self-host backup/export of channels for migrating identities — covering the core switcher promise of open-format export/import at will. missing for 10: independent hands-on verification of export fidelity/completeness and no explicit mention of bulk/full-space export beyond channel-level export.

   • [claimed-docs] “Choose your preferred format: Markdown or Any-Block.”
   • [claimed-docs] “You can import content into your spaces and export it at any time.”
   • [claimed-docs] “Anytype will process the contents and automatically create a separate object for each Markdown file.”
   • [claimed-docs] “Open Channel Settings → Import → Obsidian and click on Import files.”
   • [claimed-docs] “export all your channels, and import them into a new identity after switching the network mode”
   • [claimed-docs] “To back up your channels and data to a self-hosted network, you need to have a network configuration.”

   proof ↗⚑ flag

2. switcherImport my existing notes from Notion, Evernote, Roam, or plain Markdown with structure, links, and attachments preserved

   weight 3 · round to Anytype
   Logseq—none0/10

   The evidence pack documents Logseq's export formats and journal/page structure comparisons to Roam, but contains no mention of an import feature for Notion, Evernote, Roam exports, or Markdown migration with links/attachments preserved. Community comments mention switching from Roam via GitHub sync, not a structured import tool. Since import tooling is a plausible feature for a PKM app, absence of evidence means 'none' rather than 'na'.

   • [claimed-docs] “The Logseq Export feature allows users to export their data in various formats, including text, HTML, OPML, PNG, EDN, JSON, and standard Mar…”
   • [claimed-docs] “For people familiar with Roam Research: the Journals page in Logseq is the same as the Daily Notes Page in Roam.”
   • [community] “I switched over to LogSeq from Roam Research, and I'm using Github for syncing and backup.”

   proof ↗⚑ flag

   Anytype~partialcommunity5/10

   Anytype documents Markdown import (choose Markdown or Any-Block format) and a dedicated Obsidian migration path that creates a separate object per Markdown file, preserving structure to some degree, plus general import/export at any time. However, there is no evidence of dedicated Notion, Evernote, or Roam importers preserving links/attachments as the story specifies — only generic Markdown ingestion is documented, and a community comment even flags gaps in re-importing structured data (CSV) cleanly. Missing for 10: dedicated Notion/Evernote/Roam import tooling, evidence that links and attachments survive import from these specific sources, and independent hands-on confirmation of fidelity.

   • [claimed-docs] “Choose your preferred format: Markdown or Any-Block.”
   • [claimed-docs] “Anytype will process the contents and automatically create a separate object for each Markdown file.”
   • [claimed-docs] “Open Channel Settings → Import → Obsidian and click on Import files.”
   • [claimed-docs] “You can import content into your spaces and export it at any time.”
   • [community] “I consistently find myself in need of a 'merge feature' when re-importing cleaned CSV data into Anytype database objects - the larger the da…”

   proof ↗⚑ flag

Graph

1. researcherExplore my knowledge base as an interactive graph of notes and connections, filtered to what I care about

   weight 1 · round to Anytype
   Logseq~partialcommunity5/10

   Logseq's documented linking primitives — page/block references ([[ ]], (( ))) and simple queries ({{query}}) — provide the backbone for connecting and filtering notes, and the Whiteboard feature offers a spatial canvas with connectors for arranging knowledge visually, but no evidence explicitly documents a dedicated interactive 'graph view' with node-link visualization or filtering controls. Community reports also note serious performance degradation ('indexing and general responsiveness slows down massively once you have a few million words') which would hamper exploring a large graph. missing for 10: explicit documentation of the graph-view visualization UI and its filtering options, and independent confirmation that graph exploration performs well at scale.

   • [claimed-docs] “Type `[[]]` to create or reference any other page. You can also make a new page in the search bar. - Type `(())` to reference a block on any…”
   • [claimed-docs] “Simple queries by using `{{query }}`, the format is something like this: {{query Something you're looking for}}”
   • [claimed-docs] “Simple queries by using `{{query }}`... You can type `/query` to create a simple query.”
   • [claimed-docs] “Queries are for asking questions from your knowledge base and the outside world (in the future).”
   • [claimed-docs] “Put thoughts from your knowledge base as well as new ones next to each other on a spatial canvas together with shapes, drawings, website emb…”
   • [community] “Indexing and general responsiveness slows down massively once you have a few million words stored, and you have to break up your data into m…”

   proof ↗⚑ flag

   Anytype✓fullclaimed8/10

   Anytype's Graph is explicitly documented as 'a live, visual map of every Object in your Channel and how they connect to each other,' directly matching the interactive knowledge graph story, and linking is described as core to turning notes into a connected knowledge base. Filtering/querying is supported via the Query feature, which lets users define criteria to assemble filtered Views, though docs don't explicitly confirm Query filters apply directly to the Graph visualization itself. Missing for 10: explicit documentation or hands-on evidence that Graph view can be filtered by Query/View criteria, and independent user corroboration of the graph exploration experience.

   • [claimed-docs] “The Graph is a live, visual map of every Object in your Channel and how they connect to each other.”
   • [claimed-docs] “These connections become incredibly valuable. You can trace how ideas relate, see what's connected to a project”
   • [claimed-docs] “Linking on Anytype is what turns a bunch of separate notes into a connected knowledge base.”
   • [claimed-docs] “A Query is a question you ask your knowledge base—answered instantly and kept up to date automatically.”
   • [claimed-docs] “Rather than manually curating a list of things you're looking for, you define the criteria and the Query assembles the result for you as a V…”

   proof ↗⚑ flag

Links

1. researcherLink notes with [[wiki-style]] links and see every backlink and unlinked mention of a note in context

   weight 3 · round to Logseq
   Logseq~partialcommunity7/10

   Docs confirm core wiki-linking mechanics ([[ ]] page references, (( )) block references, journals as the default landing page) and queries for surfacing related content, which underpins backlinking functionality core to Logseq's outliner design. However, the evidence pack never explicitly documents a dedicated 'Linked References' or 'unlinked references' UI panel showing backlinks-in-context, which is a well-known Logseq feature but unevidenced here; community notes instead focus on performance/sync issues rather than confirming backlink display quality. Missing for 10: explicit docs/evidence on the Linked References and Unlinked References panels, independent hands-on confirmation of backlink context display working well at scale.

   • [claimed-docs] “Type `[[]]` to create or reference any other page. You can also make a new page in the search bar. - Type `(())` to reference a block on any…”
   • [claimed-docs] “Simple queries by using `{{query }}`, the format is something like this: {{query Something you're looking for}}”
   • [claimed-docs] “Simple queries by using `{{query }}`... You can type `/query` to create a simple query.”
   • [claimed-docs] “Queries are for asking questions from your knowledge base and the outside world (in the future).”
   • [claimed-docs] “Every time you open Logseq, you start on the Journals page.”
   • [community] “Indexing and general responsiveness slows down massively once you have a few million words stored, and you have to break up your data into m…”

   proof ↗⚑ flag

   Anytype~partialclaimed6/10

   Docs confirm bidirectional-style linking ('Linking on Anytype is what turns a bunch of separate notes into a connected knowledge base', 'trace how ideas relate, see what's connected') and a live Graph view showing every Object's connections, which covers wiki-links and a form of backlink visualization. However, the evidence never explicitly documents a dedicated 'Backlinks' panel or an 'unlinked mentions' detection feature (text mentioning a note's title without a link), so the researcher's specific in-context backlink/unlinked-mention workflow is only partly evidenced. Missing for 10: explicit backlinks list UI, unlinked-mentions detection, independent/hands-on confirmation of these specific sub-features.

   • [claimed-docs] “Linking on Anytype is what turns a bunch of separate notes into a connected knowledge base.”
   • [claimed-docs] “These connections become incredibly valuable. You can trace how ideas relate, see what's connected to a project”
   • [claimed-docs] “The Graph is a live, visual map of every Object in your Channel and how they connect to each other.”

   proof ↗⚑ flag

2. power-userReference or transclude an individual block or section of one note inside another and have it stay in sync

   weight 2 · round to Logseq
   Logseq✓fullclaimed8/10

   Logseq's block reference syntax `(())` embeds/transcludes an individual block from any page into another, and page references `[[]]` do the same at page level; since Logseq's block-based architecture keeps a single canonical block that references simply render/link to, edits propagate automatically, keeping transclusions in sync. Docs explicitly describe both block and page referencing as core features. Missing for 10: no explicit doc quote confirming live-sync behavior on edit (implied by architecture, not directly demonstrated) and no independent hands-on confirmation of transclusion sync specifically.

   • [claimed-docs] “Type `[[]]` to create or reference any other page. You can also make a new page in the search bar. - Type `(())` to reference a block on any…”
   • [claimed-docs] “Blocks that have a page as a parent i.e. usually top-level blocks can be converted to a page and back to a block easily. To convert this blo…”

   proof ↗⚑ flag

   Anytype—none0/10

   Evidence documents only object-level linking and backlinks (docs-40, docs-28) and a live Graph of Object connections (docs-9), but nowhere describes block- or section-level transclusion/embedding that stays synced across notes — a distinct feature from whole-object linking. No mention of synced blocks, block references, or embed-with-sync exists in the pack.

   • [claimed-docs] “Linking on Anytype is what turns a bunch of separate notes into a connected knowledge base.”
   • [claimed-docs] “These connections become incredibly valuable. You can trace how ideas relate, see what's connected to a project”
   • [claimed-docs] “The Graph is a live, visual map of every Object in your Channel and how they connect to each other.”

   proof ↗⚑ flag

Ownership

1. power-userMy notes live in local files or a local-first store that I own and can read without the app, and everything keeps working fully offline

   weight 3 · round drawn
   Logseq~partialcommunity6/10

   Logseq's classic (file) mode stores notes as plain Markdown on local disk, exports to multiple open formats, and only publishes pages explicitly (docs-8, docs-7, docs-23), supporting the 'own your files, work offline' story; community users confirm they read/back up the raw Markdown files themselves (comm-1, comm-19, comm-7). However, the newer DB-based version raises real doubts: a user explicitly states 'I can no longer keep all my data as markdown files' with the new format (comm-14), and others cite years of stagnation, sync bugs, and performance/data-loss concerns (comm-3, comm-5, comm-6, comm-8) that undercut confidence in durable, app-independent local ownership going forward. missing for 10: clear first-party confirmation that the DB version still exposes plain-text/local files, independent verification of offline reliability at scale, and resolution of the data-loss/performance complaints.

   • [claimed-docs] “The Logseq Export feature allows users to export their data in various formats, including text, HTML, OPML, PNG, EDN, JSON, and standard Mar…”
   • [claimed-docs] “By default no pages are public. Individual pages can be marked as public with the property `publish:: true`.”
   • [claimed-docs] “Logseq: A privacy-first, open-source knowledge base”
   • [community] “I switched over to LogSeq from Roam Research, and I'm using Github for syncing and backup.”
   • [community] “The MarkDown files it generates aren't compatible with other similar programs (Obsidian for instance). It adds 2 spaces which makes things i…”
   • [community] “I use Logseq personally and for work almost daily since a year ago or so. It's pretty nice and the 'least bad' PKM platform I'm aware of (no…”
   • [community] “Logseq remained a buggy mess, is now on an unmaintained (thus insecure) version of electron. And now after several years of complete stagnat…”
   • [community] “I had two main problems with LogSeq: 1. Not designed from the ground-up to prevent data loss. Has had data-loss issues in the past.”
   • [community] “Admittedly poor performance has been my primary gripe in the 7mos I've been using LogSeq on a near-daily basis... I'd gladly pay for a subsc…”

   proof ↗⚑ flag

   Anytype~partialcommunity6/10

   Anytype clearly delivers offline-first, locally-owned storage: docs state all content is stored locally, the app 'always works without an internet connection', data is encrypted at rest in a self-owned Vault, and a local-only sync mode exists that disables any external node entirely (anytype-docs-29, anytype-docs-30, anytype-docs-44, anytype-docs-31/43, anytype-docs-24). However, the underlying store is a proprietary local database/CRDT format, not plain files you can read without the app — the only path to human-readable local files is manual Markdown export/import (anytype-docs-11, anytype-docs-20), and a community report notes data 'lives unencrypted on-disk' at the index level despite vendor's encryption claims (anytype-comm-8, anytype-comm-9), showing some tension around the ownership/transparency claim. missing for 10: evidence that the live working store itself (not just exports) is human-readable outside the app, and independent confirmation that full offline use has no hidden network dependency beyond vendor docs.

   • [claimed-docs] “All your content is stored locally on your device... This means an offline-first experience: the app always works without an internet connec…”
   • [claimed-docs] “If you prefer to fully keep your data on your device without any server to sync between your desktop and mobile, you can enable local-only m…”
   • [claimed-docs] “A Vault is an encrypted container in Anytype that you own. Everything you create lives inside your Vault, stored directly on your device.”
   • [claimed-docs] “Only you can access your spaces and grant access to others — not even Anytype can see your content.”
   • [claimed-docs] “You control access. Only you can access your spaces and grant access to others — not even Anytype can see your content.”
   • [claimed-docs] “you can enable local-only mode. This mode disables Anytype's backup node entirely”
   • [claimed-docs] “Choose your preferred format: Markdown or Any-Block.”
   • [claimed-docs] “You can import content into your spaces and export it at any time.”
   • [community] “I found Anytype a few months ago and thought 'wow maybe I can ditch Turtl and just use this.' A few things bugged me: it's source-available …”
   • [community] “(Anytype team) All your data in Anytype is encrypted at rest; only the indexes are not encrypted currently. We have plans to also encrypt th…”

   proof ↗⚑ flag

2. researcherMy notes are stored or exportable in open, documented formats (Markdown, JSON) so my archive outlives the vendor

   weight 2 · round to Anytype
   Logseq!disputedcontradicted5/10

   Logseq's docs confirm export to open, documented formats (Markdown, JSON, EDN, OPML) and its journal-based local storage model, supporting archive portability (logseq-docs-8). However, hands-on community reports contradict full open-format durability: users note the generated Markdown isn't standard-compliant/interoperable with other tools due to extra indentation (logseq-comm-19), and the newer DB-based version reportedly abandons plain Markdown as the storage format entirely, forcing users into a proprietary DB structure (logseq-comm-14). Missing for 10: confirmation that the current/default file storage (not just export) remains plain Markdown across versions, and independent verification that exported files are lossless/interoperable.

   • [claimed-docs] “The Logseq Export feature allows users to export their data in various formats, including text, HTML, OPML, PNG, EDN, JSON, and standard Mar…”
   • [community] “The MarkDown files it generates aren't compatible with other similar programs (Obsidian for instance). It adds 2 spaces which makes things i…”
   • [community] “Logseq remained a buggy mess, is now on an unmaintained (thus insecure) version of electron. And now after several years of complete stagnat…”

   proof ↗⚑ flag

   Anytype✓fullprobed7/10

   Anytype explicitly documents Markdown export/import (choose Markdown or Any-Block format) and lets you import/export content at any time, plus Obsidian-style markdown migration, giving researchers a documented open-format path out of the vendor lock-in. The local API also exposes data via JSON over a documented OpenAPI spec, reinforcing programmatic, non-proprietary access to notes. missing for 10: explicit full-space JSON export/archival documentation and independent verification that exported Markdown preserves all object metadata/relations.

   • [claimed-docs] “Choose your preferred format: Markdown or Any-Block.”
   • [claimed-docs] “You can import content into your spaces and export it at any time.”
   • [claimed-docs] “Anytype will process the contents and automatically create a separate object for each Markdown file.”
   • [claimed-docs] “Open Channel Settings → Import → Obsidian and click on Import files.”
   • [probe] “PROBE runtime (recorded 2026-09-05): the local API's machine-readable OpenAPI 3.1.0 spec (22 paths) was fetched keylessly from the vendor's …”

   proof ↗⚑ flag

Self host

1. developerRun the whole system without the vendor's cloud — local-only mode or a self-hosted sync backend I operate myself

   weight 2 · round to Anytype
   Logseq✓fullcommunity7/10

   Logseq stores data as local Markdown/EDN files by default with no cloud requirement, and is documented as 'privacy-first' — users confirm they run it fully local or pair it with self-managed sync like GitHub instead of vendor cloud. The official Logseq Sync exists only as an optional paid vendor-hosted add-on, not a self-hosted backend, and one user explicitly notes there's no built-in way to self-host it as a server despite an open feature request. missing for 10: an officially supported self-hosted sync backend (only vendor-cloud Sync or DIY git workflows exist), and independent verification that local mode has no offline degradation.

   • [claimed-docs] “Logseq: A privacy-first, open-source knowledge base”
   • [claimed-docs] “Syncs up to 10 graphs between Logseq Desktop, Android, and iOS.”
   • [claimed-docs] “Yes, your graph is end-to-end encrypted.”
   • [community] “I switched over to LogSeq from Roam Research, and I'm using Github for syncing and backup.”
   • [community] “I use Logseq personally and for work almost daily since a year ago or so. It's pretty nice and the 'least bad' PKM platform I'm aware of (no…”
   • [community] “I know Logseq is intended as an offline-first solution, but I really wish I could self-host it as a website and have all notes saved on my s…”

   proof ↗⚑ flag

   Anytype✓fullcommunity8/10

   Anytype documents local-only mode (disables the backup node entirely, data stays on-device with offline-first storage) plus a self-hosted network backend option including a team-maintained Docker image for backing up/syncing without vendor cloud, and this is corroborated by the team's own community statements about p2p sync working without a central server. Some nuance remains around multi-device sync limitations in local-only mode and encryption caveats raised in community threads (indexes not encrypted, source-available license). Missing for 10: independent hands-on verification of a full self-hosted sync-server deployment (vs. docs-only description) and more detail on operational maturity of the self-host path.

   • [claimed-docs] “To back up your channels and data to a self-hosted network, you need to have a network configuration.”
   • [claimed-docs] “This mode disables Anytype's backup node entirely—meaning multi-device syncing will only work over the same local network”
   • [claimed-docs] “There's also a docker image that's maintained by the team.”
   • [claimed-docs] “you can enable local-only mode. This mode disables Anytype's backup node entirely”
   • [claimed-docs] “All your content is stored locally on your device... This means an offline-first experience: the app always works without an internet connec…”
   • [claimed-docs] “If you prefer to fully keep your data on your device without any server to sync between your desktop and mobile, you can enable local-only m…”
   • [claimed-docs] “You can even collaborate directly with others using peer-to-peer sync or self-host on your own network.”
   • [community] “(Anytype team) All your data in Anytype is encrypted at rest; only the indexes are not encrypted currently. We have plans to also encrypt th…”

   proof ↗⚑ flag

Mobile

1. power-userFull-featured iOS and Android apps give me my whole knowledge base — capture, search, and linking — not a stripped-down companion

   weight 2 · round to Anytype
   Logseq—none0/10

   Evidence confirms Logseq has mobile apps (iOS/Android sync up to 10 graphs, end-to-end encrypted) but contains no evidence about the actual feature set of the mobile apps themselves — no mention of whether search, linking, queries, or full editing capabilities are present on mobile versus a stripped-down capture-only experience. Community commentary focuses on desktop performance/sync bugs, not mobile app completeness.

   • [claimed-docs] “Syncs up to 10 graphs between Logseq Desktop, Android, and iOS.”
   • [claimed-docs] “Yes, your graph is end-to-end encrypted.”

   proof ↗⚑ flag

   Anytype~partialcommunity4/10

   Evidence confirms native iOS and Android apps exist and are described as polished and functional (comm-3, comm-7), and cross-device sync/offline-first architecture (anytype-docs-29, anytype-docs-30) implies capture/linking works across devices, but no documentation explicitly details mobile-specific feature parity for capture, search, and linking, and one long-term user characterizes their mobile use as 'a very basic note system,' hinting at reduced functionality vs desktop. Missing for 10: explicit docs on mobile app feature set (Queries, Graph, Types, Templates) confirming parity with desktop, and independent hands-on reviews of mobile power-user workflows beyond basic notes.

   • [community] “I've been using this for about a year. It's very polished and been stable for me. The Apple and Android apps work well too... I'm using it a…”
   • [community] “We don't offer a browser version. Instead, we have an Electron-based cross-platform app for Windows, Linux, macOS, plus native iOS and Andro…”
   • [claimed-docs] “All your content is stored locally on your device... This means an offline-first experience: the app always works without an internet connec…”
   • [claimed-docs] “If you prefer to fully keep your data on your device without any server to sync between your desktop and mobile, you can enable local-only m…”

   proof ↗⚑ flag

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

   weight 2 · round to Anytype
   Logseq!disputedcontradicted4/10

   Logseq docs describe a local HTTP APIs server for external access to the graph, a community-documented plugin API, and a logseq:// protocol for third-party invocation, suggesting programmatic access beyond the UI (logseq-docs-6, logseq-docs-21, logseq-docs-12, logseq-docs-22). However, there's no documentation showing this API surface covers 'everything' the UI can do (queries, whiteboards, publishing, sync are UI-first features with no documented API equivalents), and a hands-on user reports that after the move to the new DB version, 'Not being able to use Claude or codex anymore to write or update pages is a real deal breaker' — a concrete failure of AI-driven read/write parity (logseq-comm-11). missing for 10: full API coverage of queries/whiteboard/publish/sync, evidence of AI tools reliably reading+writing via API in the current version, independent confirmation the HTTP API matches UI capability breadth.

   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [claimed-docs] “This is a community-driven documentation for Logseq plugin APIs.”
   • [claimed-docs] “Logseq provides a protocol `logseq://` to allow third party applications to invoke actions within Logseq.”
   • [community] “I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as poss…”

   proof ↗⚑ flag

   Anytype~partialprobed6/10

   Anytype ships a real local REST API (OpenAPI spec, 22 paths, confirmed by runtime probe) plus a CLI headless server and an official MCP server that let AI agents create/search/modify objects and chats — solid API-driven access. However, the API surface (22 endpoints) is far narrower than the full UI feature set (Queries/Views, Templates, Web Publishing, Graph, Types customization, import/export flows), and no evidence confirms full parity between API and UI capabilities. Missing for 10: explicit documentation or confirmation that templates, publishing, graph, and query/view creation are all API-accessible, and independent hands-on verification of parity beyond basic CRUD/chat operations.

   • [claimed-docs] “Our API is now available and directly included with the desktop app, running entirely on localhost. It operates fully offline”
   • [claimed-docs] “Anytype CLI is now available - run Anytype as a headless server for automation and scripting.”
   • [claimed-docs] “enabling AI assistants to seamlessly interact with Anytype's API through natural language.”
   • [claimed-docs] “Create chats, send and stream messages, react, and search chat history (anytype-heart v0.50.7)”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Anytype MCP server (npm @anyproto/anytype-mcp 1.2.10) launched keylessly via `npx -y @anyp…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the local API's machine-readable OpenAPI 3.1.0 spec (22 paths) was fetched keylessly from the vendor's …”
   • [claimed-docs] “The Graph is a live, visual map of every Object in your Channel and how they connect to each other.”
   • [claimed-docs] “Web Publishing lets you turn any Object into a public webpage at a URL anyone can visit.”
   • [claimed-docs] “A Query is a question you ask your knowledge base—answered instantly and kept up to date automatically.”

   proof ↗⚑ flag

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

   weight 3 · round to Anytype
   Logseq~partialcommunity6/10

   Logseq's docs describe a native local-markdown storage model plus an explicit Export feature covering text, HTML, OPML, PNG, EDN, JSON and standard Markdown, which supports data portability and offline 'leave anytime' use (logseq-docs-8). However, community reports note markdown output isn't cleanly interoperable with other markdown apps due to formatting quirks (logseq-comm-19), and the newer DB-based version is criticized for moving away from plain markdown files as the source of truth, undermining the 'leave in open formats' guarantee for that version (logseq-comm-14). Missing for 10: independent verification that exported formats round-trip cleanly into other tools, and clarity on export fidelity in the new DB architecture.

   • [claimed-docs] “The Logseq Export feature allows users to export their data in various formats, including text, HTML, OPML, PNG, EDN, JSON, and standard Mar…”
   • [community] “The MarkDown files it generates aren't compatible with other similar programs (Obsidian for instance). It adds 2 spaces which makes things i…”
   • [community] “Logseq remained a buggy mess, is now on an unmaintained (thus insecure) version of electron. And now after several years of complete stagnat…”

   proof ↗⚑ flag

   Anytype✓fullclaimed8/10

   Anytype docs explicitly support exporting content in open formats (Markdown or Any-Block) at any time, plus local-first storage, self-hosting (including a maintained Docker image), local-only mode, and exporting/importing channels into a new identity when switching network modes — giving AI-native users a documented path to export data and leave to their own infrastructure. Missing for 10: independent/hands-on verification of export completeness and fidelity, and no detailed account of exactly what metadata/relations survive export.

   • [claimed-docs] “Choose your preferred format: Markdown or Any-Block.”
   • [claimed-docs] “You can import content into your spaces and export it at any time.”
   • [claimed-docs] “export all your channels, and import them into a new identity after switching the network mode”
   • [claimed-docs] “There's also a docker image that's maintained by the team.”
   • [claimed-docs] “If you prefer to fully keep your data on your device without any server to sync between your desktop and mobile, you can enable local-only m…”
   • [claimed-docs] “All your content is stored locally on your device... This means an offline-first experience: the app always works without an internet connec…”

   proof ↗⚑ flag

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

   weight 2 · round to Logseq
   Logseq✓fullcommunity8/10

   Logseq is explicitly described as "open-source" (logseq-docs-23), and its docs, plugin ecosystem, and marketplace are hosted publicly on GitHub, implying the source is inspectable and openly licensed; community comments corroborate "local data and source availability are important factors" (logseq-comm-7). missing for 10: explicit citation of the actual license name/terms (e.g., AGPL) and any independent audit or discussion of license compliance.

   • [claimed-docs] “Logseq: A privacy-first, open-source knowledge base”
   • [community] “I use Logseq personally and for work almost daily since a year ago or so. It's pretty nice and the 'least bad' PKM platform I'm aware of (no…”

   proof ↗⚑ flag

   Anytype!disputedcontradicted4/10

   Anytype's client code is publicly visible on GitHub (anytype-ts, anytype-heart) and even labels some AI-agent tooling 'open-source', suggesting readable source; however a hands-on community report explicitly states Anytype ships under a 'source-available license' rather than a true open license, directly contradicting an open-license claim for the core product. missing for 10: an explicit OSI-approved license file/statement for the main app repos, and resolution of the source-available vs open-source discrepancy.

   • [github] “Composable blocks: text, databases, kanban, calendar & custom Types.”
   • [github] “Extensible through a gRPC API and AI "Agents" (see AGENTS.md).”
   • [community] “I found Anytype a few months ago and thought 'wow maybe I can ditch Turtl and just use this.' A few things bugged me: it's source-available …”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to Anytype
   Logseq~partialcommunity5/10

   Logseq is open-source and stores data locally as markdown files (docs-23), and offers a local HTTP API for accessing your own graph (logseq-docs-6, logseq-docs-21), which supports a 'run entirely on your own machine' notion of self-hosting. However, there is no official self-hosted server/web deployment: a community member explicitly wished they could self-host Logseq as a website with notes on their own server, noting this remains an open, unresolved GitHub feature request among 1.8k open issues (logseq-comm-20), and official Sync is a paid, vendor-hosted cloud service rather than a self-hostable component (logseq-docs-10, logseq-comm-2). Missing for 10: an official self-hosted server/backend deployment option, first-party documentation for hosting the app as a service, and confirmation that the open feature request has been resolved.

   • [claimed-docs] “Logseq: A privacy-first, open-source knowledge base”
   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [community] “I know Logseq is intended as an offline-first solution, but I really wish I could self-host it as a website and have all notes saved on my s…”
   • [claimed-docs] “Syncs up to 10 graphs between Logseq Desktop, Android, and iOS.”
   • [community] “Logseq's own sync is now in testing and you can access it if you're a sponsor ($15/month tier)... It works fine but has enough bugs that I w…”

   proof ↗⚑ flag

   Anytype✓fullcommunity8/10

   Anytype ships a self-hostable network node (Docker image maintained by the team) for backup/sync, plus a local-only mode that removes any dependency on Anytype's backup node entirely, and the core client itself is offline-first storing all data locally. Community input corroborates the p2p/no-central-server architecture actually working in practice. Missing for 10: independent hands-on validation of running the official self-host Docker image end-to-end, and more detail on feature parity/limits of self-hosted vs managed network.

   • [claimed-docs] “To back up your channels and data to a self-hosted network, you need to have a network configuration.”
   • [claimed-docs] “There's also a docker image that's maintained by the team.”
   • [claimed-docs] “export all your channels, and import them into a new identity after switching the network mode”
   • [claimed-docs] “This mode disables Anytype's backup node entirely—meaning multi-device syncing will only work over the same local network”
   • [claimed-docs] “you can enable local-only mode. This mode disables Anytype's backup node entirely”
   • [claimed-docs] “If you prefer to fully keep your data on your device without any server to sync between your desktop and mobile, you can enable local-only m…”
   • [claimed-docs] “All your content is stored locally on your device... This means an offline-first experience: the app always works without an internet connec…”
   • [community] “(Anytype team) All your data in Anytype is encrypted at rest; only the indexes are not encrypted currently. We have plans to also encrypt th…”

   proof ↗⚑ flag

Metadata

1. power-userAttach typed properties and tags to notes and use them consistently for organization and retrieval

   weight 2 · round to Anytype
   Logseq~partialclaimed6/10

   Docs confirm block/page tagging (`#Page`) and properties (e.g., `publish:: true`), plus page/block references and query blocks (`{{query}}`) that can retrieve content by tags/properties. However, the evidence pack lacks dedicated documentation on Logseq's typed-property system (property schemas, value types, advanced query filtering by property) and no independent confirmation of consistent power-user workflows using properties for retrieval. Missing for 10: explicit docs on property types/schema, advanced query examples filtering by properties, and hands-on validation of consistent tagging/property retrieval at scale.

   • [claimed-docs] “Type `[[]]` to create or reference any other page. You can also make a new page in the search bar. - Type `(())` to reference a block on any…”
   • [claimed-docs] “Simple queries by using `{{query }}`, the format is something like this: {{query Something you're looking for}}”
   • [claimed-docs] “By default no pages are public. Individual pages can be marked as public with the property `publish:: true`.”
   • [claimed-docs] “Simple queries by using `{{query }}`... You can type `/query` to create a simple query.”
   • [claimed-docs] “Blocks that have a page as a parent i.e. usually top-level blocks can be converted to a page and back to a block easily. To convert this blo…”
   • [claimed-docs] “Queries are for asking questions from your knowledge base and the outside world (in the future).”

   proof ↗⚑ flag

   Anytype✓fullcommunity7/10

   Anytype's documented object model lets users create custom Types and attach structured properties, then retrieve them via Queries that assemble results by defined criteria (docs-32/38, docs-8/21), which is the core of typed, consistent organization and retrieval; Templates further support consistent object creation (docs-13/22). Missing for 10: explicit documentation of a dedicated 'tag' property type (only 'Types'/relations are described) and independent verification that large-scale tagging stays consistent (one community report flags friction reconciling bulk/CSV data at scale, comm-10).

   • [claimed-docs] “Anytype comes with built-in Types, but you can create your own custom Types to match your needs.”
   • [claimed-docs] “you can create your own custom Types to match your needs.”
   • [claimed-docs] “A Query is a question you ask your knowledge base—answered instantly and kept up to date automatically.”
   • [claimed-docs] “Rather than manually curating a list of things you're looking for, you define the criteria and the Query assembles the result for you as a V…”
   • [claimed-docs] “A Template is a saved layout for a page that you can reuse.”
   • [claimed-docs] “you define what a good starting point looks like once and it'll form the base for every new Object you create afterwards”
   • [community] “I consistently find myself in need of a 'merge feature' when re-importing cleaned CSV data into Anytype database objects - the larger the da…”

   proof ↗⚑ flag

Queries

1. power-userQuery my notes by their structured properties and render live database-style views (tables, boards, lists) from those queries

   weight 3 · round to Anytype
   Logseq~partialclaimed3/10

   Docs confirm a core query feature ({{query}} / /query) for asking questions of the knowledge base, and structured page/block references exist, but the pack never documents property-based structured queries or dynamic table/board/list rendering views (advanced query mode, query views like {{table}}) that power users need. missing for 10: documentation of advanced/structured-property queries, table/board/list view rendering from queries, and any hands-on confirmation of these views working.

   • [claimed-docs] “Simple queries by using `{{query }}`, the format is something like this: {{query Something you're looking for}}”
   • [claimed-docs] “Simple queries by using `{{query }}`... You can type `/query` to create a simple query.”
   • [claimed-docs] “Queries are for asking questions from your knowledge base and the outside world (in the future).”
   • [claimed-docs] “Blocks that have a page as a parent i.e. usually top-level blocks can be converted to a page and back to a block easily. To convert this blo…”

   proof ↗⚑ flag

   Anytype~partialcommunity6/10

   Anytype supports structured Types/properties and Queries that assemble live, auto-updating Views (docs describe defining criteria and getting results as a View), plus tables/kanban/calendar-style database views per the GitHub description. However, formulas are explicitly still missing per a co-founder community comment, and there's no independent hands-on evidence confirming board/list view richness or complex cross-property querying at scale. missing for 10: independent/hands-on verification of multi-view query rendering (table/board/list) beyond docs claims, confirmation of formula/aggregation support, and evidence of performance/robustness with large structured datasets.

   • [claimed-docs] “A Query is a question you ask your knowledge base—answered instantly and kept up to date automatically.”
   • [claimed-docs] “Rather than manually curating a list of things you're looking for, you define the criteria and the Query assembles the result for you as a V…”
   • [claimed-docs] “Anytype comes with built-in Types, but you can create your own custom Types to match your needs.”
   • [github] “Composable blocks: text, databases, kanban, calendar & custom Types.”
   • [community] “Anytype has tables now, simple, no formulas yet. Plan to add formulas to databases - it's one of the top requested features on our forum (co…”

   proof ↗⚑ flag

Search

1. researcherInstantly search all my notes with full-text search plus filters on tags, properties, and paths — including offline

   weight 3 · round to Anytype
   Logseq!disputedcontradicted5/10

   Logseq's docs describe a query system ({{query}}) for searching the knowledge base and page/block references and tags for organization (logseq-docs-4, -16, -19, -3), and it markets itself as privacy-first/local/offline (logseq-docs-23). However, hands-on community reports directly contradict the 'instant' part of the story: users report that 'indexing and general responsiveness slows down massively once you have a few million words stored' and describe persistent lag navigating pages even after months of daily use (logseq-comm-5, logseq-comm-6). Missing for 10: explicit documentation of a dedicated full-text search UI with tag/property/path filters (only generic query syntax is shown), and no independent benchmark confirming fast search at scale to offset the reported slowdowns.

   • [claimed-docs] “Simple queries by using `{{query }}`, the format is something like this: {{query Something you're looking for}}”
   • [claimed-docs] “Simple queries by using `{{query }}`... You can type `/query` to create a simple query.”
   • [claimed-docs] “Queries are for asking questions from your knowledge base and the outside world (in the future).”
   • [claimed-docs] “Type `[[]]` to create or reference any other page. You can also make a new page in the search bar. - Type `(())` to reference a block on any…”
   • [claimed-docs] “Logseq: A privacy-first, open-source knowledge base”
   • [community] “Admittedly poor performance has been my primary gripe in the 7mos I've been using LogSeq on a near-daily basis... I'd gladly pay for a subsc…”
   • [community] “Indexing and general responsiveness slows down massively once you have a few million words stored, and you have to break up your data into m…”

   proof ↗⚑ flag

   Anytype~partialclaimed5/10

   Anytype's Queries let users filter by Type, tag, and other properties, and all data is stored locally for a genuine offline-first experience, which supports the filtering and offline parts of this story. However, the evidence never documents a full-text search feature, path-based filtering, or how these Query filters combine with a search index — missing for 10: explicit full-text search documentation, filtering by file/object 'paths', and any performance/scale claims for search across large note collections.

   • [claimed-docs] “A Query is a question you ask your knowledge base—answered instantly and kept up to date automatically.”
   • [claimed-docs] “Rather than manually curating a list of things you're looking for, you define the criteria and the Query assembles the result for you as a V…”
   • [claimed-docs] “All your content is stored locally on your device... This means an offline-first experience: the app always works without an internet connec…”
   • [claimed-docs] “Anytype comes with built-in Types, but you can create your own custom Types to match your needs.”
   • [claimed-docs] “you can create your own custom Types to match your needs.”

   proof ↗⚑ flag

Automation hooks

1. developerDrive the app from outside — create or open notes via a URI scheme, deep links, or a local endpoint — to wire it into my scripts and workflows

   weight 2 · round drawn
   Logseq✓fullprobed8/10

   Logseq documents both a URI scheme (logseq://x-callback-url/quickCapture) that can be triggered from browser bookmarks or command line to capture/open notes, and a local HTTP APIs server enabling authorized external programmatic access to the graph — directly matching the story's ask for deep links and a local endpoint for scripting. Missing for 10: independent/hands-on confirmation of the HTTP API's request/response schema or third-party integration examples, and no evidence of a broader public REST API spec (openapi probes returned 404).

   • [claimed-docs] “local HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`”
   • [claimed-docs] “logseq://x-callback-url/quickCapture? ... Quick capture for short text and links. Can be added as a bookmark link to modern browser”
   • [claimed-docs] “logseq://x-callback-url/quickCapture? - Quick capture for short text and links.”
   • [claimed-docs] “we developed the local HTTP server to support external access to the database through authorization.”
   • [claimed-docs] “Logseq provides a protocol `logseq://` to allow third party applications to invoke actions within Logseq.”
   • [claimed-docs] “Quick capture for short text and links. Can be added as a bookmark link to modern browser or opened from command line shell”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plugins-doc.logseq.com/openapi.json, https://plugins-doc.logseq.com/swagger.json, https://pl…”

   proof ↗⚑ flag

   Anytype✓fullprobed8/10

   Anytype ships a local-API (localhost, offline) with a documented OpenAPI spec (22 paths) that developers can call directly from scripts, plus a CLI/headless server mode and an official MCP server that fronts this API for automation — all confirmed by both docs and runtime probes. This covers programmatic create/open/search of Objects for scripting and workflow integration, though it's a REST/gRPC local API rather than a classic OS-level URI scheme/deep-link handler. Missing for 10: explicit documentation of an os-level 'anytype://' URI scheme or deep-link handler, and independent third-party corroboration beyond vendor docs/probes.

   • [claimed-docs] “Our API is now available and directly included with the desktop app, running entirely on localhost. It operates fully offline”
   • [claimed-docs] “Anytype CLI is now available - run Anytype as a headless server for automation and scripting.”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Anytype MCP server (npm @anyproto/anytype-mcp 1.2.10) launched keylessly via `npx -y @anyp…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the local API's machine-readable OpenAPI 3.1.0 spec (22 paths) was fetched keylessly from the vendor's …”
   • [claimed-docs] “the agent can run scripts against your Anytype data — programmatically — to handle bulk edits, transformations, and repetitive tasks”
   • [claimed-docs] “Drop it into Claude Code, Cursor, Gemini CLI, GitHub Copilot, or any other agent-capable tool, and the agent can run scripts against your An…”

   proof ↗⚑ flag

Plugins

1. power-userBrowse and install from a large catalog of community plugins/extensions to add features the core app doesn't ship

   weight 3 · round to Logseq
   Logseq✓fullprobed8/10

   Logseq ships an in-app Marketplace dashboard to search/install/update/remove third-party plugins, plus a documented plugin API and community docs site, and a runtime probe confirms 617 published plugin packages in the official registry. Community commentary notes Logseq's ecosystem is smaller/less mature than Obsidian's, but doesn't dispute that a working plugin catalog exists. Missing for 10: independent hands-on account of browsing/installing a plugin, and quantification of catalog quality/curation vs. just count.

   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated…”
   • [claimed-docs] “From this dashboard, third-party plugins from the [[Marketplace]], can be searched, installed, updated and removed.”
   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the [[Marketplace]], can be searched, installed, upd…”
   • [claimed-docs] “Click on `Load unpacked plugin` to load plugins that are distributed outside the marketplace.”
   • [claimed-docs] “third-party plugins from the [[Marketplace]], can be searched, installed, updated and removed.”
   • [claimed-docs] “This is a community-driven documentation for Logseq plugin APIs.”
   • [probe] “PROBE runtime (recorded 2026-09-05): Logseq's official plugin marketplace registry (logseq/marketplace, one directory per package) counted 6…”
   • [community] “Yeah I felt the same about the decision when they decided to move to database structure. If it had this structure from the start it could've…”

   proof ↗⚑ flag

   Anytype—none0/10

   Anytype documents an API, CLI, MCP server, and 'Agent Skill' for scripting/AI integration, but nothing in the evidence describes a community plugin/extension marketplace or catalog that users can browse and install to add features — these integrations are developer/API surfaces, not an installable plugin ecosystem.

   • [claimed-docs] “Our API is now available and directly included with the desktop app, running entirely on localhost. It operates fully offline”
   • [claimed-docs] “Anytype CLI is now available - run Anytype as a headless server for automation and scripting.”
   • [github] “Extensible through a gRPC API and AI "Agents" (see AGENTS.md).”
   • [probe] “official MCP server documented at https://developers.anytype.io/docs/examples/featured/mcp/”

   proof ↗⚑ flag

2. developerBuild my own plugins against a documented extension API/SDK with samples and developer docs

   weight 2 · round drawn
   Logseq~partialprobed6/10

   Logseq has a documented plugin API (plugins-doc.logseq.com, described as community-driven documentation for the SDK) plus in-app tooling for loading unpacked/dev plugins and a marketplace with 617 published packages showing a real developer ecosystem. However, the core API docs are explicitly community-maintained rather than official first-party reference docs with samples, and probes show no llms.txt/openapi spec, suggesting thinner formal SDK documentation than top competitors. Missing for 10: official first-party API reference with code samples/tutorials, and machine-readable API spec (openapi/llms.txt) confirming documented completeness.

   • [claimed-docs] “Extends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated…”
   • [claimed-docs] “This is a community-driven documentation for Logseq plugin APIs.”
   • [claimed-docs] “Click on `Load unpacked plugin` to load plugins that are distributed outside the marketplace.”
   • [probe] “PROBE runtime (recorded 2026-09-05): Logseq's official plugin marketplace registry (logseq/marketplace, one directory per package) counted 6…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://plugins-doc.logseq.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://plugins-doc.logseq.com/openapi.json, https://plugins-doc.logseq.com/swagger.json, https://pl…”

   proof ↗⚑ flag

   Anytype~partialprobed6/10

   Anytype documents a local REST API (with a real OpenAPI 3.1 spec, 22 paths) plus a CLI, an official MCP server, and an 'agents skill' example showing scripts run against Anytype data — this gives developers a documented, sample-backed way to build integrations. However there's no evidence of an actual in-app plugin/extension SDK (e.g., UI extension points, a plugin marketplace, or a formal SDK package) — the API is more integration/automation-oriented than a plugin framework. Missing for 10: an official plugin SDK/framework for extending the app itself, a plugin marketplace or registry, and broader third-party plugin examples beyond MCP/agent scripts.

   • [claimed-docs] “Our API is now available and directly included with the desktop app, running entirely on localhost. It operates fully offline”
   • [claimed-docs] “Anytype CLI is now available - run Anytype as a headless server for automation and scripting.”
   • [claimed-docs] “enabling AI assistants to seamlessly interact with Anytype's API through natural language.”
   • [claimed-docs] “the agent can run scripts against your Anytype data — programmatically — to handle bulk edits, transformations, and repetitive tasks”
   • [claimed-docs] “Drop it into Claude Code, Cursor, Gemini CLI, GitHub Copilot, or any other agent-capable tool, and the agent can run scripts against your An…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the official Anytype MCP server (npm @anyproto/anytype-mcp 1.2.10) launched keylessly via `npx -y @anyp…”
   • [probe] “PROBE runtime (recorded 2026-09-05): the local API's machine-readable OpenAPI 3.1.0 spec (22 paths) was fetched keylessly from the vendor's …”
   • [github] “Extensible through a gRPC API and AI "Agents" (see AGENTS.md).”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Logseq~partialcommunity6/10

   Logseq stores data as local markdown/EDN files by default, giving users full control over where their data physically resides (their own device, self-hosted git repos, etc.), and its optional Sync service is end-to-end encrypted, which aligns with a privacy-first, local-first posture. However, there is no documented feature letting users select a specific data-center region for the Sync service, and community reports note sync reliability issues and no self-hosting option for a hosted graph. Missing for 10: explicit region/residency selection controls for the cloud Sync product, first-party documentation on where Sync servers are physically located, and confirmation that self-hosting/regional choice is officially supported rather than just achievable via local storage or third-party git.

   • [claimed-docs] “Logseq: A privacy-first, open-source knowledge base”
   • [claimed-docs] “Syncs up to 10 graphs between Logseq Desktop, Android, and iOS.”
   • [claimed-docs] “Yes, your graph is end-to-end encrypted.”
   • [community] “I switched over to LogSeq from Roam Research, and I'm using Github for syncing and backup.”
   • [community] “Logseq's own sync is now in testing and you can access it if you're a sponsor ($15/month tier)... It works fine but has enough bugs that I w…”
   • [community] “I know Logseq is intended as an offline-first solution, but I really wish I could self-host it as a website and have all notes saved on my s…”

   proof ↗⚑ flag

   Anytype~partialcommunity6/10

   Anytype is local-first (data stored on-device) and offers a self-hosted network / local-only mode, giving users control over where their data physically lives rather than a fixed vendor cloud region — this indirectly satisfies data-residency concerns. However, there's no explicit multi-region cloud selection feature or documented compliance framework (e.g., EU-only hosting) — missing for 10: explicit region/residency selection UI, documented compliance certifications, and independent verification of self-host deployment satisfying legal residency requirements.

   • [claimed-docs] “To back up your channels and data to a self-hosted network, you need to have a network configuration.”
   • [claimed-docs] “There's also a docker image that's maintained by the team.”
   • [claimed-docs] “you can enable local-only mode. This mode disables Anytype's backup node entirely”
   • [claimed-docs] “If you prefer to fully keep your data on your device without any server to sync between your desktop and mobile, you can enable local-only m…”
   • [claimed-docs] “Our infrastructure handles background syncing and backups automatically, so you retain full ownership of your data without compromising your…”
   • [community] “As a teacher I just can't use Notion or any other US-service due to GDPR concerns. I hope AnyType copies as many good Notion features so I c…”

   proof ↗⚑ flag

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

   weight 3 · round to Anytype
   Logseq~partialcommunity3/10

   Logseq positions itself as a 'privacy-first, open-source knowledge base' with local-first storage and end-to-end encrypted sync, which implies user data isn't funneled to a cloud AI training pipeline by default, but no evidence explicitly states a policy on AI model training use of user data. Missing for 10: explicit statement addressing AI training data usage, any opt-out/consent controls for AI features, and confirmation that plugins or integrations (e.g., Claude/Codex mentioned in community posts) don't send data to third-party AI services.

   • [claimed-docs] “Logseq: A privacy-first, open-source knowledge base”
   • [claimed-docs] “Yes, your graph is end-to-end encrypted.”
   • [community] “I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as poss…”

   proof ↗⚑ flag

   Anytype~partialcommunity6/10

   Anytype's local-first, encrypted architecture ('not even Anytype can see your content', all data stored locally, offline-first) strongly implies the vendor has no access to user data and thus cannot use it for AI training, and this is reinforced by the fact that AI integrations (MCP, local API) run entirely on localhost rather than sending data to a cloud AI service. However, there is no explicit vendor statement or ToS clause addressing AI-training use of data, and community evidence notes that index data is not yet encrypted at rest, a caveat to the 'we can't see your data' claim. Missing for 10: an explicit no-AI-training policy/ToS clause, and confirmation that even metadata/indexes are excluded from any vendor-side processing.

   • [claimed-docs] “Only you can access your spaces and grant access to others — not even Anytype can see your content.”
   • [claimed-docs] “You control access. Only you can access your spaces and grant access to others — not even Anytype can see your content.”
   • [claimed-docs] “All your content is stored locally on your device... This means an offline-first experience: the app always works without an internet connec…”
   • [claimed-docs] “Our API is now available and directly included with the desktop app, running entirely on localhost. It operates fully offline”
   • [community] “(Anytype team) All your data in Anytype is encrypted at rest; only the indexes are not encrypted currently. We have plans to also encrypt th…”

   proof ↗⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to Anytype
   Logseq~partialclaimed5/10

   Logseq stores graphs as local Markdown files and is marketed as 'privacy-first,' implying users can delete or retain data simply by managing local files, and Export lets users extract data in multiple formats; optional Sync is end-to-end encrypted. However, there is no explicit documentation on deletion mechanics for synced/cloud data, data-retention policies, or how to purge synced copies across devices. Missing for 10: documented data-retention/deletion policy, explicit instructions for deleting synced cloud data, and independent verification that deletion is complete and irreversible.

   • [claimed-docs] “Logseq: A privacy-first, open-source knowledge base”
   • [claimed-docs] “The Logseq Export feature allows users to export their data in various formats, including text, HTML, OPML, PNG, EDN, JSON, and standard Mar…”
   • [claimed-docs] “Syncs up to 10 graphs between Logseq Desktop, Android, and iOS.”
   • [claimed-docs] “Yes, your graph is end-to-end encrypted.”

   proof ↗⚑ flag

   Anytype~partialcommunity6/10

   Anytype's local-first architecture gives strong implicit control over retention: data lives encrypted at rest on-device (anytype-docs-44, anytype-comm-9), can be exported/imported at any time (anytype-docs-20), and local-only mode lets users disable all cloud/backup-node sync entirely (anytype-docs-24, anytype-docs-30), plus self-hosting for full network control (anytype-docs-6, anytype-docs-19). However there's no explicit documented 'delete my data/account' feature, data-retention policy statement, or purge/right-to-erasure mechanism in the evidence — only inferred control via local file ownership and export. Missing for 10: explicit deletion/erasure feature or policy docs, retention period controls, and confirmation of what happens to synced/self-hosted copies upon deletion request.

   • [claimed-docs] “A Vault is an encrypted container in Anytype that you own. Everything you create lives inside your Vault, stored directly on your device.”
   • [claimed-docs] “You can import content into your spaces and export it at any time.”
   • [claimed-docs] “you can enable local-only mode. This mode disables Anytype's backup node entirely”
   • [claimed-docs] “If you prefer to fully keep your data on your device without any server to sync between your desktop and mobile, you can enable local-only m…”
   • [claimed-docs] “To back up your channels and data to a self-hosted network, you need to have a network configuration.”
   • [community] “(Anytype team) All your data in Anytype is encrypted at rest; only the indexes are not encrypted currently. We have plans to also encrypt th…”
   • [claimed-docs] “Our infrastructure handles background syncing and backups automatically, so you retain full ownership of your data without compromising your…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Logseq—none0/10

   The evidence describes Logseq as 'privacy-first, open-source' and local-first, implying no telemetry infrastructure exists, but there is no explicit documentation of a telemetry/usage-tracking feature or an opt-out setting for it. Absence of concrete evidence of an actual telemetry toggle means this cannot be confirmed as full/partial delivery. Missing for 10: explicit telemetry/analytics policy documentation, evidence of an opt-out setting or confirmation that no tracking occurs at all.

   • [claimed-docs] “Logseq: A privacy-first, open-source knowledge base”

   proof ↗⚑ flag

   Anytype—none0/10

   The evidence pack details Anytype's local-first storage, encryption, and offline-first architecture (anytype-docs-29, anytype-docs-31, anytype-docs-43), but none of it mentions a telemetry/usage-analytics toggle or opt-out setting specifically. Privacy-by-architecture claims don't substitute for documented telemetry controls, so this applicable axis has no direct supporting evidence.

   ⚑ flag

Publish

1. researcherPublish selected notes as a browsable website — a digital garden with working links — without leaving the app

   weight 2 · round to Anytype
   Logseq✓fullclaimed7/10

   Logseq's Publishing docs confirm per-page publish:: true flags to selectively expose notes, and the Publish feature generates a browsable static SPA site with working page/block references intact, matching the digital-garden use case entirely within the app. missing for 10: no independent/hands-on report confirming the exported site's link integrity or ease of workflow, and no detail on hosting/deployment specifics or custom domain support.

   • [claimed-docs] “By default no pages are public. Individual pages can be marked as public with the property `publish:: true`.”
   • [claimed-docs] “This feature publishes a graph as a [[Publish Web]], single page application (SPA).”
   • [claimed-docs] “Type `[[]]` to create or reference any other page. You can also make a new page in the search bar. - Type `(())` to reference a block on any…”

   proof ↗⚑ flag

   Anytype✓fullclaimed8/10

   Anytype's Web Publishing feature lets users pick any Object and click Publish to generate a static HTML page on a personal subdomain (.any.org), including custom icon/cover, directly from within the app — matching the digital-garden use case with working links via the app's native linking/backlinking system. Missing for 10: no independent/community confirmation of link-following behavior between published pages or customization depth, and no evidence on bulk/multi-page publishing workflows.

   • [claimed-docs] “Web Publishing lets you turn any Object into a public webpage at a URL anyone can visit.”
   • [claimed-docs] “Pick an Object, click Publish, and Anytype generates a static HTML page hosted on your personal subdomain at .any.org/”
   • [claimed-docs] “Custom Object icon and cover — appears at the top of the page”
   • [claimed-docs] “Include a custom ANY ID — your unique handle, used for web publishing URLs”
   • [claimed-docs] “Linking on Anytype is what turns a bunch of separate notes into a connected knowledge base.”
   • [claimed-docs] “These connections become incredibly valuable. You can trace how ideas relate, see what's connected to a project”

   proof ↗⚑ flag

Collaboration

1. researcherShare a vault or space with collaborators and edit notes together without stepping on each other's changes

   weight 2 · round to Anytype
   Logseq—none0/10

   Logseq's Sync feature is described as syncing a user's own graphs across their own devices (desktop/Android/iOS), not as multi-user real-time collaborative editing with conflict resolution; community reports describe using GitHub for personal sync/backup and note Logseq's own sync was still buggy/beta, with no evidence of concurrent multi-collaborator editing safeguards.

   • [claimed-docs] “Syncs up to 10 graphs between Logseq Desktop, Android, and iOS.”
   • [claimed-docs] “Yes, your graph is end-to-end encrypted.”
   • [community] “I switched over to LogSeq from Roam Research, and I'm using Github for syncing and backup.”
   • [community] “Logseq's own sync is now in testing and you can access it if you're a sponsor ($15/month tier)... It works fine but has enough bugs that I w…”
   • [community] “I still use Logseq and conceptually it's still a great method for building a second brain. But it has been dormant for years and early attem…”

   proof ↗⚑ flag

   Anytype!disputedcontradicted4/10

   Anytype's docs claim you can share a Vault/space and collaborate without sacrificing privacy, with peer-to-peer sync or self-hosting for shared editing (anytype-docs-12, anytype-docs-33, anytype-docs-39), but independent community evidence directly contradicts this: a Notion employee notes Anytype 'still lacking collaboration' and another user reports 'you can't share with others yet' as of their hands-on testing (anytype-comm-5, anytype-comm-8), and another user flags the need for a 'merge feature' when re-importing data, suggesting conflict handling for concurrent edits is immature (anytype-comm-10). Missing for 10: documented conflict-resolution/CRDT mechanics for simultaneous multi-user edits, and recent independent confirmation that sharing/collaboration works reliably today.

   • [claimed-docs] “Anytype lets you collaborate with others without sacrificing your privacy.”
   • [claimed-docs] “Collaborators don't need to provide an email address, buy a subscription, or ask anyone for permission.”
   • [claimed-docs] “You can even collaborate directly with others using peer-to-peer sync or self-host on your own network.”
   • [community] “(Notion employee) The Anytype model is really cool - they've rebuilt Lotus Notes with 21st century E2E encrypted protocols... However they a…”
   • [community] “I found Anytype a few months ago and thought 'wow maybe I can ditch Turtl and just use this.' A few things bugged me: it's source-available …”
   • [community] “I consistently find myself in need of a 'merge feature' when re-importing cleaned CSV data into Anytype database objects - the larger the da…”

   proof ↗⚑ flag

Sync

1. power-userAn official sync service keeps my notes updated across all my devices with end-to-end encryption the vendor can't read

   weight 3 · round to Anytype
   Logseq!disputedcontradicted5/10

   Docs confirm an official Logseq Sync service across Desktop/Android/iOS with explicit end-to-end encryption ('Yes, your graph is end-to-end encrypted'), fitting the story's claim. However, community reports directly contradict reliable delivery: one user in 2022 found the paid sync beta 'has enough bugs that I wouldn't rely on it yet,' and another in 2025 stated 'early attempts at syncing didn't work well... I paid to support the sync effort but we saw nothing for years,' indicating the sync feature has a documented history of not working as promised despite payment. Missing for 10: independent verification that sync is now stable/production-ready, technical detail on the E2EE key model, and resolution of the multi-year reliability complaints.

   • [claimed-docs] “Syncs up to 10 graphs between Logseq Desktop, Android, and iOS.”
   • [claimed-docs] “Yes, your graph is end-to-end encrypted.”
   • [community] “Logseq's own sync is now in testing and you can access it if you're a sponsor ($15/month tier)... It works fine but has enough bugs that I w…”
   • [community] “I still use Logseq and conceptually it's still a great method for building a second brain. But it has been dormant for years and early attem…”
   • [community] “I loved what Logseq had to offer, and setup monthly donations for a while, but after the long period of apparent stagnation I lost faith and…”

   proof ↗⚑ flag

   Anytype!disputedcontradicted6/10

   Anytype ships an official multi-device sync via its backup-node infrastructure with claims of full E2E encryption where 'not even Anytype can see your content' (anytype-docs-31, anytype-docs-42, anytype-docs-43), and sync reportedly works well across devices (anytype-comm-9). However, a hands-on user and the vendor's own team response concretely contradict the blanket E2E claim: data is not fully encrypted on disk and 'only the indexes are not encrypted currently' (anytype-comm-8, anytype-comm-9), meaning the vendor itself confirms a gap in the encryption story it markets. missing for 10: independent security audit confirming full E2E coverage, resolution of the unencrypted-index gap, and clearer docs distinguishing at-rest vs. index encryption.

   • [claimed-docs] “Only you can access your spaces and grant access to others — not even Anytype can see your content.”
   • [claimed-docs] “Our infrastructure handles background syncing and backups automatically, so you retain full ownership of your data without compromising your…”
   • [claimed-docs] “You control access. Only you can access your spaces and grant access to others — not even Anytype can see your content.”
   • [community] “I found Anytype a few months ago and thought 'wow maybe I can ditch Turtl and just use this.' A few things bugged me: it's source-available …”
   • [community] “(Anytype team) All your data in Anytype is encrypted at rest; only the indexes are not encrypted currently. We have plans to also encrypt th…”

   proof ↗⚑ flag

2. power-userView a note's version history and restore earlier versions or recover deleted notes

   weight 2 · round drawn
   Logseq—none0/10

   The evidence pack contains no documentation of a native version-history or restore/undo-delete feature in Logseq; users instead rely on external tools like Git for backup (logseq-comm-1), and there are reports of past data-loss issues (logseq-comm-3), but no built-in mechanism to view or restore prior versions of a note is described.

   • [community] “I switched over to LogSeq from Roam Research, and I'm using Github for syncing and backup.”
   • [community] “I had two main problems with LogSeq: 1. Not designed from the ground-up to prevent data loss. Has had data-loss issues in the past.”

   proof ↗⚑ flag

   Anytype—none0/10

   No evidence in the pack mentions version history, restoring earlier versions, or recovering deleted notes; documentation covers sync, backup, encryption, import/export, and API/MCP integrations but never a version-history or undo/trash-recovery feature.

   ⚑ flag