Capacities vs Reflect
Capacities wins · 20–13 (20 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to CapacitiesA live probe confirms docs.capacities.io/llms.txt returns HTTP 200 with structured, agent-readable content describing Capacities' documentation, directly matching the story of pointing an agent at an llms.txt file; this is corroborated by the broader developer docs (MCP, API) being machine-consumable and openly hosted. Missing for 10: independent third-party confirmation that agents actually consume this llms.txt successfully in practice, and no explicit vendor statement promoting llms.txt as a first-class agent onboarding feature.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.capacities.io/llms.txt # Capacities Documentation > Documentation for Capacities, a note-taking an…”
- [claimed-docs] “Build your own app, agent, or bot and integrate it with a Capacities space by implementing a custom MCP client”
- [claimed-docs] “Build your own app, agent, or bot and integrate it with a Capacities space by implementing a custom MCP client using the Model Context Proto…”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to CapacitiesCapacities exposes a REST API with bearer/OAuth auth and a hosted MCP server (verified live with 401/OAuth challenge), which could be scripted from a CI pipeline to automate content creation/export, but there is no documented CLI, container image, or explicit 'headless mode' for running the app itself in automation contexts. Missing for 10: dedicated CI/headless-mode documentation, CLI or batch-automation examples, and independent evidence of the API being used in automated pipelines.
- [claimed-docs] “The Capacities API uses Bearer authentication (token-based authentication, OAuth 2.0 RFC 6750).”
- [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
- [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · round drawnCapacitiesnone0/10Evidence consistently shows Capacities exposes itself AS an MCP server (and its own chat-connector/API) so external AI clients (ChatGPT, Claude, custom agents) can connect TO Capacities — the reverse of this story, which asks whether Capacities can consume external MCP servers to use their tools. No documentation or probe shows Capacities' AI assistant/chat feature acting as an MCP client that plugs in third-party MCP servers.
- [claimed-docs] “Build your own app, agent, or bot and integrate it with a Capacities space by implementing a custom MCP client”
- [claimed-docs] “Build your own app, agent, or bot and integrate it with a Capacities space by implementing a custom MCP client using the Model Context Proto…”
- [claimed-docs] “Chat Connectors let you connect AI chat apps, like ChatGPT, Claude, Cursor, or Le Chat, to your Capacities space.”
- [probe] “official MCP server documented at https://docs.capacities.io/developer/model-context-protocol”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”
ai-native userConnect an agent via an official MCP server
weight 3 · round to CapacitiesA runtime probe confirms a live, official hosted MCP server at https://api.capacities.io/mcp that responds with proper OAuth-protected-resource metadata and read/write scopes, and Capacities' developer docs explicitly document this MCP endpoint. This is genuine first-party server infrastructure an AI agent can connect to, not just a client-side integration guide. Missing for 10: independent/community confirmation of a successful agent connection in practice, and the docs text is inconsistently worded (framing it as building a 'custom MCP client' rather than clearly as 'our official server'), which adds minor ambiguity.
- [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”
- [probe] “official MCP server documented at https://docs.capacities.io/developer/model-context-protocol”
- [claimed-docs] “Build your own app, agent, or bot and integrate it with a Capacities space by implementing a custom MCP client”
- [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
ai-native userUse an official CLI
weight 2 · round drawnCapacitiesnone0/10The 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.)
ai-native userDrive the product through a documented public API
weight 3 · round to CapacitiesCapacities documents a REST API with Bearer-token OAuth authentication for accessing/creating/manipulating content, and this is independently verified by a runtime probe showing a live OpenAPI 3.1 spec at api.capacities.io and a correctly bearer-gated /spaces endpoint. It also exposes an official hosted MCP server (with OAuth-scoped read/write) confirmed live via probe, giving AI-native users multiple documented, working integration paths. Missing for 10: deeper endpoint-level documentation excerpts and independent third-party developer testimonials beyond the runtime probes.
- [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
- [claimed-docs] “The Capacities API uses Bearer authentication (token-based authentication, OAuth 2.0 RFC 6750).”
- [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”
- [probe] “official MCP server documented at https://docs.capacities.io/developer/model-context-protocol”
Reflect documents a public REST API with OAuth2 (including PKCE) authentication for building third-party clients, and a runtime probe confirms the API endpoint is live and enforces auth as documented. However the API is explicitly limited to appending data and listing bookmarked links (not full CRUD due to E2E encryption), and there is no formal OpenAPI/swagger spec or llms.txt discoverability (both probed and returned 404s). Missing for 10: comprehensive OpenAPI/swagger schema, broader read/write API coverage beyond append-only actions, official SDKs, and machine-readable API discovery file.
- [claimed-docs] “For authentication, we support OAuth 2. You will need to create credentials here.”
- [claimed-docs] “Our supports appending data to your notes, returning a list of the links you've bookmarked, and a few other things.”
- [claimed-docs] “We do support OAuth's PKCE extension which means you can build a client to Reflect without shipping secret keys around.”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless GET to the documented REST base https://reflect.app/api/graphs returned HTTP 401 {"error":{"typ…”
- [probe] “PROBE llms.txt: HTTP 404 at https://reflect.academy/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://reflect.academy/openapi.json, https://reflect.academy/swagger.json, https://reflect.academy/…”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round to CapacitiesCapacities' API and MCP server use Bearer/OAuth 2.0 authentication, and the live MCP endpoint exposes discrete 'mcp:read' and 'mcp:write' scopes, showing some notion of least-privilege access. However, there is no documented mechanism for a user to generate multiple distinct API keys per-agent, restrict a token to specific spaces/objects, or revoke individual credentials independently. Missing for 10: docs on issuing/managing multiple scoped tokens, per-agent key rotation/revocation, and fine-grained resource-level permissions beyond read/write.
- [claimed-docs] “The Capacities API uses Bearer authentication (token-based authentication, OAuth 2.0 RFC 6750)”
- [claimed-docs] “The Capacities API uses Bearer authentication (token-based authentication, OAuth 2.0 RFC 6750).”
- [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”
Reflectnone0/10Reflect's API docs describe OAuth2 with PKCE (no secret keys needed) for authenticating a client, but there is no mention of scopes, granular permissions, or the ability to issue least-privilege credentials limited to specific actions/data for an agent — the API is described as a general append/list interface, not a scoped credentialing system.
- [claimed-docs] “For authentication, we support OAuth 2. You will need to create credentials here.”
- [claimed-docs] “Our supports appending data to your notes, returning a list of the links you've bookmarked, and a few other things.”
- [claimed-docs] “We do support OAuth's PKCE extension which means you can build a client to Reflect without shipping secret keys around.”
ai-native userBuild against official SDKs
weight 2 · round to CapacitiesCapacities exposes a documented REST API with a verified live OpenAPI 3.1 spec and Bearer/OAuth authentication, plus an official hosted MCP server with live OAuth-gated endpoints — solid ground for building integrations. However, no dedicated client SDKs (e.g. Python/JS libraries) are evidenced, only the raw REST API and MCP protocol spec. Missing for 10: language-specific official SDK packages, code samples/quickstarts beyond raw API docs.
- [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
- [claimed-docs] “The Capacities API uses Bearer authentication (token-based authentication, OAuth 2.0 RFC 6750)”
- [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”
- [probe] “official MCP server documented at https://docs.capacities.io/developer/model-context-protocol”
- [claimed-docs] “Build your own app, agent, or bot and integrate it with a Capacities space by implementing a custom MCP client using the Model Context Proto…”
Reflect exposes a documented REST API with OAuth2/PKCE authentication that developers can build against, confirmed live via probe, but there is no dedicated SDK package, no OpenAPI/swagger spec, and no llms.txt for AI-native tooling — the API itself is limited (append-only, no note read due to E2E encryption). missing for 10: official SDK libraries, OpenAPI spec, llms.txt/AI-friendly docs, read access to note content.
- [claimed-docs] “For authentication, we support OAuth 2. You will need to create credentials here.”
- [claimed-docs] “Our supports appending data to your notes, returning a list of the links you've bookmarked, and a few other things.”
- [claimed-docs] “We do support OAuth's PKCE extension which means you can build a client to Reflect without shipping secret keys around.”
- [probe] “PROBE llms.txt: HTTP 404 at https://reflect.academy/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://reflect.academy/openapi.json, https://reflect.academy/swagger.json, https://reflect.academy/…”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless GET to the documented REST base https://reflect.app/api/graphs returned HTTP 401 {"error":{"typ…”
ai-native userSubscribe to events via webhooks
weight 2 · round drawnCapacitiesnone0/10Evidence shows Capacities has a REST API and MCP server for pull-based access, but no documentation or probe indicates any webhook subscription mechanism for event notifications.
Reflectnone0/10Reflect's API docs describe OAuth2-based REST access for appending/reading data, but there is no mention of webhooks or event subscriptions anywhere in the docs or probes; the API is described as append-only and pull-based, not event-driven.
- [claimed-docs] “For authentication, we support OAuth 2. You will need to create credentials here.”
- [claimed-docs] “Our supports appending data to your notes, returning a list of the links you've bookmarked, and a few other things.”
- [claimed-docs] “We do support OAuth's PKCE extension which means you can build a client to Reflect without shipping secret keys around.”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless GET to the documented REST base https://reflect.app/api/graphs returned HTTP 401 {"error":{"typ…”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to ReflectCapacities offers concrete in-app AI features—AI Chats with context, AI Property Auto-Fill, and AI Image Analysis (OCR, categorization)—that provide AI-generated insights/suggestions on user data, and these are opt-in with privacy controls. However, these are fairly narrow (chat, auto-fill, image analysis) rather than broader proactive insight generation like automated summaries, trend detection, or knowledge-graph-driven suggestions. Missing for 10: evidence of proactive/automated insight surfacing (e.g., suggested connections, summaries across notes), independent hands-on reviews validating quality of AI suggestions, and broader coverage beyond the three documented AI features.
- [claimed-docs] “AI Property Auto-Fill: Rather than manually filling in the properties of your custom objects, you can rely on the AI model's knowledge to au…”
- [claimed-docs] “AI Chats: Start a chat with AI from Explore, or with a keyboard shortcut. You can pass blocks or notes as context.”
- [claimed-docs] “AI Image Analysis: Analyze any image with one click. The AI extracts a title, description, text (OCR, including handwritten text), a color p…”
- [claimed-docs] “Rather than manually filling in the properties of your custom objects, you can rely on the AI model's knowledge to auto-fill them for you.”
- [claimed-docs] “AI features in Capacities are fully opt-in. If you do not activate AI, no data from your spaces is shared with any third-party AI services”
Reflect's AI palette lets users summarize meeting notes into action items/key takeaways, ask free-form questions, chat with filtered notes, and choose between GPT-4o and Claude 3.5 Sonnet — clear AI-generated insight/suggestion features built into the product. Missing for 10: independent/hands-on validation of insight quality and any proactive (vs. purely on-demand) suggestion generation.
- [claimed-docs] “List action-items and key takeaways from meeting notes”
- [claimed-docs] “You can also ask the AI palette anything you’d like using the open text field, and save it as a custom prompt to quickly call on again later…”
- [claimed-docs] “To use it, first highlight some text, and then press `cmd j`... That’ll popup the AI palette.”
- [claimed-docs] “You can also **ask the AI palette anything** you’d like using the open text field, and save it as a custom prompt to quickly call on again l…”
- [claimed-docs] “Reflect's AI tools give you the option to now use either GPT-4o (the latest model from OpenAI) or Claude 3.5 Sonnet (the latest model from A…”
- [claimed-docs] “you can also “chat” with those specific notes to ask questions and extract information.”
- [claimed-docs] “After applying any desired filters to the search, you can also “chat” with those specific notes to ask questions and extract information.”
ai-native userSet up automations that run autonomously in the background
weight 2 · round drawnCapacitiesnone0/10Evidence shows only a scheduled full-export feature and API/MCP integration points for external clients, but nothing indicating autonomous, self-triggering background automations (e.g., workflows/triggers acting on data changes) running inside Capacities.
- [claimed-docs] “You can schedule automatic exports by going to Settings > Full Export > Automated Full Export > Add Schedule.”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”
- [claimed-docs] “AI features in Capacities are fully opt-in. If you do not activate AI, no data from your spaces is shared with any third-party AI services”
Reflectnone0/10Reflect is a note-taking app with integrations, deep links, and an append-only API, but there is no evidence of any automation/workflow engine, scheduler, or trigger system that runs autonomously in the background without user action. Integrations (Trello, Asana, calendar sync) are passive data pulls, not user-configured autonomous automations.
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round to ReflectCapacities ships a built-in AI assistant with AI Chats (pass blocks/notes as context), AI Property Auto-Fill, and AI Image Analysis, which are genuine in-app AI delegation features (opt-in, per capacities-docs-16/23/24/36). However, these are narrow, single-step assist functions rather than open-ended agentic task delegation (e.g., multi-step autonomous workflows or tool-use chains). Missing for 10: evidence of multi-step/autonomous task execution, any agent-like planning or tool invocation by the built-in assistant, and independent hands-on validation of these AI features' reliability.
- [claimed-docs] “AI Chats: Start a chat with AI from Explore, or with a keyboard shortcut. You can pass blocks or notes as context.”
- [claimed-docs] “AI Image Analysis: Analyze any image with one click. The AI extracts a title, description, text (OCR, including handwritten text), a color p…”
- [claimed-docs] “Rather than manually filling in the properties of your custom objects, you can rely on the AI model's knowledge to auto-fill them for you.”
- [claimed-docs] “AI features in Capacities are fully opt-in. If you do not activate AI, no data from your spaces is shared with any third-party AI services”
Reflect ships a built-in 'AI palette' that can summarize notes, list action items, answer custom prompts, and let users 'chat' with their notes using GPT-4o or Claude 3.5 Sonnet — a real in-app AI assistant a user can delegate simple analysis/writing tasks to. However, this is limited to text generation/QA over notes rather than broader agentic task execution (no evidence of multi-step autonomous actions, tool use, or task automation beyond note content). Missing for 10: evidence of autonomous multi-step task delegation, agentic tool-use/actions beyond text Q&A, and independent hands-on verification of the AI assistant's reliability.
- [claimed-docs] “List action-items and key takeaways from meeting notes”
- [claimed-docs] “You can also ask the AI palette anything you’d like using the open text field, and save it as a custom prompt to quickly call on again later…”
- [claimed-docs] “To use it, first highlight some text, and then press `cmd j`... That’ll popup the AI palette.”
- [claimed-docs] “You can also **ask the AI palette anything** you’d like using the open text field, and save it as a custom prompt to quickly call on again l…”
- [claimed-docs] “Reflect's AI tools give you the option to now use either GPT-4o (the latest model from OpenAI) or Claude 3.5 Sonnet (the latest model from A…”
- [claimed-docs] “you can also “chat” with those specific notes to ask questions and extract information.”
ai-native userOperate the product with natural-language commands
weight 2 · round drawnCapacities supports AI chats with context, AI property auto-fill, and connects to external AI assistants (ChatGPT, Claude, Cursor) via chat connectors and a live MCP server with read/write scopes, letting AI act as an intermediary for natural-language commands. However, there is no evidence of a native in-app natural-language command palette/interface where a user directly types free-form commands to control the app itself (e.g., 'create a project page and link it to my meeting notes') — the NL interaction is mediated through external AI tools/chat rather than a first-party built-in command layer. missing for 10: first-party in-app natural-language command interface, hands-on evidence of NL commands controlling core app actions (creating/organizing objects) rather than just chat/auto-fill, independent user reports validating this workflow.
- [claimed-docs] “Chat Connectors let you connect AI chat apps, like ChatGPT, Claude, Cursor, or Le Chat, to your Capacities space.”
- [claimed-docs] “AI Chats: Start a chat with AI from Explore, or with a keyboard shortcut. You can pass blocks or notes as context.”
- [claimed-docs] “Rather than manually filling in the properties of your custom objects, you can rely on the AI model's knowledge to auto-fill them for you.”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”
- [claimed-docs] “AI Property Auto-Fill: Rather than manually filling in the properties of your custom objects, you can rely on the AI model's knowledge to au…”
Reflect's AI palette lets users type natural-language prompts to summarize, extract action items, or chat with notes (cmd-j palette, custom prompts), and search supports semantic natural-language queries. However, this NL support is limited to content Q&A/summarization rather than controlling the app's actions—actual app commands are exposed via structured deep-link URLs (reflect://...&command=...) rather than natural language, so full agentic NL control is not evidenced. Missing for 10: evidence of NL commands driving app actions (e.g., creating/organizing notes, triggering integrations) beyond querying/summarizing content, and any independent/hands-on confirmation of this NL interface's reliability.
- [claimed-docs] “You can also ask the AI palette anything you’d like using the open text field, and save it as a custom prompt to quickly call on again later…”
- [claimed-docs] “To use it, first highlight some text, and then press `cmd j`... That’ll popup the AI palette.”
- [claimed-docs] “You can also **ask the AI palette anything** you’d like using the open text field, and save it as a custom prompt to quickly call on again l…”
- [claimed-docs] “you can also “chat” with those specific notes to ask questions and extract information.”
- [claimed-docs] “After applying any desired filters to the search, you can also “chat” with those specific notes to ask questions and extract information.”
- [claimed-docs] “reflect://reflect?command=<command_name>&<parameter1>=<value1>&...”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnCapacitiesnone0/10Evidence confirms a REST API and a machine-readable OpenAPI 3.1 spec exist, but there is no sign of an interactive reference (e.g., Swagger/Redoc UI, try-it-now console, runnable code snippets) — docs are plain markdown reference pages and the openapi.json is only a raw spec file, not an interactive explorer.
- [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.capacities.io/openapi.json, https://docs.capacities.io/swagger.json, https://docs.capac…”
- [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
Reflectnone0/10Reflect's API docs (reflect.academy/api) describe OAuth2 endpoints and PKCE support in prose, but there is no evidence of an interactive API reference with runnable examples — probes confirm no OpenAPI/Swagger spec (404s) and no llms.txt, and nothing in the docs shows a live sandbox or try-it-now console.
- [claimed-docs] “For authentication, we support OAuth 2. You will need to create credentials here.”
- [claimed-docs] “Our supports appending data to your notes, returning a list of the links you've bookmarked, and a few other things.”
- [claimed-docs] “We do support OAuth's PKCE extension which means you can build a client to Reflect without shipping secret keys around.”
- [probe] “PROBE llms.txt: HTTP 404 at https://reflect.academy/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://reflect.academy/openapi.json, https://reflect.academy/swagger.json, https://reflect.academy/…”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless GET to the documented REST base https://reflect.app/api/graphs returned HTTP 401 {"error":{"typ…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round to CapacitiesA live runtime probe confirms Capacities serves a genuine machine-readable OpenAPI 3.1.0 spec at https://api.capacities.io/openapi.json, paired with a working bearer-gated REST API, directly satisfying the story; the docs also describe the REST API and Bearer auth. missing for 10: an explicit documentation page linking to/download-able copy of the spec (the docs subdomain's openapi.json paths 404) and independent/community confirmation of the spec's existence.
- [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
- [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
- [claimed-docs] “The Capacities API uses Bearer authentication (token-based authentication, OAuth 2.0 RFC 6750).”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.capacities.io/openapi.json, https://docs.capacities.io/swagger.json, https://docs.capac…”
Reflectnone0/10Reflect has an API with OAuth2/PKCE docs, but probes confirm no OpenAPI/Swagger spec or machine-readable schema is published (all candidate paths 404, llms.txt 404); documentation is prose-only.
- [probe] “PROBE openapi: all candidate paths 404 (https://reflect.academy/openapi.json, https://reflect.academy/swagger.json, https://reflect.academy/…”
- [probe] “PROBE llms.txt: HTTP 404 at https://reflect.academy/llms.txt”
- [claimed-docs] “For authentication, we support OAuth 2. You will need to create credentials here.”
- [claimed-docs] “We do support OAuth's PKCE extension which means you can build a client to Reflect without shipping secret keys around.”
ai-native userTest against a sandbox environment without touching production data
weight 1 · round drawnCapacitiesnone0/10Capacities' docs describe a production REST API and MCP server with bearer/OAuth auth, but there is no mention of a sandbox, staging, or test space that lets an AI-native developer experiment without touching real production data. Missing for 10: any documented sandbox/staging environment, test API keys, or a dedicated test space feature.
- [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
- [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnCapacitiesnone0/10Evidence confirms Capacities ships a REST API and MCP server, but nothing documents API version numbers, a versioning scheme, or a deprecation policy — the OpenAPI spec is even labeled 'Beta' with no stability guarantees mentioned.
- [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
- [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
Reflectnone0/10The API docs describe OAuth2/PKCE authentication and basic endpoints, but there is no evidence of any versioning scheme (e.g., v1/v2 paths), changelog, or documented deprecation policy anywhere in the docs or probes; OpenAPI/spec probes also 404. missing for 10: API version numbering, changelog/release notes, explicit deprecation policy or backward-compatibility guarantees.
- [claimed-docs] “For authentication, we support OAuth 2. You will need to create credentials here.”
- [claimed-docs] “Our supports appending data to your notes, returning a list of the links you've bookmarked, and a few other things.”
- [claimed-docs] “We do support OAuth's PKCE extension which means you can build a client to Reflect without shipping secret keys around.”
- [probe] “PROBE openapi: all candidate paths 404 (https://reflect.academy/openapi.json, https://reflect.academy/swagger.json, https://reflect.academy/…”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless GET to the documented REST base https://reflect.app/api/graphs returned HTTP 401 {"error":{"typ…”
Ai in notes — stories about ai in notes in this arenaAi in notes
Stories about ai in notes in this arena
Agent ops
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 CapacitiesCapacities ships both a documented REST API (Bearer/OAuth authenticated, verified live with a 401 on keyless access) and an official hosted MCP server at api.capacities.io/mcp with confirmed read AND write scopes (mcp:read mcp:write), enabling headless agent read/write access without the GUI. missing for 10: independent third-party hands-on report of an agent actually using the MCP server end-to-end, and clearer documentation of write-operation specifics/limits in the API docs.
- [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”
- [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
- [claimed-docs] “The Capacities API uses Bearer authentication (token-based authentication, OAuth 2.0 RFC 6750).”
- [probe] “official MCP server documented at https://docs.capacities.io/developer/model-context-protocol”
Reflect documents a real OAuth2/PKCE REST API (confirmed live via runtime probe) that supports appending data to notes and returning bookmarked links, giving agents a write path. However, the same probe notes the API is append-only by design because end-to-end encryption prevents Reflect's servers from reading note content — so headless READ of actual notes is not possible via the documented API, and no MCP server is documented. Missing for 10: a documented way to read/retrieve full note content headlessly, and an official MCP server integration.
- [claimed-docs] “For authentication, we support OAuth 2. You will need to create credentials here.”
- [claimed-docs] “Our supports appending data to your notes, returning a list of the links you've bookmarked, and a few other things.”
- [claimed-docs] “We do support OAuth's PKCE extension which means you can build a client to Reflect without shipping secret keys around.”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless GET to the documented REST base https://reflect.app/api/graphs returned HTTP 401 {"error":{"typ…”
- [claimed-docs] “The contents of your notes are end-to-end encrypted. No one else can read them (not even us).”
Ai assist
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 CapacitiesCapacities ships first-party AI connectors (Chat Connectors for ChatGPT/Claude/Cursor/Le Chat), a documented and runtime-verified hosted MCP server with OAuth scopes, and a REST API confirmed live via OpenAPI probe, giving multiple first-party paths to connect external LLMs/tools to notes. Missing for 10: independent hands-on user reports specifically testing these connectors/MCP server in practice, and evidence of a broader third-party plugin ecosystem beyond the officially listed chat apps.
- [claimed-docs] “Chat Connectors let you connect AI chat apps, like ChatGPT, Claude, Cursor, or Le Chat, to your Capacities space.”
- [claimed-docs] “Build your own app, agent, or bot and integrate it with a Capacities space by implementing a custom MCP client using the Model Context Proto…”
- [probe] “official MCP server documented at https://docs.capacities.io/developer/model-context-protocol”
- [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”
- [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
Reflect ships first-party AI features letting users toggle between GPT-4o and Claude 3.5 Sonnet for in-app AI palette actions (summarize, chat with notes), and exposes an OAuth2/PKCE API for building custom clients. However there's no evidence of a broader plugin ecosystem or first-party connectors letting external AI tools/agents read and act on notes — the API is documented as append-only and scoped narrowly (bookmarks, appending data), not an AI integration surface, and no third-party AI plugin marketplace is mentioned. Missing for 10: a documented AI-plugin ecosystem, evidence of external AI tools consuming notes via API, and richer API scope beyond append-only actions.
- [claimed-docs] “Reflect's AI tools give you the option to now use either GPT-4o (the latest model from OpenAI) or Claude 3.5 Sonnet (the latest model from A…”
- [claimed-docs] “To use it, first highlight some text, and then press `cmd j`... That’ll popup the AI palette.”
- [claimed-docs] “You can also **ask the AI palette anything** you’d like using the open text field, and save it as a custom prompt to quickly call on again l…”
- [claimed-docs] “For authentication, we support OAuth 2. You will need to create credentials here.”
- [claimed-docs] “Our supports appending data to your notes, returning a list of the links you've bookmarked, and a few other things.”
- [claimed-docs] “We do support OAuth's PKCE extension which means you can build a client to Reflect without shipping secret keys around.”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless GET to the documented REST base https://reflect.app/api/graphs returned HTTP 401 {"error":{"typ…”
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 to ReflectDocs confirm a built-in AI Chat that can be grounded on selected notes/blocks as context (capacities-docs-23), AI property auto-fill and image analysis (capacities-docs-24, docs-36), and explicit opt-in/data-sharing controls for AI features (capacities-docs-16). This covers Q&A and grounding-with-control well, but explicit 'summarize' and 'draft' capabilities aren't directly documented, only implied via chat/context features. missing for 10: explicit documentation of summarization/drafting workflows, independent/hands-on user validation of AI answer quality or grounding accuracy.
- [claimed-docs] “AI Chats: Start a chat with AI from Explore, or with a keyboard shortcut. You can pass blocks or notes as context.”
- [claimed-docs] “AI features in Capacities are fully opt-in. If you do not activate AI, no data from your spaces is shared with any third-party AI services”
- [claimed-docs] “AI Image Analysis: Analyze any image with one click. The AI extracts a title, description, text (OCR, including handwritten text), a color p…”
- [claimed-docs] “Rather than manually filling in the properties of your custom objects, you can rely on the AI model's knowledge to auto-fill them for you.”
Docs show a built-in AI palette (cmd-j) that can summarize meeting notes, list action items, answer custom prompts, and 'chat' with filtered/specific notes grounded in the user's own content, with model choice (GPT-4o/Claude 3.5). Data-scoping control is shown via search filters before chatting with a subset of notes, and E2E encryption is claimed for note content, though community evidence notes files/images are excluded from encryption. Missing for 10: independent hands-on review of AI answer quality/grounding, explicit UI controls for restricting AI's data access beyond search filters, and no clarification on how E2E encryption interacts with cloud-based AI processing.
- [claimed-docs] “List action-items and key takeaways from meeting notes”
- [claimed-docs] “you can also “chat” with those specific notes to ask questions and extract information.”
- [claimed-docs] “You can also ask the AI palette anything you’d like using the open text field, and save it as a custom prompt to quickly call on again later…”
- [claimed-docs] “After applying any desired filters to the search, you can also “chat” with those specific notes to ask questions and extract information.”
- [claimed-docs] “To use it, first highlight some text, and then press `cmd j`... That’ll popup the AI palette.”
- [claimed-docs] “You can also **ask the AI palette anything** you’d like using the open text field, and save it as a custom prompt to quickly call on again l…”
- [claimed-docs] “Reflect's AI tools give you the option to now use either GPT-4o (the latest model from OpenAI) or Claude 3.5 Sonnet (the latest model from A…”
- [claimed-docs] “Reflect’s Semantic search lets you find specific pieces of information without knowing the exact words.”
- [claimed-docs] “The contents of your notes are end-to-end encrypted. No one else can read them (not even us).”
- [community] “Question about Reflect's E2E encryption claims: 'We do not end-to-end encrypt things like files or images you upload' - user noted this excl…”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round drawnCapacitiesnone0/10The evidence shows a REST API and MCP server for programmatic access, plus scheduled full exports and selective exports, but nothing documents a bulk/batch operation capability (e.g., batch API endpoints, multi-select bulk edit/tag/delete across many items) that an AI agent could invoke at scale.
- [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
- [claimed-docs] “You can schedule automatic exports by going to Settings > Full Export > Automated Full Export > Add Schedule.”
- [claimed-docs] “Export selected content as Markdown + CSV... In Capacities, go to Settings > Import Content, open the Notion guide in Migration guides, then…”
- [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
Reflectnone0/10Reflect's API supports appending data to individual notes and returning bookmark lists, but there is no evidence of any bulk/batch operation capability (e.g., batch update, multi-note transformation, or scripted bulk edits across many items at once); the API is explicitly append-only per note due to E2E encryption.
- [claimed-docs] “Our supports appending data to your notes, returning a list of the links you've bookmarked, and a few other things.”
- [claimed-docs] “We do support OAuth's PKCE extension which means you can build a client to Reflect without shipping secret keys around.”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless GET to the documented REST base https://reflect.app/api/graphs returned HTTP 401 {"error":{"typ…”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round drawnCapacitiesnone0/10Capacities offers an API, MCP server, and AI assistant features, but no evidence of a rules/trigger engine (event-based automation like 'when X happens, do Y') exists in the docs pack—only manual actions, scheduled exports, and AI-assisted fill-in features are documented.
Capture editing — stories about capture editing in this arenaCapture editing
Stories about capture editing in this arena
Capture
researcherClip web pages, articles, and highlights from my browser straight into my notes with an official clipper or capture flow
weight 2 · round to ReflectCapacitiesnone0/10No evidence pack item mentions a browser extension, web clipper, or article/highlight capture flow for Capacities; the closest features are generic content-type ingestion and a mobile app for 'capture on the go', not a browser clipper. This is a reasonable axis for a note-taking/knowledge-base app (competitors ship clippers), so absence of evidence means 'none' rather than 'na'.
- [claimed-docs] “The mobile app is a companion to desktop for day-to-day work in your space: search and capture on the go.”
- [claimed-docs] “Any image you input into Capacities becomes an image object, that can be reused anywhere in your space.”
- [claimed-docs] “Object types are either created automatically by Capacities, or you can create them yourself. The first group is what we call Basic Object T…”
Reflect ships an official Chrome and Safari browser extension for bookmarking websites, capturing snippets, and highlights, which are automatically added to the daily note — directly matching the researcher's clipper/capture workflow. Documentation is detailed and first-party; missing for 10: independent hands-on review specifically validating the clipper extension's reliability/quality.
- [claimed-docs] “Reflect lets you quickly bookmark websites and capture snippets from across the web using our Chrome extension”
- [claimed-docs] “The link and your highlights will automatically be added to your daily note.”
- [claimed-docs] “Reflect lets you quickly bookmark websites and capture snippets from across the web using our Chrome extension and Safari extension.”
Daily notes
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 ReflectCapacities docs confirm a native daily-note concept uniquely linked to each day for quick capture (capacities-docs-21) and a general templates feature that can pre-fill properties and blocks in objects (capacities-docs-9), and daily notes surface backlinked references automatically (capacities-docs-8). However, the docs never explicitly confirm that a template is auto-applied to the daily note by default or that the daily note is the default landing page/capture surface on app open. Missing for 10: explicit documentation of template-to-daily-note binding, and confirmation that the daily note is the default landing view.
- [claimed-docs] “A daily note is a note that is uniquely linked to one day. It often serves as a quick and simple way to write down ideas or things to rememb…”
- [claimed-docs] “Templates allow you to prefill the content of an object- you can prefill properties and blocks in your objects.”
- [claimed-docs] “The next section shows all references of that day, including objects with properties to that day and mentions of the day in your writing.”
Reflect's docs explicitly confirm automatic daily notes created every day as the journaling landing place, and multiple features (voice transcription, bookmarking, calendar sync, integrations) are documented as auto-filling into that daily note, showing it's the default capture surface. Missing for 10: explicit confirmation of a customizable daily-note *template* pre-filling structure/content, and independent hands-on verification of the daily-note experience beyond docs.
- [claimed-docs] “Tools like Reflect will create a new _daily note_ for you everyday for you to journal in.”
- [claimed-docs] “Tools like Reflect will create a new daily note for you everyday for you to journal in.”
- [claimed-docs] “Speak your note, then click stop recording... their transcription will be added to your daily note.”
- [claimed-docs] “The link and your highlights will automatically be added to your daily note.”
- [claimed-docs] “We support connecting your Google, iCloud and Office 365 account(s) to Reflect. This lets you: Pull in your calendar events, so you can easi…”
- [claimed-docs] “Add Trello cards or Asana tasks to your Daily Note”
- [claimed-docs] “Add Trello cards or Asana tasks to your Daily Note Add Google Docs and Slack notes to Reflect Save emails and Tweets to your notes Sync your…”
Editor
power-userDefine reusable templates (with variables like date and title) and apply them when creating recurring kinds of notes
weight 2 · round to CapacitiesCapacities docs confirm a template system that lets you prefill properties and blocks of an object type, which supports reusable templates for recurring note kinds (e.g., Meetings, Projects) as suggested by the object-type-first workflow. However, no evidence describes dynamic variable insertion (e.g., auto-filled current date or title placeholders) within templates. Missing for 10: explicit documentation of variable/placeholder support (date, title, etc.) in templates and independent hands-on confirmation of this behavior.
- [claimed-docs] “Templates allow you to prefill the content of an object- you can prefill properties and blocks in your objects.”
- [claimed-docs] “Object types are either created automatically by Capacities, or you can create them yourself. The first group is what we call Basic Object T…”
- [claimed-docs] “Capacities is object-type-first. Define key object types early (`People`, `Projects`, `Meetings`, etc.) and add core properties.”
Reflectnone0/10The evidence pack shows daily notes, backlinks, tags, filters, imports, and AI palette features, but nowhere mentions reusable note templates with variable substitution (e.g., date/title placeholders) for creating recurring note types. Missing for 10: any documentation of a templates feature, variable/placeholder syntax, or ability to save/apply templates to new notes.
power-userWrite and format notes with headings, callouts, tables, code blocks, and embedded media in a fast keyboard-driven editor
weight 2 · round drawnCapacitiesnone0/10The evidence pack covers linking, templates, object types, and AI features but never documents core editor formatting elements (headings, callouts, tables, code blocks) or keyboard-driven editing speed/shortcuts, so this applicable power-user capability has no supporting evidence.
Reflectnone0/10The evidence pack covers linking/backlinks, daily notes, import/export in Markdown, AI features, and encryption, but contains no documentation or community evidence about core rich-text editing capabilities such as headings, callouts, tables, code blocks, or embedded media, nor about keyboard-driven editing speed. Missing for 10: any docs mentioning headings/callout blocks/tables/code blocks/embedded media support, and any evidence of keyboard-shortcut-driven formatting workflow.
Import export — stories about import export in this arenaImport export
Stories about import export in this arena
Migration
switcherExport my entire knowledge base at any time in open formats, so leaving is as easy as arriving
weight 2 · round to ReflectCapacities documents a native Full Export feature (Settings > Full Export) that can be run on demand or scheduled automatically, exporting content as Markdown with properties as front matter and collections as CSV files explicitly 'to reuse your content in other apps or work with it programmatically' — both open, portable formats satisfying a switcher's exit needs. Missing for 10: independent/hands-on verification of export completeness (media, attachments, block-references, backlinks fidelity) and confirmation this covers the entire space rather than only selected content in the documented flows.
- [claimed-docs] “You can schedule automatic exports by going to Settings > Full Export > Automated Full Export > Add Schedule.”
- [claimed-docs] “All your properties are transformed into front matter values, all collections are stored as CSV files, making it easy to reuse your content …”
- [claimed-docs] “Export selected content as Markdown + CSV... In Capacities, go to Settings > Import Content, open the Notion guide in Migration guides, then…”
- [claimed-docs] “Export only the selected content you intend to migrate. Use Markdown + CSV as your default format for this flow.”
Reflect explicitly documents export into open formats (HTML, Markdown) at any time, and the founder corroborates this as an anti-lock-in feature in community discussion. missing for 10: independent hands-on verification of a full/bulk knowledge-base export (vs per-note export) and confirmation that all note types/attachments are included.
- [claimed-docs] “you can always export it into an open format (like HTML or Markdown).”
- [community] “Reflect founder on data lock-in: 'you can always export your notes into markdown or HTML so you shouldn't feel too locked in.' Also noted th…”
switcherImport my existing notes from Notion, Evernote, Roam, or plain Markdown with structure, links, and attachments preserved
weight 3 · round to ReflectDocs provide a detailed Notion-to-Capacities migration guide (curate structure, export as Markdown+CSV, define object types before import) which covers the Notion import path, but there is no evidence at all for importing from Evernote or Roam, and no confirmation that links/attachments are preserved on import (the export docs describe front matter/CSV output going out of Capacities, not import fidelity). missing for 10: Evernote import support, Roam import support, plain Markdown import instructions, explicit evidence that internal links/backlinks and attachments survive the import process, independent/hands-on reports confirming fidelity.
- [claimed-docs] “Migrate from Notion by curating structure before export.”
- [claimed-docs] “Export selected content as Markdown + CSV... In Capacities, go to Settings > Import Content, open the Notion guide in Migration guides, then…”
- [claimed-docs] “Capacities is object-type-first. Define key object types early (`People`, `Projects`, `Meetings`, etc.) and add core properties.”
- [claimed-docs] “Export only the selected content you intend to migrate. Use Markdown + CSV as your default format for this flow.”
- [claimed-docs] “All your properties are transformed into front matter values, all collections are stored as CSV files, making it easy to reuse your content …”
Reflect's docs confirm native import support for Evernote (ENEX), Roam (JSON), and Markdown files, three of the four sources named in the story, plus Apple Notes and Workflowy. However, Notion import is not mentioned anywhere in the import/export documentation, and there is no explicit confirmation that internal links or attachments are preserved through the import process for any of these formats. Missing for 10: Notion import support, explicit evidence that links and attachments (not just note text) survive import.
- [claimed-docs] “We currently support imports from: Apple Notes (HTML) Evernote (ENEX) Markdown files Roam (JSON) Workflowy (OPML)”
- [claimed-docs] “We currently support imports from: * Apple Notes (HTML) * Evernote (ENEX) * Markdown files * Roam (JSON) * Workflowy (OPML)”
- [claimed-docs] “First you’ll have to export your existing Apple Notes using the provided script below, then import them into Reflect normally.”
- [claimed-docs] “you can always export it into an open format (like HTML or Markdown).”
Linking graph — stories about linking graph in this arenaLinking graph
Stories about linking graph in this arena
Graph
researcherExplore my knowledge base as an interactive graph of notes and connections, filtered to what I care about
weight 1 · round to CapacitiesCapacities has a documented Graph View that visualizes an object's links as a network showing the 'local neighbourhood' around the open note, which supports interactive graph exploration of the knowledge base. However, the evidence never describes any filtering mechanism (by tag, type, date, or search term) within the graph view itself, so the 'filtered to what I care about' part of the story is unevidenced. missing for 10: documented graph filtering/faceting by object type, tag, or search query, and any independent hands-on account of using filters in graph view.
- [claimed-docs] “Graph view shows how one object connects to others. Each link between notes becomes a line in the graph”
- [claimed-docs] “Graph view shows how one object connects to others. Each link between notes becomes a line in the graph, so you can see the local neighbourh…”
- [claimed-docs] “All backlinks are grouped together at the bottom of your object in a section titled "Backlinks".”
- [claimed-docs] “Capacities lets you link to individual blocks inside of an object, and reference them in other pages. We call this concept block-based linki…”
Reflectnone0/10Reflect's docs describe backlinks, [[ ]] linking, and filtering notes by tags/date/backlinks, but nowhere is an interactive visual graph view of the knowledge base mentioned or shown — the evidence only covers list-style backlinks and search filters, not a graph exploration UI.
- [claimed-docs] “Networked note-taking tools, like Reflect, support creating links between notes... backlinks”
- [claimed-docs] “Backlinks are just a list of incoming links from other notes.”
- [claimed-docs] “You can filter notes by: Date created or updated, Daily Notes, Where they are backlinked to/from, #tags, Pinned notes”
- [claimed-docs] “You can filter notes by: Date created or updated Daily Notes Where they are backlinked to/from #tags Pinned notes”
- [claimed-docs] “You can filter notes by: * Date created or updated * Daily Notes * Where they are backlinked to/from * #tags * Pinned notes”
Links
researcherLink notes with [[wiki-style]] links and see every backlink and unlinked mention of a note in context
weight 3 · round to ReflectDocs confirm backlinks are grouped in a dedicated 'Backlinks' section on each object and graph view shows links between notes, and daily notes show 'mentions of the day in your writing,' but there is no explicit mention of [[wiki-style]] link syntax or a general unlinked-mention detection feature across regular notes (only for daily notes). missing for 10: explicit [[wiki-link]] syntax documentation, a general unlinked-mentions panel for all object types, and independent/hands-on confirmation of in-context backlink previews.
- [claimed-docs] “All backlinks are grouped together at the bottom of your object in a section titled "Backlinks".”
- [claimed-docs] “Graph view shows how one object connects to others. Each link between notes becomes a line in the graph”
- [claimed-docs] “The next section shows all references of that day, including objects with properties to that day and mentions of the day in your writing.”
- [claimed-docs] “Graph view shows how one object connects to others. Each link between notes becomes a line in the graph, so you can see the local neighbourh…”
- [claimed-docs] “A daily note is a note that is uniquely linked to one day. It often serves as a quick and simple way to write down ideas or things to rememb…”
Docs confirm [[ ]] wiki-link shortcut, backlinks as incoming links, and filtering notes by where they're backlinked to/from, covering the core linking-graph story. However, evidence never explicitly mentions detection/surfacing of 'unlinked mentions' in context, which is a specific part of the story. Missing for 10: explicit unlinked-mention detection/surfacing, independent hands-on demonstration of backlink UI in context.
- [claimed-docs] “Networked note-taking tools, like Reflect, support creating links between notes... backlinks”
- [claimed-docs] “Generally note-taking tools, including Reflect, use the `[[` shortcut to link some text.”
- [claimed-docs] “Backlinks are just a list of incoming links from other notes.”
- [claimed-docs] “You can filter notes by: Date created or updated, Daily Notes, Where they are backlinked to/from, #tags, Pinned notes”
- [claimed-docs] “You can filter notes by: Date created or updated Daily Notes Where they are backlinked to/from #tags Pinned notes”
- [claimed-docs] “You can filter notes by: * Date created or updated * Daily Notes * Where they are backlinked to/from * #tags * Pinned notes”
power-userReference or transclude an individual block or section of one note inside another and have it stay in sync
weight 2 · round to CapacitiesCapacities explicitly supports block-based linking/embedding (block references) where an embedded block is identical to the original and edits propagate everywhere it's used, plus backlinks and graph view to surface these connections — directly matching the transclusion-stays-in-sync story. Missing for 10: independent hands-on verification of sync behavior across notes and any documented limits (e.g., section-level vs single-block granularity).
- [claimed-docs] “Capacities lets you link to individual blocks inside of an object, and reference them in other pages.”
- [claimed-docs] “Capacities lets you link to individual blocks inside of an object, and reference them in other pages. We call this concept block-based linki…”
- [claimed-docs] “An embedded block is identical to the original. This means that any edits will occur in all places where this block is used.”
- [claimed-docs] “All backlinks are grouped together at the bottom of your object in a section titled "Backlinks".”
- [claimed-docs] “Graph view shows how one object connects to others. Each link between notes becomes a line in the graph, so you can see the local neighbourh…”
Reflectnone0/10Evidence shows Reflect supports note-to-note linking and backlinks ([[ shortcuts, backlinks list) but nowhere documents block- or section-level transclusion/embedding that stays synced across notes — only whole-note linking and filtering by backlink is described.
- [claimed-docs] “Networked note-taking tools, like Reflect, support creating links between notes... backlinks”
- [claimed-docs] “Generally note-taking tools, including Reflect, use the `[[` shortcut to link some text.”
- [claimed-docs] “Backlinks are just a list of incoming links from other notes.”
Local first ownership — stories about local first ownership in this arenaLocal first ownership
Stories about local first ownership in this arena
Ownership
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 to CapacitiesCapacities documents offline-first behavior (work offline, sync when back online, offline search) and a full/scheduled export to Markdown+CSV/front-matter that is 'easy to reuse... work with programmatically,' giving some data ownership. However, there is no evidence the primary store is plain local files usable without the app day-to-day — the live working format is the app's own sync/cloud store, and export is a periodic snapshot rather than the native storage format. Missing for 10: evidence of a genuine local-first primary file format (e.g. markdown files on disk that the app just syncs), and confirmation that full functionality (not just search) works offline without any cloud dependency.
- [claimed-docs] “Capacities is an offline-first application. You can work offline and your changes will get synchronized as soon as you're back online.”
- [claimed-docs] “You can work offline and your changes will get synchronized as soon as you're back online.”
- [claimed-docs] “Search in Capacities is great for navigation, finding, and connecting your content. It works offline on all devices, giving you quick search…”
- [claimed-docs] “You can schedule automatic exports by going to Settings > Full Export > Automated Full Export > Add Schedule.”
- [claimed-docs] “All your properties are transformed into front matter values, all collections are stored as CSV files, making it easy to reuse your content …”
- [claimed-docs] “Export selected content as Markdown + CSV... In Capacities, go to Settings > Import Content, open the Notion guide in Migration guides, then…”
- [claimed-docs] “Export only the selected content you intend to migrate. Use Markdown + CSV as your default format for this flow.”
Reflectnone0/10Reflect is a cloud-synced, end-to-end-encrypted note service (docs-16/35) with export-to-Markdown/HTML available (docs-44, comm-7), but there is no evidence notes are stored as local files or in a local-first store the user can read without the app, nor evidence of full offline functionality — the API and encryption model imply server-mediated sync rather than local-first ownership.
- [claimed-docs] “End-to-end encryption keeps your notes secure.”
- [claimed-docs] “The contents of your notes are end-to-end encrypted. No one else can read them (not even us).”
- [claimed-docs] “you can always export it into an open format (like HTML or Markdown).”
- [community] “Reflect founder on data lock-in: 'you can always export your notes into markdown or HTML so you shouldn't feel too locked in.' Also noted th…”
- [community] “Question about Reflect's E2E encryption claims: 'We do not end-to-end encrypt things like files or images you upload' - user noted this excl…”
researcherMy notes are stored or exportable in open, documented formats (Markdown, JSON) so my archive outlives the vendor
weight 2 · round to ReflectCapacities documents a full, schedulable export to Markdown (with front matter) plus CSV for collections, explicitly stated to make content reusable in other apps or programmatically ('capacities-docs-11','capacities-docs-31'), alongside a REST API for direct data access ('capacities-docs-33'). This gives researchers a genuine open-format escape hatch beyond vendor lock-in. Missing for 10: independent/hands-on verification of export completeness and fidelity (e.g., whether all object types and block-links survive the export), and confirmation that the 'Full Export' truly captures the entire space rather than only selected/migration content.
- [claimed-docs] “You can schedule automatic exports by going to Settings > Full Export > Automated Full Export > Add Schedule.”
- [claimed-docs] “All your properties are transformed into front matter values, all collections are stored as CSV files, making it easy to reuse your content …”
- [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
- [claimed-docs] “Export selected content as Markdown + CSV... In Capacities, go to Settings > Import Content, open the Notion guide in Migration guides, then…”
- [claimed-docs] “Migrate from Notion by curating structure before export.”
Reflect explicitly documents export to open formats (Markdown, HTML) and import from Markdown/JSON-based formats, and the founder publicly confirms notes can always be exported to Markdown/HTML to avoid lock-in. Missing for 10: no independent hands-on verification of export fidelity/completeness, and export format is somewhat limited (HTML/Markdown only, not full JSON archive of all metadata).
- [claimed-docs] “We currently support imports from: Apple Notes (HTML) Evernote (ENEX) Markdown files Roam (JSON) Workflowy (OPML)”
- [claimed-docs] “We currently support imports from: * Apple Notes (HTML) * Evernote (ENEX) * Markdown files * Roam (JSON) * Workflowy (OPML)”
- [claimed-docs] “you can always export it into an open format (like HTML or Markdown).”
- [community] “Reflect founder on data lock-in: 'you can always export your notes into markdown or HTML so you shouldn't feel too locked in.' Also noted th…”
Self host
developerRun the whole system without the vendor's cloud — local-only mode or a self-hosted sync backend I operate myself
weight 2 · round drawnCapacitiesnone0/10Capacities is offline-first (local caching with sync) but all evidence shows sync and API/MCP endpoints run through the vendor's own cloud (api.capacities.io); there is no documented self-hosted sync backend or fully local-only mode without vendor infrastructure. Missing for 10: any option to self-host sync server, any documented local-only deployment mode, independent confirmation of running without vendor cloud.
- [claimed-docs] “Capacities is an offline-first application. You can work offline and your changes will get synchronized as soon as you're back online.”
- [claimed-docs] “You can work offline and your changes will get synchronized as soon as you're back online.”
- [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”
Reflectnone0/10Reflect is a cloud-hosted, closed-source SaaS with E2E encryption on the vendor's servers — there is no evidence of a local-only mode or self-hostable sync backend; only export to Markdown/HTML for backup is documented, not operating your own sync server.
- [claimed-docs] “you can always export it into an open format (like HTML or Markdown).”
- [community] “Reflect founder on data lock-in: 'you can always export your notes into markdown or HTML so you shouldn't feel too locked in.' Also noted th…”
- [claimed-docs] “The contents of your notes are end-to-end encrypted. No one else can read them (not even us).”
Mobile capture — stories about mobile capture in this arenaMobile capture
Stories about mobile capture in this arena
Mobile
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 drawnCapacitiesnone0/10The only description of the mobile app in the evidence pack is Capacities' own docs stating it is 'a companion to desktop for day-to-day work... search and capture on the go' — this explicitly frames mobile as a stripped-down companion, not a full-featured app with linking/graph/backlinks parity, and no evidence shows block-based linking, graph view, or full object-type editing on iOS/Android. missing for 10: any documentation or reports of full linking/graph/template features on mobile, evidence that mobile isn't limited to search+capture, independent hands-on confirmation of mobile feature parity.
- [claimed-docs] “The mobile app is a companion to desktop for day-to-day work in your space: search and capture on the go.”
Reflectnone0/10The evidence pack covers imports, API, AI features, publishing, security, and integrations extensively, but contains no mention of iOS or Android apps, their feature set, or mobile-specific capture/search/linking capabilities. Without any documentation or community evidence describing dedicated mobile apps (full-featured or otherwise), there is nothing to substantiate this story.
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to CapacitiesCapacities ships a documented REST API (with a live OpenAPI spec) and an official hosted MCP server with both read and write scopes, letting programmatic clients create/manipulate content and integrate agents — a real API-driven workflow, not just a UI. However, no evidence shows the API/MCP exposes UI-only features like AI property auto-fill, AI image analysis, chat connectors, graph view, or templates, so full UI-API parity is not demonstrated. Missing for 10: confirmation that AI assistant features, graph view, templates, and chat connector functionality are all reachable via API/MCP, and independent hands-on verification of API completeness.
- [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
- [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”
- [claimed-docs] “Build your own app, agent, or bot and integrate it with a Capacities space by implementing a custom MCP client using the Model Context Proto…”
Reflect does expose an OAuth2/PKCE REST API confirmed live via runtime probe, but by its own docs it only supports appending data to notes and returning bookmarked links plus 'a few other things' — a small subset of UI capabilities (semantic search, AI chat, publishing, backlinks, calendar/integrations, deep links) with no evidence these are API-accessible. The API is also explicitly append-only for note content since E2E encryption prevents server-side reads, meaning even reading/editing existing notes via API is not possible as it is in the UI. Missing for 10: API endpoints for search/AI features, note reading/editing, publishing, and integrations parity with the UI.
- [claimed-docs] “For authentication, we support OAuth 2. You will need to create credentials here.”
- [claimed-docs] “Our supports appending data to your notes, returning a list of the links you've bookmarked, and a few other things.”
- [claimed-docs] “We do support OAuth's PKCE extension which means you can build a client to Reflect without shipping secret keys around.”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless GET to the documented REST base https://reflect.app/api/graphs returned HTTP 401 {"error":{"typ…”
- [claimed-docs] “Reflect’s Semantic search lets you find specific pieces of information without knowing the exact words.”
- [claimed-docs] “Reflect offers one-click publishing of your notes. Simply hit the publish button and your note will be publicly available behind a long hard…”
ai-native userExport all of my data in open formats and leave
weight 3 · round drawnCapacities offers full/selective export to open Markdown+CSV formats (front matter, CSV collections) explicitly designed for reuse in other apps or programmatic work, plus scheduled automated full exports, giving users a genuine 'export and leave' path. missing for 10: no independent/hands-on verification that exported data is fully lossless (e.g., all block references, embeds, graph links preserved) and no evidence of bulk data deletion/account closure workflow alongside export.
- [claimed-docs] “You can schedule automatic exports by going to Settings > Full Export > Automated Full Export > Add Schedule.”
- [claimed-docs] “All your properties are transformed into front matter values, all collections are stored as CSV files, making it easy to reuse your content …”
- [claimed-docs] “Export only the selected content you intend to migrate. Use Markdown + CSV as your default format for this flow.”
- [claimed-docs] “Export selected content as Markdown + CSV... In Capacities, go to Settings > Import Content, open the Notion guide in Migration guides, then…”
Reflect explicitly documents export to open formats (HTML, Markdown) and the founder confirms this is a deliberate anti-lock-in policy, directly matching the story. missing for 10: no independent hands-on verification of a full data export/migration, and export is confined to notes (E2E-encrypted files/images may not be fully portable per reflect-comm-8).
- [claimed-docs] “you can always export it into an open format (like HTML or Markdown).”
- [claimed-docs] “We currently support imports from: Apple Notes (HTML) Evernote (ENEX) Markdown files Roam (JSON) Workflowy (OPML)”
- [community] “Reflect founder on data lock-in: 'you can always export your notes into markdown or HTML so you shouldn't feel too locked in.' Also noted th…”
- [community] “Question about Reflect's E2E encryption claims: 'We do not end-to-end encrypt things like files or images you upload' - user noted this excl…”
ai-native userRead the product's source under an open license
weight 2 · round drawnCapacitiesnone0/10No evidence of Capacities' source code being open-licensed or publicly available; it is a closed, proprietary SaaS/app with a documented API and MCP server, but no open-source repository or license is mentioned anywhere in the evidence.
ai-native userSelf-host the core product
weight 3 · round drawnCapacitiesnone0/10The 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.)
Organization retrieval — stories about organization retrieval in this arenaOrganization retrieval
Stories about organization retrieval in this arena
Metadata
power-userAttach typed properties and tags to notes and use them consistently for organization and retrieval
weight 2 · round to CapacitiesCapacities is explicitly object-type-first, letting users define custom object types with typed properties (front-matter on export) and tags, with AI auto-fill for properties, and search/graph/backlinks for retrieval; a HN commenter corroborates that all content becomes taggable, reusable entities in a network of notes. missing for 10: independent hands-on validation of complex multi-property queries/filtering at scale and more detailed docs on tag hierarchies or property types beyond basic examples.
- [claimed-docs] “Object types are either created automatically by Capacities, or you can create them yourself. The first group is what we call Basic Object T…”
- [claimed-docs] “Capacities is object-type-first. Define key object types early (`People`, `Projects`, `Meetings`, etc.) and add core properties.”
- [claimed-docs] “Object types are either created automatically by Capacities, or you can create them yourself.”
- [claimed-docs] “AI Property Auto-Fill: Rather than manually filling in the properties of your custom objects, you can rely on the AI model's knowledge to au…”
- [claimed-docs] “Rather than manually filling in the properties of your custom objects, you can rely on the AI model's knowledge to auto-fill them for you.”
- [claimed-docs] “All your properties are transformed into front matter values, all collections are stored as CSV files, making it easy to reuse your content …”
- [claimed-docs] “Search in Capacities is designed to return useful results even when your wording is not exact.”
- [claimed-docs] “Search in Capacities is great for navigation, finding, and connecting your content. It works offline on all devices, giving you quick search…”
- [community] “Have been using it for a while now, there are really some cool new concepts... all media is automatically treated as an entity that can be r…”
Reflect clearly supports tags (#tags) for organization and retrieval, including automatic tagging (e.g. Kindle imports tagged #book) and filtering notes by #tags, backlinks, dates, and pinned status. However, there is no evidence of 'typed properties' (structured metadata fields with types, akin to database properties) — Reflect's organization model is built around tags, backlinks, and daily notes, not typed property schemas. Missing for 10: evidence of typed/structured properties (not just tags), evidence of consistent property schemas across notes, and any UI for defining property types.
- [claimed-docs] “You can filter notes by: Date created or updated, Daily Notes, Where they are backlinked to/from, #tags, Pinned notes”
- [claimed-docs] “You can filter notes by: Date created or updated Daily Notes Where they are backlinked to/from #tags Pinned notes”
- [claimed-docs] “You can filter notes by: * Date created or updated * Daily Notes * Where they are backlinked to/from * #tags * Pinned notes”
- [claimed-docs] “Reflect can automatically sync your books, highlights, and comments from your Kindle. They will be imported into Reflect as individual notes…”
- [claimed-docs] “Reflect can automatically sync your books, highlights, and comments from your Kindle. They will be imported into Reflect as individual notes…”
Queries
power-userQuery my notes by their structured properties and render live database-style views (tables, boards, lists) from those queries
weight 3 · round to CapacitiesCapacities clearly supports structured object types with custom properties (docs-26, docs-29, docs-35) and lists 'Smart queries' as a paid feature (docs-27), implying some query capability over properties, but there is no documentation describing table/board/list view rendering, filtering/sorting UI, or database-style views comparable to Notion databases. missing for 10: explicit documentation of query views (table/board/list), filter/sort UI, examples of rendering query results as live views.
- [claimed-docs] “Task management, AI assistant, Calendar integrations, Smart queries, Task actions”
- [claimed-docs] “Object types are either created automatically by Capacities, or you can create them yourself. The first group is what we call Basic Object T…”
- [claimed-docs] “Capacities is object-type-first. Define key object types early (`People`, `Projects`, `Meetings`, etc.) and add core properties.”
- [claimed-docs] “Object types are either created automatically by Capacities, or you can create them yourself.”
Reflectnone0/10Reflect only supports basic filtering (tags, dates, backlinks, pinned) per reflect-docs-15/22/27, with no evidence of structured/typed properties, query language, or database-style table/board/list views like Notion or Roam-style databases. No documentation or community evidence mentions live queryable views rendered from structured properties.
- [claimed-docs] “You can filter notes by: Date created or updated, Daily Notes, Where they are backlinked to/from, #tags, Pinned notes”
- [claimed-docs] “You can filter notes by: Date created or updated Daily Notes Where they are backlinked to/from #tags Pinned notes”
- [claimed-docs] “You can filter notes by: * Date created or updated * Daily Notes * Where they are backlinked to/from * #tags * Pinned notes”
Search
researcherInstantly search all my notes with full-text search plus filters on tags, properties, and paths — including offline
weight 3 · round drawnDocs confirm full-text search that works offline and tolerates inexact wording (capacities-docs-10, capacities-docs-22, capacities-docs-13, capacities-docs-37), and object types/tags/properties exist as structural concepts (capacities-docs-26, capacities-docs-35). However, no evidence documents explicit search filters/query syntax for tags, properties, or paths specifically. Missing for 10: documented filter syntax or UI for narrowing search by tag/property/path, independent hands-on confirmation of filtered search results.
- [claimed-docs] “Search in Capacities is designed to return useful results even when your wording is not exact.”
- [claimed-docs] “Search in Capacities is great for navigation, finding, and connecting your content. It works offline on all devices, giving you quick search…”
- [claimed-docs] “Capacities is an offline-first application. You can work offline and your changes will get synchronized as soon as you're back online.”
- [claimed-docs] “You can work offline and your changes will get synchronized as soon as you're back online.”
- [claimed-docs] “Object types are either created automatically by Capacities, or you can create them yourself. The first group is what we call Basic Object T…”
Reflect documents semantic + full-text search with filters on tags, backlinks, date, daily notes, and pinned status (reflect-docs-6,15,22,27,41), covering most of the story. However, no explicit filter on "properties" (beyond tags) or "paths" is documented, and offline capability/search-while-offline is never mentioned anywhere in the evidence. Missing for 10: explicit property-based filtering, path-based filtering, and any documentation of offline search support.
- [claimed-docs] “Reflect’s Semantic search lets you find specific pieces of information without knowing the exact words.”
- [claimed-docs] “You can filter notes by: Date created or updated, Daily Notes, Where they are backlinked to/from, #tags, Pinned notes”
- [claimed-docs] “You can filter notes by: Date created or updated Daily Notes Where they are backlinked to/from #tags Pinned notes”
- [claimed-docs] “You can filter notes by: * Date created or updated * Daily Notes * Where they are backlinked to/from * #tags * Pinned notes”
- [claimed-docs] “Reflect's Semantic search lets you find specific pieces of information without knowing the exact words.”
- [claimed-docs] “After applying any desired filters to the search, you can also “chat” with those specific notes to ask questions and extract information.”
Plugins extensibility — stories about plugins extensibility in this arenaPlugins extensibility
Stories about plugins extensibility in this arena
Automation hooks
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 to ReflectCapacities exposes a documented REST API (Bearer-auth, OpenAPI spec verified live) that lets developers create and manipulate content programmatically, which satisfies the 'local endpoint' part of the story for scripting/automation. However, there is no evidence of a URI scheme or deep-link mechanism for opening/creating notes from other apps, only a hosted (not local) API and MCP server. Missing for 10: documented URI scheme or deep-link support, evidence of a local (non-cloud) endpoint, and independent confirmation of scripting workflows beyond the API docs.
- [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
- [claimed-docs] “The Capacities API uses Bearer authentication (token-based authentication, OAuth 2.0 RFC 6750).”
- [claimed-docs] “The Capacities API uses Bearer authentication (token-based authentication, OAuth 2.0 RFC 6750)”
- [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
Reflect ships a documented custom URI scheme (reflect://reflect?command=...) for deep linking into the app, plus a REST API with OAuth2/PKCE authentication that a runtime probe confirms is live and enforcing auth, letting developers script note creation/appending from outside the app. missing for 10: independent/hands-on developer confirmation of building an external integration, and full endpoint/command reference beyond the docs snippets.
- [claimed-docs] “Reflect supports deep linking, allowing users to perform actions within the app using custom URLs.”
- [claimed-docs] “reflect://reflect?command=<command_name>&<parameter1>=<value1>&...”
- [claimed-docs] “For authentication, we support OAuth 2. You will need to create credentials here.”
- [claimed-docs] “Our supports appending data to your notes, returning a list of the links you've bookmarked, and a few other things.”
- [claimed-docs] “We do support OAuth's PKCE extension which means you can build a client to Reflect without shipping secret keys around.”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless GET to the documented REST base https://reflect.app/api/graphs returned HTTP 401 {"error":{"typ…”
Plugins
power-userBrowse and install from a large catalog of community plugins/extensions to add features the core app doesn't ship
weight 3 · round drawnCapacitiesnone0/10The 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.)
Reflectnone0/10There is no evidence of a plugin/extension marketplace; instead community evidence explicitly states Reflect is designed to be 'fully functional without any plugins' as a differentiator from Obsidian, indicating no such catalog exists.
- [community] “What drew me to Reflect (away from Obsidian) was full functionality out of the box without the need for plugins... Reflect is fully function…”
developerBuild my own plugins against a documented extension API/SDK with samples and developer docs
weight 2 · round to CapacitiesCapacities exposes a documented REST API (with OpenAPI spec, verified live) and an MCP integration standard for building external agents/bots/clients, which covers part of the 'extend Capacities programmatically' story, but there is no evidence of a true in-app plugin architecture/SDK, plugin samples, or a plugin marketplace — the docs describe API/MCP client integration rather than installable plugins running inside the product. missing for 10: dedicated plugin SDK/framework, code samples for building in-app plugins, plugin distribution/marketplace docs.
- [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
- [claimed-docs] “Build your own app, agent, or bot and integrate it with a Capacities space by implementing a custom MCP client”
- [claimed-docs] “Build your own app, agent, or bot and integrate it with a Capacities space by implementing a custom MCP client using the Model Context Proto…”
- [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”
- [probe] “official MCP server documented at https://docs.capacities.io/developer/model-context-protocol”
Reflectnone0/10Reflect documents a limited OAuth2 REST API for appending data/links and deep-linking (reflect-docs-2,17,18,38), but this is not a plugin extension SDK, and community evidence explicitly states Reflect is 'fully functional without any plugins' by design, unlike Obsidian (reflect-comm-2). No plugin architecture, extension samples, or plugin developer docs exist.
- [claimed-docs] “Our supports appending data to your notes, returning a list of the links you've bookmarked, and a few other things.”
- [claimed-docs] “We do support OAuth's PKCE extension which means you can build a client to Reflect without shipping secret keys around.”
- [community] “What drew me to Reflect (away from Obsidian) was full functionality out of the box without the need for plugins... Reflect is fully function…”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round drawnCapacitiesnone0/10No evidence anywhere in the pack mentions data residency, region selection, or where user data is physically stored; docs cover offline-first sync and AI opt-in privacy but never data location choice. Missing for 10: any documentation of region/residency selection, server location options, or data hosting jurisdiction controls.
- [claimed-docs] “Capacities is an offline-first application. You can work offline and your changes will get synchronized as soon as you're back online.”
- [claimed-docs] “AI features in Capacities are fully opt-in. If you do not activate AI, no data from your spaces is shared with any third-party AI services”
ai-native userPrevent my data from being used to train AI models
weight 3 · round to CapacitiesCapacities explicitly documents that AI features are opt-in and that no data is shared with third-party AI services unless a user activates AI features, directly addressing the training-data-prevention story. missing for 10: no independent/third-party audit or hands-on verification of the no-training-data claim beyond vendor documentation.
- [claimed-docs] “AI features in Capacities are fully opt-in. If you do not activate AI, no data from your spaces is shared with any third-party AI services”
Reflectnone0/10Reflect advertises end-to-end encryption of note content (reflect-docs-16, reflect-docs-35), which limits Reflect's own server-side access, but there is no explicit statement anywhere in the evidence about whether note content sent to third-party AI models (GPT-4o, Claude 3.5 Sonnet per reflect-docs-37) is used for model training, nor any opt-out/data-processing policy addressing AI training use. Community evidence even notes files/images are excluded from E2E encryption (reflect-comm-8), raising unaddressed questions rather than resolving them.
- [claimed-docs] “End-to-end encryption keeps your notes secure.”
- [claimed-docs] “The contents of your notes are end-to-end encrypted. No one else can read them (not even us).”
- [claimed-docs] “Reflect's AI tools give you the option to now use either GPT-4o (the latest model from OpenAI) or Claude 3.5 Sonnet (the latest model from A…”
- [community] “Question about Reflect's E2E encryption claims: 'We do not end-to-end encrypt things like files or images you upload' - user noted this excl…”
ai-native userControl data retention and deletion
weight 2 · round drawnCapacitiesnone0/10Evidence covers AI opt-in privacy (docs-16), offline/export features, and API auth, but there is no documentation of data retention policies, deletion controls, or account/data-deletion mechanisms specific to AI usage.
- [claimed-docs] “AI features in Capacities are fully opt-in. If you do not activate AI, no data from your spaces is shared with any third-party AI services”
- [claimed-docs] “You can schedule automatic exports by going to Settings > Full Export > Automated Full Export > Add Schedule.”
- [claimed-docs] “All your properties are transformed into front matter values, all collections are stored as CSV files, making it easy to reuse your content …”
ai-native userOpt out of telemetry and usage tracking
weight 2 · round to CapacitiesCapacities docs state that AI features are fully opt-in and no space data is shared with third-party AI services unless activated, which gives users control over AI-related data sharing, but there is no evidence of a general telemetry/usage-analytics opt-out setting for the app itself. Missing for 10: explicit documentation of a general telemetry/analytics opt-out toggle, independent confirmation that the app collects no usage data when opted out.
- [claimed-docs] “AI features in Capacities are fully opt-in. If you do not activate AI, no data from your spaces is shared with any third-party AI services”
Reflectnone0/10No evidence pack item discusses telemetry, analytics, usage tracking, or an opt-out/privacy settings toggle for such tracking; the evidence covers encryption, imports, AI features, and API access instead. Missing for 10: any mention of telemetry collection, opt-out settings, or a privacy policy addressing usage tracking.
Publish sharing — stories about publish sharing in this arenaPublish sharing
Stories about publish sharing in this arena
Publish
researcherPublish selected notes as a browsable website — a digital garden with working links — without leaving the app
weight 2 · round to ReflectCapacitiesnone0/10No evidence of any public-publishing or website/digital-garden export feature; Capacities offers only view-only sharing access, local export to Markdown/CSV, and APIs/MCP for integrations, none of which produce a browsable public website with working links.
- [claimed-docs] “Grant others view-only access to notes”
- [claimed-docs] “All your properties are transformed into front matter values, all collections are stored as CSV files, making it easy to reuse your content …”
- [claimed-docs] “You can schedule automatic exports by going to Settings > Full Export > Automated Full Export > Add Schedule.”
Reflect docs confirm one-click publishing of individual notes to a public URL with minimal branding, which supports sharing selected notes without leaving the app, but there is no evidence of a browsable multi-page 'digital garden' site (index/navigation) or confirmation that backlinks between published notes remain functional as working links. Missing for 10: evidence of a site-level index/navigation across multiple published notes, confirmation that internal links/backlinks resolve correctly between published pages, and any custom-domain or site-branding options.
- [claimed-docs] “Reflect offers one-click publishing of your notes. Simply hit the publish button and your note will be publicly available behind a long hard…”
- [claimed-docs] “We try to keep the style clean and branding to a minimum.”
- [claimed-docs] “Backlinks are just a list of incoming links from other notes.”
Sync collaboration — stories about sync collaboration in this arenaSync collaboration
Stories about sync collaboration in this arena
Collaboration
researcherShare a vault or space with collaborators and edit notes together without stepping on each other's changes
weight 2 · round to CapacitiesThe only sharing capability documented is view-only access to notes for others (capacities-docs-28), not true multi-user collaborative editing or conflict-free simultaneous editing of a shared vault/space. There is no evidence of real-time co-editing, presence indicators, or conflict resolution mechanisms that would let collaborators edit together without stepping on each other's changes. Missing for 10: real-time collaborative editing support, multi-editor conflict resolution, shared-space edit permissions beyond view-only, and any community/hands-on corroboration of team editing.
- [claimed-docs] “Grant others view-only access to notes”
Reflectnone0/10No evidence pack item mentions shared vaults/spaces, multi-user collaboration, or real-time co-editing/conflict resolution; Reflect's documented features are import/export, linking, AI, search, publishing, integrations, and E2E encryption for a single user's notes, with no mention of collaborative editing between multiple people.
Sync
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 ReflectCapacitiesnone0/10There is evidence of offline-first sync ('changes get synchronized as soon as you're back online') but no mention anywhere of end-to-end encryption of sync data or a vendor-can't-read architecture; encryption claims are absent from docs, pricing, or community sources.
- [claimed-docs] “Capacities is an offline-first application. You can work offline and your changes will get synchronized as soon as you're back online.”
- [claimed-docs] “You can work offline and your changes will get synchronized as soon as you're back online.”
Reflectdisputedcontradicted5/10Reflect markets end-to-end encryption 'no one else can read them (not even us)' and syncs notes across devices as a core feature, but a founder-sourced community comment reveals a concrete carve-out: files/images uploaded are NOT end-to-end encrypted, contradicting the blanket vendor claim. Missing for 10: explicit documentation of sync architecture/conflict resolution across devices, independent security audit report details, and a full accounting of what content types are/aren't encrypted.
- [claimed-docs] “End-to-end encryption keeps your notes secure.”
- [claimed-docs] “The contents of your notes are end-to-end encrypted. No one else can read them (not even us).”
- [community] “Question about Reflect's E2E encryption claims: 'We do not end-to-end encrypt things like files or images you upload' - user noted this excl…”
- [community] “Reflect founder: 'We're building it as a lifestyle company. There's only four of us. We bootstrapped for a while, and then did a $1m crowdfu…”
- [community] “Props to Reflect for their security audit too. I will be keeping an eye on how they progress.”
power-userView a note's version history and restore earlier versions or recover deleted notes
weight 2 · round to ReflectCapacitiesnone0/10No evidence anywhere in the pack of a version history feature or a way to recover deleted notes; documentation covers export, offline sync, linking, AI, and API but never mentions version history or trash/recovery.
Reflect's documentation explicitly states it continually records edits and lets users revert a note to any point in time, directly matching the version history/restore story (docs-8). Deleted note recovery isn't explicitly documented, so missing for 10: explicit documentation of deleted-note recovery/trash restoration, and independent hands-on corroboration of restore functionality.
- [claimed-docs] “We continually record edits to notes which means you can see all your changes and revert a note to any point in time.”
Not comparable on these axes
ai-native userSchedule recurring jobs or workflows
weight 2 · not comparableCapacitiesnone0/10No evidence of any scheduling, cron-style triggers, or recurring workflow/automation capability aside from a manual 'automated full export' schedule which is not a general job/workflow scheduler; the API, MCP server, and AI features shown are all synchronous/manual, not recurring triggers for workflows.
- [claimed-docs] “You can schedule automatic exports by going to Settings > Full Export > Automated Full Export > Add Schedule.”
- [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
- [probe] “PROBE runtime (recorded 2026-09-05): https://api.capacities.io/openapi.json served a machine-readable OpenAPI 3.1.0 spec ('Capacities API (B…”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”
Reflectn/aReflect is a personal note-taking/journaling app, not an automation/workflow platform; there is no scheduler, cron, or recurring-job concept in its feature set (daily notes are manually created journaling prompts, not scheduled jobs). Scheduling recurring workflows is a category error for this product type.
- [claimed-docs] “Tools like Reflect will create a new _daily note_ for you everyday for you to journal in.”
- [claimed-docs] “Tools like Reflect will create a new daily note for you everyday for you to journal in.”
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableCapacitiesnone0/10Capacities documents templates, an API, and an MCP server for integrations, but nothing in the evidence describes an automation-building feature (workflows/triggers/actions) let alone version history, review, or rollback for such automations.
- [claimed-docs] “Templates allow you to prefill the content of an object- you can prefill properties and blocks in your objects.”
- [claimed-docs] “The Capacities API is a REST API that allows you access, create and manipulate your content.”
- [probe] “PROBE runtime (recorded 2026-09-05): keyless JSON-RPC initialize POST to the official hosted MCP server https://api.capacities.io/mcp return…”
Reflectn/aReflect is a note-taking/knowledge-management app with API, integrations, and note history (version/revert notes), but it has no automation/workflow-building feature (e.g., triggers/actions pipelines) that could be versioned, reviewed, or rolled back — the axis doesn't apply to this product category.