How SoloKeys Solo 2’s scores are calculated

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://docs.solokeys.dev/llms.txt“PROBE llms.txt: HTTP 404 at https://docs.solokeys.dev/llms.txt”
• [probe] https://docs.solokeys.dev/.md“PROBE docs-md: HTTP 404 at https://docs.solokeys.dev/.md”
• [probe] https://docs.solokeys.dev/openapi.json“PROBE openapi: all candidate paths 404 (https://docs.solokeys.dev/openapi.json, https://docs.solokeys.dev/swagger.json, https://docs.solokeys.dev/api/openapi.json, https://docs.solokeys.dev/.well-known/openapi.json)”
• [probe] https://solokeys.com/llms.txt“PROBE runtime (recorded 2026-09-15): solokeys.com serves an llms.txt ('# Agent Instructions — SoloKeys'), but it is Shopify's platform-generated shopping-agent file for the store (it recommends the shop.app SKILL.md) — NOT product or technical documentation. docs.solokeys.dev has no llms.txt (404).”

Run the product headlessly / in CI for automationweight 2

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

• [claimed-docs] https://solokeys.com/“When prompted, touch the capacitive sensor on your Solo 2 to confirm.”
• [github] https://github.com/solokeys/solo2“solo2 list # list connected devices (alias: solo2 ls)”
• [probe] https://github.com/solokeys/solo1-cli“PROBE runtime negative (recorded 2026-09-15): the official Solo CLI has bit-rotted — `uvx --from solo-python solo version` fails with 'ImportError: cannot import name CTAP1 from fido2.ctap1' (solo-python 0.1.1 is incompatible with current python-fido2 2.x), and the last tagged Solo 2 firmware release is 2.964.0 from 2022-08-25. Repos still receive dependency/CI commits (Aug 2026), but no firmware release in 4 years.”

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

n/a — not applicable to this product: excluded from numerator and denominator

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

Connect an agent via an official MCP serverweight 3

n/a — not applicable to this product: excluded from numerator and denominator

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

Use an official CLIweight 2

2 (weight) × 3 (quality) × 0.3 (disputed) = 1.8 of 20 max

• [github] https://github.com/solokeys/solo2“solo2 app admin set led 007f7f 00007f # set led to teal (idle) / blue (active) - use 000000 to turn the led off”
• [github] https://github.com/solokeys/solo2“solo2 list # list connected devices (alias: solo2 ls)”
• [claimed-docs] https://docs.solokeys.dev/building/“solo monitor <serial-port>”
• [claimed-docs] https://github.com/solokeys/solo2/releases“You can "wipe" a device using `fido2-token -R`”
• [probe] https://github.com/solokeys/solo1-cli“PROBE runtime negative (recorded 2026-09-15): the official Solo CLI has bit-rotted — `uvx --from solo-python solo version` fails with 'ImportError: cannot import name CTAP1 from fido2.ctap1' (solo-python 0.1.1 is incompatible with current python-fido2 2.x), and the last tagged Solo 2 firmware release is 2.964.0 from 2022-08-25. Repos still receive dependency/CI commits (Aug 2026), but no firmware release in 4 years.”

Drive the product through a documented public APIweight 3

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

• [probe] https://docs.solokeys.dev/openapi.json“PROBE openapi: all candidate paths 404 (https://docs.solokeys.dev/openapi.json, https://docs.solokeys.dev/swagger.json, https://docs.solokeys.dev/api/openapi.json, https://docs.solokeys.dev/.well-known/openapi.json)”
• [probe] https://docs.solokeys.dev/llms.txt“PROBE llms.txt: HTTP 404 at https://docs.solokeys.dev/llms.txt”
• [probe] https://github.com/solokeys/solo1-cli“PROBE runtime negative (recorded 2026-09-15): the official Solo CLI has bit-rotted — `uvx --from solo-python solo version` fails with 'ImportError: cannot import name CTAP1 from fido2.ctap1' (solo-python 0.1.1 is incompatible with current python-fido2 2.x), and the last tagged Solo 2 firmware release is 2.964.0 from 2022-08-25. Repos still receive dependency/CI commits (Aug 2026), but no firmware release in 4 years.”
• [probe] https://solokeys.com/llms.txt“PROBE runtime (recorded 2026-09-15): solokeys.com serves an llms.txt ('# Agent Instructions — SoloKeys'), but it is Shopify's platform-generated shopping-agent file for the store (it recommends the shop.app SKILL.md) — NOT product or technical documentation. docs.solokeys.dev has no llms.txt (404).”

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

n/a — not applicable to this product: excluded from numerator and denominator

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

Build against official SDKsweight 2

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

• [claimed-docs] https://docs.solokeys.dev/building/“To build, develop and debug the firmware for the STM32L432.”
• [claimed-docs] https://hackmd.io/@solokeys/solo2-getting-started“rustup target install thumbv8m.main-none-eabi cargo install flip-link cargo install cargo-binutils cargo install probe-rs-tools”
• [github] https://github.com/solokeys/solo2“On a **Hacker** key you can build and flash your own firmware.”
• [probe] https://github.com/solokeys/solo1-cli“PROBE runtime negative (recorded 2026-09-15): the official Solo CLI has bit-rotted — `uvx --from solo-python solo version` fails with 'ImportError: cannot import name CTAP1 from fido2.ctap1' (solo-python 0.1.1 is incompatible with current python-fido2 2.x), and the last tagged Solo 2 firmware release is 2.964.0 from 2022-08-25. Repos still receive dependency/CI commits (Aug 2026), but no firmware release in 4 years.”
• [probe] https://docs.solokeys.dev/openapi.json“PROBE openapi: all candidate paths 404 (https://docs.solokeys.dev/openapi.json, https://docs.solokeys.dev/swagger.json, https://docs.solokeys.dev/api/openapi.json, https://docs.solokeys.dev/.well-known/openapi.json)”

Subscribe to events via webhooksweight 2

n/a — not applicable to this product: excluded from numerator and denominator

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

Explore an interactive API reference with runnable examplesweight 2

n/a — not applicable to this product: excluded from numerator and denominator

• [probe] https://docs.solokeys.dev/openapi.json“PROBE openapi: all candidate paths 404 (https://docs.solokeys.dev/openapi.json, https://docs.solokeys.dev/swagger.json, https://docs.solokeys.dev/api/openapi.json, https://docs.solokeys.dev/.well-known/openapi.json)”
• [github] https://github.com/solokeys/solo2“solo2 list # list connected devices (alias: solo2 ls)”

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

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

• [probe] https://docs.solokeys.dev/openapi.json“PROBE openapi: all candidate paths 404 (https://docs.solokeys.dev/openapi.json, https://docs.solokeys.dev/swagger.json, https://docs.solokeys.dev/api/openapi.json, https://docs.solokeys.dev/.well-known/openapi.json)”
• [probe] https://docs.solokeys.dev/llms.txt“PROBE llms.txt: HTTP 404 at https://docs.solokeys.dev/llms.txt”
• [probe] https://solokeys.com/llms.txt“PROBE runtime (recorded 2026-09-15): solokeys.com serves an llms.txt ('# Agent Instructions — SoloKeys'), but it is Shopify's platform-generated shopping-agent file for the store (it recommends the shop.app SKILL.md) — NOT product or technical documentation. docs.solokeys.dev has no llms.txt (404).”

Test against a sandbox environment without touching production dataweight 1

n/a — not applicable to this product: excluded from numerator and denominator

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

Rely on versioned APIs with a documented deprecation policyweight 2

n/a — not applicable to this product: excluded from numerator and denominator

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

Do everything through the API that I can do in the UIweight 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

Export all of my data in open formats and leaveweight 3

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

• [claimed-docs] https://github.com/solokeys/solo2/releases“You can "wipe" a device using `fido2-token -R`”
• [github] https://github.com/solokeys/solo2“It's a USB+NFC device that protects your accounts with passkeys/WebAuthn, and also speaks OATH (TOTP/HOTP), PIV, and OpenPGP.”
• [claimed-docs] https://docs.solokeys.dev/customization/“If you don't want to use the default attestation key that Solo builds with, you can create your own and program it.”
• [claimed-docs] https://docs.solokeys.dev/customization/“Now to generate & sign the attestation key pair that will go on your device, or maybe 100,000 devices :)”

Read the product's source under an open licenseweight 2

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

• [github] https://github.com/solokeys/solo2“Solo 2 Hacker — the same hardware, unlocked. Flash your own firmware, experiment with new features, and learn how a security key works end to end.”
• [github] https://github.com/solokeys/solo2“On a **Hacker** key you can build and flash your own firmware.”
• [github] https://github.com/solokeys/solo2“It's a USB+NFC device that protects your accounts with passkeys/WebAuthn, and also speaks OATH (TOTP/HOTP), PIV, and OpenPGP.”
• [claimed-docs] https://docs.solokeys.dev/building/“To build, develop and debug the firmware for the STM32L432.”
• [community] https://news.ycombinator.com/item?id=26118571“This is an LPC55S69. So it's open source firmware, not open source hardware.”

Self-host the core productweight 3

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

• [github] https://github.com/solokeys/solo2“Solo 2 Hacker — the same hardware, unlocked. Flash your own firmware, experiment with new features, and learn how a security key works end to end.”
• [github] https://github.com/solokeys/solo2“On a **Hacker** key you can build and flash your own firmware.”
• [claimed-docs] https://docs.solokeys.dev/customization/“If you don't want to use the default attestation key that Solo builds with, you can create your own and program it.”
• [claimed-docs] https://docs.solokeys.dev/building/“To build, develop and debug the firmware for the STM32L432.”
• [claimed-docs] https://hackmd.io/@solokeys/solo2-getting-started“rustup target install thumbv8m.main-none-eabi cargo install flip-link cargo install cargo-binutils cargo install probe-rs-tools”
• [claimed-docs] https://hackmd.io/@solokeys/solo2-getting-started“cargo build --release --features board-lpcxpresso55,develop”
• [probe] https://github.com/solokeys/solo1-cli“PROBE runtime negative (recorded 2026-09-15): the official Solo CLI has bit-rotted — `uvx --from solo-python solo version` fails with 'ImportError: cannot import name CTAP1 from fido2.ctap1' (solo-python 0.1.1 is incompatible with current python-fido2 2.x), and the last tagged Solo 2 firmware release is 2.964.0 from 2022-08-25. Repos still receive dependency/CI commits (Aug 2026), but no firmware release in 4 years.”

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

n/a — not applicable to this product: excluded from numerator and denominator

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

Set up automations that run autonomously in the backgroundweight 2

n/a — not applicable to this product: excluded from numerator and denominator

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

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

n/a — not applicable to this product: excluded from numerator and denominator

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

Operate the product with natural-language commandsweight 2

n/a — not applicable to this product: excluded from numerator and denominator

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

Perform bulk operations across many items at onceweight 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

Define rules that trigger actions automatically on eventsweight 3

n/a — not applicable to this product: excluded from numerator and denominator

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

Schedule recurring jobs or workflowsweight 2

n/a — not applicable to this product: excluded from numerator and denominator

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

Version, review, and roll back my automationsweight 1

n/a — not applicable to this product: excluded from numerator and denominator

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