Skip to content

How Logseq’s scores are calculated

The full audit trail, recomputed from the verdict data at build time through the same code that produced the leaderboard: verdict × quality × story weight per cell, cells sum to dimension scores, dimensions blend into the PA Score. Every number on the product page is reproducible from this page alone; for why the formula looks like this, see the methodology.

verdict factors: full ×1.0 · partial ×0.6 · disputed ×0.3 · none ×0.0 · n/a excluded from both sides · cell points = weight × quality × factor · cell max = weight × 10

PA Score11/100

Agent-ready 8.6 × 0.30 = 2.58

API quality 0.0 × 0.20 = 0.00

Openness 38.2 × 0.20 = 7.64

Built-in AI 0.0 × 0.15 = 0.00

Automation 6.0 × 0.15 = 0.90

(2.58 + 0.00 + 7.64 + 0.00 + 0.90) ÷ (0.30 + 0.20 + 0.20 + 0.15 + 0.15) = 11.12 ÷ 1.00 = 11.1

Scores are stored to 1 decimal; the product page’s pills round to whole numbers for display. Each dimension below shows the stories, verdicts, and cited evidence behind its number.

Agent-ready8.6/100×0.30 of the PA blend

Outside-in: can YOUR agent reach and drive this product — API, MCP, CLI, headless runs, agent docs.

Point an agent at llms.txt or agent-oriented docsweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [probe] https://plugins-doc.logseq.com/llms.txtPROBE llms.txt: HTTP 404 at https://plugins-doc.logseq.com/llms.txt
  • [probe] https://plugins-doc.logseq.com/openapi.jsonPROBE openapi: all candidate paths 404 (https://plugins-doc.logseq.com/openapi.json, https://plugins-doc.logseq.com/swagger.json, https://plugins-doc.logseq.com/api/openapi.json, https://plugins-doc.logseq.com/.well-known/openapi.json)

Run the product headlessly / in CI for automationweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Local%20Http%20server.mdlocal HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Local%20Http%20server.mdwe developed the local HTTP server to support external access to the database through authorization.
  • [claimed-docs] https://logseq.comLogseq: A privacy-first, open-source knowledge base

Plug MCP servers into this product so it can use their toolsweight 3

3 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 30 max

  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Plugins.mdExtends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated and removed.
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Local%20Http%20server.mdlocal HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Local%20Http%20server.mdwe developed the local HTTP server to support external access to the database through authorization.
  • [community] https://hn.algolia.com/api/v1/items/48896229I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as possible. Not being able to use Claude or codex anymore to write or update pages is a real deal breaker for me.

Connect an agent via an official MCP serverweight 3

3 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 30 max

  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Local%20Http%20server.mdlocal HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Local%20Http%20server.mdwe developed the local HTTP server to support external access to the database through authorization.
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Plugins.mdExtends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated and removed.

Use an official CLIweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Drive the product through a documented public APIweight 3

3 (weight) × 6 (quality) × 0.6 (partial) = 10.8 of 30 max

  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Local%20Http%20server.mdlocal HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Local%20Http%20server.mdwe developed the local HTTP server to support external access to the database through authorization.
  • [claimed-docs] https://plugins-doc.logseq.comThis is a community-driven documentation for Logseq plugin APIs.
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Logseq%20Protocol.mdLogseq provides a protocol `logseq://` to allow third party applications to invoke actions within Logseq.
  • [probe] https://plugins-doc.logseq.com/llms.txtPROBE llms.txt: HTTP 404 at https://plugins-doc.logseq.com/llms.txt
  • [probe] https://plugins-doc.logseq.com/openapi.jsonPROBE openapi: all candidate paths 404 (https://plugins-doc.logseq.com/openapi.json, https://plugins-doc.logseq.com/swagger.json, https://plugins-doc.logseq.com/api/openapi.json, https://plugins-doc.logseq.com/.well-known/openapi.json)
  • [community] https://hn.algolia.com/api/v1/items/48896229I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as possible. Not being able to use Claude or codex anymore to write or update pages is a real deal breaker for me.

Issue scoped/least-privilege API credentials for an agentweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Local%20Http%20server.mdlocal HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Local%20Http%20server.mdwe developed the local HTTP server to support external access to the database through authorization.
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Local%20Http%20server.mdlocal HTTP server to access logseq's graph

Build against official SDKsweight 2

2 (weight) × 6 (quality) × 0.6 (partial) = 7.2 of 20 max

  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Plugins.mdExtends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated and removed.
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Local%20Http%20server.mdlocal HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`
  • [claimed-docs] https://plugins-doc.logseq.comThis is a community-driven documentation for Logseq plugin APIs.
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Local%20Http%20server.mdwe developed the local HTTP server to support external access to the database through authorization.
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Logseq%20Protocol.mdLogseq provides a protocol `logseq://` to allow third party applications to invoke actions within Logseq.
  • [probe] https://github.com/logseq/marketplacePROBE runtime (recorded 2026-09-05): Logseq's official plugin marketplace registry (logseq/marketplace, one directory per package) counted 617 published packages keylessly via the GitHub contents API — the in-app Marketplace is registry-verified.
  • [probe] https://plugins-doc.logseq.com/llms.txtPROBE llms.txt: HTTP 404 at https://plugins-doc.logseq.com/llms.txt
  • [probe] https://plugins-doc.logseq.com/openapi.jsonPROBE openapi: all candidate paths 404 (https://plugins-doc.logseq.com/openapi.json, https://plugins-doc.logseq.com/swagger.json, https://plugins-doc.logseq.com/api/openapi.json, https://plugins-doc.logseq.com/.well-known/openapi.json)

Subscribe to events via webhooksweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Agent-ready = 18.0 ÷ 210 × 100 = 8.6

API quality0.0/100×0.20 of the PA blend

The programmable surface once an agent is there — machine-readable spec, interactive docs, sandbox, versioning discipline.

Explore an interactive API reference with runnable examplesweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [claimed-docs] https://plugins-doc.logseq.comThis is a community-driven documentation for Logseq plugin APIs.
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Local%20Http%20server.mdlocal HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`
  • [probe] https://plugins-doc.logseq.com/llms.txtPROBE llms.txt: HTTP 404 at https://plugins-doc.logseq.com/llms.txt
  • [probe] https://plugins-doc.logseq.com/openapi.jsonPROBE openapi: all candidate paths 404 (https://plugins-doc.logseq.com/openapi.json, https://plugins-doc.logseq.com/swagger.json, https://plugins-doc.logseq.com/api/openapi.json, https://plugins-doc.logseq.com/.well-known/openapi.json)

Download a machine-readable API spec (OpenAPI or equivalent)weight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Local%20Http%20server.mdlocal HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`
  • [claimed-docs] https://plugins-doc.logseq.comThis is a community-driven documentation for Logseq plugin APIs.
  • [probe] https://plugins-doc.logseq.com/llms.txtPROBE llms.txt: HTTP 404 at https://plugins-doc.logseq.com/llms.txt
  • [probe] https://plugins-doc.logseq.com/openapi.jsonPROBE openapi: all candidate paths 404 (https://plugins-doc.logseq.com/openapi.json, https://plugins-doc.logseq.com/swagger.json, https://plugins-doc.logseq.com/api/openapi.json, https://plugins-doc.logseq.com/.well-known/openapi.json)

Test against a sandbox environment without touching production dataweight 1

1 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 10 max

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Rely on versioned APIs with a documented deprecation policyweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Local%20Http%20server.mdlocal HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Local%20Http%20server.mdwe developed the local HTTP server to support external access to the database through authorization.
  • [probe] https://plugins-doc.logseq.com/llms.txtPROBE llms.txt: HTTP 404 at https://plugins-doc.logseq.com/llms.txt
  • [probe] https://plugins-doc.logseq.com/openapi.jsonPROBE openapi: all candidate paths 404 (https://plugins-doc.logseq.com/openapi.json, https://plugins-doc.logseq.com/swagger.json, https://plugins-doc.logseq.com/api/openapi.json, https://plugins-doc.logseq.com/.well-known/openapi.json)
  • [community] https://hn.algolia.com/api/v1/items/48896229I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as possible. Not being able to use Claude or codex anymore to write or update pages is a real deal breaker for me.

API quality = 0.0 ÷ 70 × 100 = 0.0

Openness38.2/100×0.20 of the PA blend

Can you leave, inspect, or self-host — data export, open source, portability.

Do everything through the API that I can do in the UIweight 2

2 (weight) × 4 (quality) × 0.3 (disputed) = 2.4 of 20 max

  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Local%20Http%20server.mdlocal HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Local%20Http%20server.mdwe developed the local HTTP server to support external access to the database through authorization.
  • [claimed-docs] https://plugins-doc.logseq.comThis is a community-driven documentation for Logseq plugin APIs.
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Logseq%20Protocol.mdLogseq provides a protocol `logseq://` to allow third party applications to invoke actions within Logseq.
  • [community] https://hn.algolia.com/api/v1/items/48896229I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as possible. Not being able to use Claude or codex anymore to write or update pages is a real deal breaker for me.

Export all of my data in open formats and leaveweight 3

3 (weight) × 6 (quality) × 0.6 (partial) = 10.8 of 30 max

  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Export.mdThe Logseq Export feature allows users to export their data in various formats, including text, HTML, OPML, PNG, EDN, JSON, and standard Markdown.
  • [community] https://news.ycombinator.com/item?id=33218561The MarkDown files it generates aren't compatible with other similar programs (Obsidian for instance). It adds 2 spaces which makes things incompatible with others.
  • [community] https://hn.algolia.com/api/v1/items/48896229Logseq remained a buggy mess, is now on an unmaintained (thus insecure) version of electron. And now after several years of complete stagnation, the supposed improvement is a database format to fix their technical issues, so I can no longer keep all my data as markdown files?

Read the product's source under an open licenseweight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

  • [claimed-docs] https://logseq.comLogseq: A privacy-first, open-source knowledge base
  • [community] https://hn.algolia.com/api/v1/items/33218561I use Logseq personally and for work almost daily since a year ago or so. It's pretty nice and the 'least bad' PKM platform I'm aware of (no mandatory subscription, local data and source availability are important factors).

Self-host the core productweight 3

3 (weight) × 5 (quality) × 0.6 (partial) = 9.0 of 30 max

  • [claimed-docs] https://logseq.comLogseq: A privacy-first, open-source knowledge base
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Local%20Http%20server.mdlocal HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Local%20Http%20server.mdwe developed the local HTTP server to support external access to the database through authorization.
  • [community] https://news.ycombinator.com/item?id=33218561I know Logseq is intended as an offline-first solution, but I really wish I could self-host it as a website and have all notes saved on my server... there's an open issue on github for the same feature request... but there are currently 1.8k open issues.
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Logseq%20Sync.mdSyncs up to 10 graphs between Logseq Desktop, Android, and iOS.
  • [community] https://hn.algolia.com/api/v1/items/33218561Logseq's own sync is now in testing and you can access it if you're a sponsor ($15/month tier)... It works fine but has enough bugs that I wouldn't rely on it yet - but they are responsive to fixing the bugs that we report.

Openness = 38.2 ÷ 100 × 100 = 38.2

Built-in AI0.0/100×0.15 of the PA blend

Inside-out: how agentic the product itself is for its users — built-in assistants, autonomous features.

Get AI-generated insights and suggestions from my data inside the productweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [community] https://hn.algolia.com/api/v1/items/48896229I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as possible. Not being able to use Claude or codex anymore to write or update pages is a real deal breaker for me.
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Queries.mdSimple queries by using `{{query }}`, the format is something like this: {{query Something you're looking for}}
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Queries.mdQueries are for asking questions from your knowledge base and the outside world (in the future).

Set up automations that run autonomously in the backgroundweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Plugins.mdExtends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated and removed.
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Local%20Http%20server.mdlocal HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Local%20Http%20server.mdwe developed the local HTTP server to support external access to the database through authorization.
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Logseq%20Protocol.mdLogseq provides a protocol `logseq://` to allow third party applications to invoke actions within Logseq.

Delegate tasks to a built-in AI assistant inside the productweight 3

3 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 30 max

  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Plugins.mdExtends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated and removed.
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Local%20Http%20server.mdlocal HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`
  • [community] https://hn.algolia.com/api/v1/items/48896229I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as possible. Not being able to use Claude or codex anymore to write or update pages is a real deal breaker for me.

Operate the product with natural-language commandsweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [community] https://hn.algolia.com/api/v1/items/48896229I've got so much already in logseq though, and I really like the model. Right now I'm thinking I'll just stay on version one as long as possible. Not being able to use Claude or codex anymore to write or update pages is a real deal breaker for me.
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Plugins.mdExtends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated and removed.
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Queries.mdQueries are for asking questions from your knowledge base and the outside world (in the future).

Built-in AI = 0.0 ÷ 90 × 100 = 0.0

Automation6.0/100×0.15 of the PA blend

Depth of automation primitives — rules, scheduling, bulk operations, webhooks.

Perform bulk operations across many items at onceweight 2

2 (weight) × 4 (quality) × 0.6 (partial) = 4.8 of 20 max

  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Queries.mdSimple queries by using `{{query }}`, the format is something like this: {{query Something you're looking for}}
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Queries.mdSimple queries by using `{{query }}`... You can type `/query` to create a simple query.
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Queries.mdQueries are for asking questions from your knowledge base and the outside world (in the future).
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Local%20Http%20server.mdlocal HTTP server to access logseq's graph ... Enable HTTP APIs server in `Features > HTTP APIs server`
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Local%20Http%20server.mdwe developed the local HTTP server to support external access to the database through authorization.
  • [claimed-docs] https://plugins-doc.logseq.comThis is a community-driven documentation for Logseq plugin APIs.

Define rules that trigger actions automatically on eventsweight 3

3 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 30 max

  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Plugins.mdExtends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated and removed.
  • [claimed-docs] https://plugins-doc.logseq.comThis is a community-driven documentation for Logseq plugin APIs.
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Logseq%20Protocol.mdLogseq provides a protocol `logseq://` to allow third party applications to invoke actions within Logseq.

Schedule recurring jobs or workflowsweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Version, review, and roll back my automationsweight 1

1 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 10 max

  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Plugins.mdExtends the functionality of logseq with third party tools ... third-party plugins from the Marketplace, can be searched, installed, updated and removed.
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Plugins.mdFrom this dashboard, third-party plugins from the [[Marketplace]], can be searched, installed, updated and removed.
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Plugins.mdExtends the functionality of logseq with third party tools ... third-party plugins from the [[Marketplace]], can be searched, installed, updated and removed.
  • [claimed-docs] https://raw.githubusercontent.com/logseq/docs/master/pages/Plugins.mdthird-party plugins from the [[Marketplace]], can be searched, installed, updated and removed.

Automation = 4.8 ÷ 80 × 100 = 6.0