Feitian FIDO Keys vs Token2

Agent access

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

   weight 2 · round drawn
   Feitian FIDO Keys—none0/10

   Feitian is a hardware FIDO key vendor with no evidence of an llms.txt or agent-oriented documentation; probes explicitly show 404s for llms.txt, markdown docs, and OpenAPI endpoints.

   • [probe] “PROBE llms.txt: HTTP 404 at https://fido.ftsafe.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://fido.ftsafe.com/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://fido.ftsafe.com/openapi.json, https://fido.ftsafe.com/swagger.json, https://fido.ftsafe.com/…”

   proof ↗⚑ flag

   Token2—none0/10

   Direct probes show no llms.txt (404) and no markdown-accessible docs (404), and no OpenAPI/agent-oriented documentation exists; Token2 is a hardware security key vendor with no evidence of agent-discoverable docs.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.token2.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.token2.com/site/page/tools-for-fido-security-keys.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.token2.com/openapi.json, https://www.token2.com/swagger.json, https://www.token2.com/api…”

   proof ↗⚑ flag

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

   weight 2 · round to Token2
   Feitian FIDO Keys—none0/10

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

   ⚑ flag

   Token2~partialprobed4/10

   Token2 ships a PowerShell bulk-enrollment script (fido2_bulkenroll_entraid) that could in principle be scripted/automated, and fido2-manage exposes some command-line-style operations (PIN, SSH key management) beyond its Python/tkinter GUI, suggesting some automation potential. However, the flagship tool is explicitly GUI-based and requires physical FIDO2 hardware interaction over USB/NFC, and there is no documented headless mode, CI integration, or automation-focused CLI/API (no OpenAPI, no llms.txt, no CI examples). Missing for 10: dedicated headless/CI-mode documentation, evidence of non-interactive scripted runs without physical key presence, and any CI/pipeline integration guide.

   • [claimed-docs] “This tool streamlines the process of registering FIDO2 security keys in Microsoft Entra ID by leveraging the FIDO2 Provisioning Graph API.”
   • [github] “SSH security keys: generate, list resident, download (rehydrate), upload to a remote (`ssh-copy-id`), add to the local ssh-agent”
   • [claimed-docs] “fido2-manage is an open-source tool allowing to manage FIDO2.1 devices over USB or NFC, including Passkey (resident keys) management. It als…”
   • [probe] “official CLI documented at https://github.com/token2/fido2-manage”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.token2.com/openapi.json, https://www.token2.com/swagger.json, https://www.token2.com/api…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.token2.com/llms.txt”

   proof ↗⚑ flag

3. ai-native userUse an official CLI

   weight 2 · round to Token2
   Feitian FIDO Keys—none0/10

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

   ⚑ flag

   Token2~partialprobed5/10

   Token2 publishes official open-source tools (fido2-manage, fido2_bulkenroll_entraid) that expose scriptable command operations (list/delete/generate/upload for keys, PIN, biometrics, SSH) usable from the command line, and the PowerShell bulk-enroll tool is inherently a CLI-style utility, but neither is explicitly branded or documented as an 'official CLI' for AI-native/agentic workflows — the flagship fido2-manage tool is described primarily as a GUI (Python/tkinter) application with underlying scriptable functions rather than a dedicated documented CLI interface. Missing for 10: explicit CLI documentation/binary/flags, examples of scripting/automation for AI agents, and independent confirmation the tool is used headlessly.

   • [github] “fido2-manage is a tool allowing to manage FIDO2.1 devices over USB or NFC, including Passkey (resident keys) management”
   • [github] “PIN management: set, change, set minimum PIN length, min-PIN-length RP allow-list... Biometric templates (bio models): list, rename, delete,…”
   • [github] “SSH security keys: generate, list resident, download (rehydrate), upload to a remote (`ssh-copy-id`), add to the local ssh-agent”
   • [claimed-docs] “This tool streamlines the process of registering FIDO2 security keys in Microsoft Entra ID by leveraging the FIDO2 Provisioning Graph API.”
   • [probe] “PROBE runtime (recorded 2026-09-15): Token2's open-source fido2-manage — 'An open-source FIDO2.1 key management tool (with a GUI) under diff…”
   • [probe] “official CLI documented at https://github.com/token2/fido2-manage”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Feitian FIDO Keys—none0/10

   Feitian FIDO Keys are hardware authentication devices with no documented public API for programmatic/agentic control; probes for llms.txt, docs-md, and OpenAPI specs all returned 404, and no evidence describes any API surface for AI agents to drive.

   • [probe] “PROBE llms.txt: HTTP 404 at https://fido.ftsafe.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://fido.ftsafe.com/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://fido.ftsafe.com/openapi.json, https://fido.ftsafe.com/swagger.json, https://fido.ftsafe.com/…”

   proof ↗⚑ flag

   Token2—none0/10

   Token2 is a hardware security key vendor; probes explicitly show no public API, no OpenAPI/Swagger spec, and no llms.txt (404s across all checked endpoints). Its tools (fido2-manage CLI, GUI, browser demos) are device-management utilities over USB/NFC/WebAuthn, not a documented public API for programmatic/agentic control.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.token2.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.token2.com/site/page/tools-for-fido-security-keys.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.token2.com/openapi.json, https://www.token2.com/swagger.json, https://www.token2.com/api…”
   • [github] “Resident credentials (passkeys): list (with user handle), delete, edit metadata”

   proof ↗⚑ flag

5. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Feitian FIDO Keys—none0/10

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

   ⚑ flag

   Token2—none0/10

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

   ⚑ flag

Api quality

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

   weight 2 · round drawn
   Feitian FIDO Keys—none0/10

   Feitian's FIDO key documentation covers WebAuthn/FIDO2 standards and setup guides but no OpenAPI/Swagger spec is published; explicit probes for llms.txt, docs-md, and openapi.json all returned 404.

   • [probe] “PROBE llms.txt: HTTP 404 at https://fido.ftsafe.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://fido.ftsafe.com/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://fido.ftsafe.com/openapi.json, https://fido.ftsafe.com/swagger.json, https://fido.ftsafe.com/…”

   proof ↗⚑ flag

   Token2—none0/10

   Token2 is a hardware security key vendor with desktop/browser tools and a CLI, but there is no evidence of a machine-readable API spec; explicit probes for OpenAPI/Swagger endpoints and llms.txt all returned 404.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.token2.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://www.token2.com/site/page/tools-for-fido-security-keys.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.token2.com/openapi.json, https://www.token2.com/swagger.json, https://www.token2.com/api…”

   proof ↗⚑ flag

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

   weight 2 · round to Token2
   Feitian FIDO Keys—none0/10

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

   ⚑ flag

   Token2~partialprobed6/10

   Token2 provides fido2_bulkenroll_entraid, a dedicated PowerShell tool for bulk-provisioning FIDO2 keys into Entra ID, and fido2-manage is a scriptable CLI (list/delete/edit passkeys, PIN and bio-template management, SSH key handling) that can be run in loops/scripts to act across many devices. This is real automation-depth for security-key/credential management but is narrow in scope (security keys/passkeys, one specific IdP integration) rather than a general bulk-operations API. Missing for 10: a general-purpose bulk API/SDK, documented batch endpoints beyond the Entra-specific script, and independent evidence of large-scale bulk use in production.

   • [claimed-docs] “This tool streamlines the process of registering FIDO2 security keys in Microsoft Entra ID by leveraging the FIDO2 Provisioning Graph API.”
   • [github] “Resident credentials (passkeys): list (with user handle), delete, edit metadata”
   • [github] “PIN management: set, change, set minimum PIN length, min-PIN-length RP allow-list... Biometric templates (bio models): list, rename, delete,…”
   • [github] “SSH security keys: generate, list resident, download (rehydrate), upload to a remote (`ssh-copy-id`), add to the local ssh-agent”
   • [probe] “PROBE runtime (recorded 2026-09-15): Token2's open-source fido2-manage — 'An open-source FIDO2.1 key management tool (with a GUI) under diff…”

   proof ↗⚑ flag

Openpgp

1. developerKeep OpenPGP keys on the device and use them for git commit signing and encrypted email

   weight 2 · round drawn
   Feitian FIDO Keys—none0/10

   Evidence covers FIDO/U2F, PIV, OTP, and OpenSSH use cases, but there is no mention of OpenPGP key storage, git commit signing, or encrypted email support anywhere in the pack.

   ⚑ flag

   Token2—none0/10

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

   ⚑ flag

Otp

1. power userThe key covers legacy one-time-password schemes — TOTP/HOTP slots or challenge-response — for services that still lack WebAuthn

   weight 2 · round to Feitian FIDO Keys
   Feitian FIDO Keys~partialclaimed6/10

   Feitian documents HOTP functionality that emulates HID keyboard to auto-type OTP values, plus an OTP Tool to switch protocols and an SK Manager to manage OTP/PIV/FIDO functions, confirming legacy OTP slot support beyond WebAuthn. However, there's no detail on TOTP support, challenge-response mode, or number of OTP slots available. Missing for 10: TOTP-specific documentation, challenge-response mode details, slot capacity/configuration specifics, and independent hands-on verification.

   • [claimed-docs] “The HOTP function of FEITIAN FIDO Security Key emulates HID Keyboard protocol to enable automatically type the value in.”
   • [claimed-docs] “Learn how to use OTP Tool to switch protocol with FEITIAN FIDO security key.”
   • [claimed-docs] “Learn how to use FEITIAN SK Manager tool to manager your security key 's functions including FIDO, PIV, OTP.”

   proof ↗⚑ flag

   Token2—none0/10

   The evidence only shows a browser-based TOTP toolset (docs-4, docs-6) and Entra ID seed export, unrelated to the FIDO2 security key itself carrying TOTP/HOTP slots or challenge-response capability; no documentation shows the hardware key supports legacy OTP protocols. Missing for 10: any spec sheet or docs stating the key itself implements TOTP/HOTP slots, challenge-response mode, or dual-protocol firmware.

   • [claimed-docs] “Generate and verify TOTP codes entirely in your browser. Algorithm: SHA-1. All computation happens locally — no seed is ever sent to a serve…”
   • [claimed-docs] “Export the current seed as an Entra ID hardware-token import file (CSV or JSON).”

   proof ↗⚑ flag

Piv

1. it adminThe key acts as a PIV smart card for certificate-based login — workstation sign-in, VPN, and code signing with keys that never leave the device

   weight 2 · round to Feitian FIDO Keys
   Feitian FIDO Keys~partialclaimed6/10

   Feitian documents PIV smart card functionality via the SK Manager tool, including macOS PIV smart card logon configuration and general PIV/FIDO/OTP management, supporting workstation sign-in use cases. However, evidence does not explicitly confirm VPN certificate-based authentication or code signing use cases with PIV, nor detail Windows/Active Directory PIV smart card logon specifically. Missing for 10: explicit VPN certificate-auth documentation, code-signing workflow evidence, Windows PIV smart card logon docs, and independent/third-party validation of PIV compliance.

   • [claimed-docs] “Learn how to use FEITIAN SK Manager tool to manager your security key 's functions including FIDO, PIV, OTP.”
   • [claimed-docs] “Learn how to use FEITIAN SK Manager to configure macOS PIV smart card log on.”

   proof ↗⚑ flag

   Token2~partialclaimed5/10

   Token2 documents PIV support via a Windows miniDriver and macOS Companion App enabling smartcard-based certificate enrollment and login with on-prem AD, which covers workstation sign-in use cases. However, there is no evidence for VPN integration or code signing use cases specifically, nor independent/hands-on verification of PIV certificate workflows beyond vendor docs. missing for 10: VPN certificate-auth evidence, code-signing use case evidence, independent/hands-on validation of PIV smartcard login, detail on key non-exportability guarantees for PIV certs.

   • [claimed-docs] “Using the Windows miniDriver, users can manage essential PIV functions such as PIN setup, PIN changes, and basic card configuration.”
   • [claimed-docs] “the miniDriver is needed to configure smartcard-based certificate enrollment and login with Windows on-premises Active Directory.”
   • [claimed-docs] “PIV features can be configured using our all-in-one management tool, the Companion App, which is now also available on macOS.”

   proof ↗⚑ flag

Ssh

1. developerMy SSH keys can be hardware-backed on the device — via FIDO2 sk-ssh keys, PIV, or OpenPGP — so server access requires a physical touch

   weight 2 · round drawn
   Feitian FIDO Keys~partialclaimed6/10

   Feitian docs explicitly cover FIDO2 sk-ssh usage for OpenSSH/GitHub/Linux server login (feitian-docs-6) and PIV smart-card functionality including macOS PIV logon via SK Manager (feitian-docs-9, feitian-docs-10), supporting hardware-backed SSH auth with physical touch. However, no OpenPGP-based SSH key support is documented anywhere in the pack. Missing for 10: explicit OpenPGP applet/SSH support, independent/hands-on verification of sk-ssh workflow, and unified documentation tying all three methods together.

   • [claimed-docs] “Learn how to apply FEITIAN FIDO security keys with OpenSSH connections including remotely connecting Github and Linux server.”
   • [claimed-docs] “Learn how to use FEITIAN SK Manager tool to manager your security key 's functions including FIDO, PIV, OTP.”
   • [claimed-docs] “Learn how to use FEITIAN SK Manager to configure macOS PIV smart card log on.”

   proof ↗⚑ flag

   Token2~partialprobed6/10

   Token2's fido2-manage tool explicitly supports SSH security keys (generate, list resident, download/rehydrate, ssh-copy-id, add to local ssh-agent), directly evidencing FIDO2 sk-ssh hardware-backed key workflows. PIV is also supported via the Windows miniDriver and Companion App for smartcard-based certificate enrollment, but there is no mention of OpenPGP support for SSH auth. missing for 10: OpenPGP-based SSH key support, independent/hands-on verification of the sk-ssh workflow, and cross-platform PIV parity beyond Windows/macOS.

   • [github] “SSH security keys: generate, list resident, download (rehydrate), upload to a remote (`ssh-copy-id`), add to the local ssh-agent”
   • [claimed-docs] “Using the Windows miniDriver, users can manage essential PIV functions such as PIN setup, PIN changes, and basic card configuration.”
   • [claimed-docs] “the miniDriver is needed to configure smartcard-based certificate enrollment and login with Windows on-premises Active Directory.”
   • [claimed-docs] “PIV features can be configured using our all-in-one management tool, the Companion App, which is now also available on macOS.”
   • [probe] “PROBE runtime (recorded 2026-09-15): Token2's open-source fido2-manage — 'An open-source FIDO2.1 key management tool (with a GUI) under diff…”

   proof ↗⚑ flag

Agent audit

1. ai-native userAn agent can read a key's state programmatically — serial, firmware version, enabled applications, stored credentials — to audit security posture across a fleet

   weight 2 · round to Token2
   Feitian FIDO Keys—none0/10

   There is a SK Manager GUI tool for managing FIDO/PIV/OTP functions, but no evidence of any programmatic API, CLI output, or SDK exposing serial, firmware version, enabled applications, or credential state for automated fleet auditing by an agent; probes for API/docs endpoints all returned 404.

   • [claimed-docs] “Learn how to use FEITIAN SK Manager tool to manager your security key 's functions including FIDO, PIV, OTP.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://fido.ftsafe.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://fido.ftsafe.com/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://fido.ftsafe.com/openapi.json, https://fido.ftsafe.com/swagger.json, https://fido.ftsafe.com/…”

   proof ↗⚑ flag

   Token2~partialprobed5/10

   Token2's open-source fido2-manage CLI/GUI tool (scriptable over USB/NFC) can view device information, list resident credentials (passkeys) with user handle, manage PINs, and enumerate biometric templates — giving an agent a scriptable path to audit key state across a fleet. However, no evidence documents reading serial numbers, firmware version, or 'enabled applications' specifically, nor is there a structured/JSON API, OpenAPI spec, or llms.txt for machine-readable output (confirmed 404s), so agent-friendly programmatic access is only partially evidenced. Missing for 10: documented serial/firmware-version fields, explicit 'enabled applications' enumeration, and a structured machine-readable output/API for agent consumption.

   • [github] “Resident credentials (passkeys): list (with user handle), delete, edit metadata”
   • [github] “fido2-manage is a tool allowing to manage FIDO2.1 devices over USB or NFC, including Passkey (resident keys) management”
   • [github] “PIN management: set, change, set minimum PIN length, min-PIN-length RP allow-list... Biometric templates (bio models): list, rename, delete,…”
   • [claimed-docs] “It provides a simple interface to view device information, manage passkeys, change PINs, and perform factory resets.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.token2.com/openapi.json, https://www.token2.com/swagger.json, https://www.token2.com/api…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Token2's open-source fido2-manage — 'An open-source FIDO2.1 key management tool (with a GUI) under diff…”

   proof ↗⚑ flag

Attestation

1. security engineerVerify device attestation at registration to enforce that only genuine, approved key models are enrolled

   weight 2 · round to Token2
   Feitian FIDO Keys—none0/10

   No evidence in the pack discusses FIDO attestation, AAGUID verification, metadata service (MDS) support, or any mechanism for security engineers to validate genuine Feitian key models at registration; the docs cover general FIDO compatibility, interfaces, and setup guides only.

   ⚑ flag

   Token2~partialclaimed3/10

   Token2 provides an AAGUID lookup tool to identify certified authenticators and a WebAuthn registration demo, which touch on device identification, but there is no documented mechanism for verifying attestation certificates or enforcing an allow-list of approved key models at registration. missing for 10: attestation certificate chain validation, FIDO Metadata Service integration, documented enterprise enrollment policy enforcement.

   • [claimed-docs] “Look up any certified authenticator by name or AAGUID — no key required.”
   • [claimed-docs] “Register a security key or passkey, then log in with it — all in your browser using the WebAuthn API.”
   • [claimed-docs] “This tool streamlines the process of registering FIDO2 security keys in Microsoft Entra ID by leveraging the FIDO2 Provisioning Graph API.”

   proof ↗⚑ flag

Cli

1. developerConfigure and manage the key from an official CLI — enable applications, set PINs, manage slots, read device state — scriptably

   weight 3 · round to Token2
   Feitian FIDO Keys~partialclaimed4/10

   Feitian offers GUI tools (SK Manager, iePassManager, OTP Tool) for managing FIDO/PIV/OTP functions, PINs, and slots, but these are graphical utilities, not documented as scriptable CLIs. No evidence of a command-line interface, scripting API, or automation-friendly tooling for enabling apps, setting PINs, or reading device state. missing for 10: dedicated CLI tool, scripting/automation documentation, examples of headless/scriptable configuration workflows.

   • [claimed-docs] “Learn how to use FEITIAN SK Manager tool to manager your security key 's functions including FIDO, PIV, OTP.”
   • [claimed-docs] “Learn how to use FEITIAN SK Manager to configure macOS PIV smart card log on.”
   • [claimed-docs] “Learn how to use iePassManager at Android OS to manage your FIDO devices(including FIDO PIN and credential related operations).”
   • [claimed-docs] “Learn how to use OTP Tool to switch protocol with FEITIAN FIDO security key.”

   proof ↗⚑ flag

   Token2~partialprobed6/10

   fido2-manage is an official open-source Token2 tool that supports PIN set/change, resident-credential (passkey) and biometric slot management, and device info viewing, and a probe confirms it is documented as a CLI, giving genuine scriptable control over FIDO2 keys. However most docs describe it primarily as a Python/tkinter GUI rather than a dedicated CLI, and there's no explicit mention of an 'enable applications' feature or comprehensive CLI usage examples/API reference. missing for 10: explicit CLI command reference/examples, 'enable applications' capability, independent hands-on CLI scripting confirmation.

   • [github] “fido2-manage is a tool allowing to manage FIDO2.1 devices over USB or NFC, including Passkey (resident keys) management”
   • [github] “PIN management: set, change, set minimum PIN length, min-PIN-length RP allow-list... Biometric templates (bio models): list, rename, delete,…”
   • [github] “Resident credentials (passkeys): list (with user handle), delete, edit metadata”
   • [claimed-docs] “fido2-manage is an open-source tool allowing to manage FIDO2.1 devices over USB or NFC, including Passkey (resident keys) management. It als…”
   • [probe] “official CLI documented at https://github.com/token2/fido2-manage”
   • [probe] “PROBE runtime (recorded 2026-09-15): Token2's open-source fido2-manage — 'An open-source FIDO2.1 key management tool (with a GUI) under diff…”

   proof ↗⚑ flag

Sdks

1. developerOfficial SDKs let me integrate the key into my own desktop and mobile apps

   weight 2 · round drawn
   Feitian FIDO Keys—none0/10

   Evidence covers WebAuthn/FIDO2 standard support, OS integrations (Windows Hello, Azure AD, OpenSSH), and firmware provisioning via Google's OpenSK repo, but nothing indicates Feitian ships its own official SDK for developers to embed key support into custom desktop/mobile apps. Probe results also confirm no API/docs discoverability artifacts. This is an applicable axis for a hardware key vendor (SDKs are common in this space) but no evidence of one existing.

   • [claimed-docs] “Users can build firmware from the source code of Google OpenSK Github repository without changing anything, provision it to this OpenSK hard…”
   • [claimed-docs] “Users can build firmware from the source code of Google OpenSK Github repository without changing anything, provision it to this OpenSK hard…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://fido.ftsafe.com/openapi.json, https://fido.ftsafe.com/swagger.json, https://fido.ftsafe.com/…”

   proof ↗⚑ flag

   Token2—none0/10

   Evidence shows only management/admin tools (fido2-manage GUI/CLI, bulk enrollment for Entra ID, browser-based WebAuthn demo) rather than an official SDK or library for embedding the key's authentication into a developer's own desktop/mobile applications. No mention of a downloadable SDK, API bindings, or mobile library is found anywhere in the pack.

   • [claimed-docs] “Open-source cross-platform desktop companion application for managing FIDO2 security keys.”
   • [github] “Resident credentials (passkeys): list (with user handle), delete, edit metadata”
   • [github] “fido2-manage is a tool allowing to manage FIDO2.1 devices over USB or NFC, including Passkey (resident keys) management”
   • [github] “PIN management: set, change, set minimum PIN length, min-PIN-length RP allow-list... Biometric templates (bio models): list, rename, delete,…”
   • [github] “SSH security keys: generate, list resident, download (rehydrate), upload to a remote (`ssh-copy-id`), add to the local ssh-agent”
   • [claimed-docs] “Register a security key or passkey, then log in with it — all in your browser using the WebAuthn API.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.token2.com/openapi.json, https://www.token2.com/swagger.json, https://www.token2.com/api…”
   • [probe] “official CLI documented at https://github.com/token2/fido2-manage”

   proof ↗⚑ flag

Agent approval

1. ai-native userRequire a physical key touch as the human-approval step for sensitive automated or agent-initiated actions

   weight 1 · round to Feitian FIDO Keys
   Feitian FIDO Keys~partialclaimed5/10

   Feitian keys are standard FIDO2/WebAuthn/U2F hardware tokens that inherently require a physical touch to complete authentication (feitian-docs-1, feitian-docs-4, feitian-docs-18), which is the underlying mechanism that could be wired into an agent's approval flow via WebAuthn. However, there is no evidence of any AI-agent-specific integration, SDK, or documented workflow showing the key used as a human-approval gate for agent-initiated actions. Missing for 10: explicit AI-agent/automation integration examples, documentation of using the key as an approval gate in agentic pipelines, and any third-party corroboration of this use case.

   • [claimed-docs] “Fully compatible to W3C's Web Authentication Standard with HID interface. Plug in and secure your web applications easily.”
   • [claimed-docs] “USB, NFC, and BLE, MultiPass FIDO® Security Key employs three communication interfaces.”
   • [claimed-docs] “USB, NFC, and BLE, MultiPass FIDO® Security Key employs three communication interfaces. Users can use any of these interfaces to complete FI…”

   proof ↗⚑ flag

   Token2—none0/10

   Token2's evidence covers FIDO2 key management, PIV, TOTP tools, and WebAuthn demos, but nothing shows integration with AI agents or automated workflows that would use a physical touch as an approval gate for agent-initiated actions. Missing for 10: any documentation of agent/automation integration, an approval-step API or SDK, or a workflow example tying physical touch to AI-agent action authorization.

   • [claimed-docs] “Open-source cross-platform desktop companion application for managing FIDO2 security keys.”
   • [claimed-docs] “Register a security key or passkey, then log in with it — all in your browser using the WebAuthn API.”
   • [github] “Resident credentials (passkeys): list (with user handle), delete, edit metadata”
   • [claimed-docs] “This manufacturer-agnostic tool works with any FIDO2.1 device.”

   proof ↗⚑ flag

Compatibility

1. power userThe key works across my operating systems and browsers, with a published compatibility catalog of supported services

   weight 2 · round drawn
   Feitian FIDO Keys~partialclaimed5/10

   Feitian documents cross-platform compatibility (Windows, macOS, Linux, Android/iOS) and integration guides for specific platforms (Windows Hello, Azure AD, GitHub/OpenSSH, Google Advanced Protection, PIV/macOS), and multi-interface support (USB/NFC/BLE) which implies broad OS/browser reach. However there is no published, centralized compatibility catalog or matrix listing supported browsers/services, and no independent verification of claims. Missing for 10: a formal published compatibility catalog/matrix of supported services and browsers, independent/hands-on verification of cross-platform claims.

   • [claimed-docs] “Fully compatible to W3C's Web Authentication Standard with HID interface. Plug in and secure your web applications easily.”
   • [claimed-docs] “Seamlessly support Windows Hello (Within an Azure AD).”
   • [claimed-docs] “Learn how to apply FEITIAN FIDO security keys with OpenSSH connections including remotely connecting Github and Linux server.”
   • [claimed-docs] “Learn how to use your FEITIAN FIDO2 security key to protect your Azure AD joined Windows 10.”
   • [claimed-docs] “Learn how to use FEITIAN SK Manager to configure macOS PIV smart card log on.”
   • [claimed-docs] “MultiPass FIDO® Security Key is also compatible with any Android / iOS platforms with Bluetooth v4.0+.”
   • [claimed-docs] “Recognized as a HID device, no driver is needed for MultiPass FIDO® Security Key to work on Microsoft Windows, macOS and Linux via USB.”
   • [claimed-docs] “Introduction about how FEITIAN Security Keys works with Google advanced protection.”

   proof ↗⚑ flag

   Token2~partialclaimed5/10

   Evidence shows solid cross-OS/browser support (Windows control panel, Chromium browsers, macOS/Linux companion app, PIV miniDriver) and manufacturer-agnostic FIDO2.1 tooling, but there is no published catalog listing which third-party services/relying parties are certified compatible with Token2 keys. missing for 10: a published service/RP compatibility catalog, independent cross-browser/OS corroboration beyond vendor docs.

   • [claimed-docs] “It provides a simple interface to view device information, manage passkeys, change PINs, and perform factory resets.”
   • [claimed-docs] “If you are using macOS or Linux, you can manage your FIDO2 keys using the tool integrated into the latest Chromium based browsers, such as G…”
   • [claimed-docs] “You can use the standard Windows control panel tool to manage your key, as long as you run Windows 10 build 1903 or later.”
   • [claimed-docs] “PIV features can be configured using our all-in-one management tool, the Companion App, which is now also available on macOS.”
   • [claimed-docs] “This manufacturer-agnostic tool works with any FIDO2.1 device.”
   • [github] “fido2-manage is a tool allowing to manage FIDO2.1 devices over USB or NFC, including Passkey (resident keys) management”

   proof ↗⚑ flag

Recovery

1. security engineerThe vendor documents a credible lockout-recovery strategy — registering a backup key, and what is and is not recoverable if a key is lost

   weight 3 · round to Feitian FIDO Keys
   Feitian FIDO Keys~partialclaimed5/10

   FAQ entries state that a lost key can be worked around by logging in with a backup security key or another method, then disabling the lost key and provisioning a new one, which is a real but minimal statement of a lockout-recovery strategy (feitian-docs-14, feitian-docs-24). However, there is no dedicated recovery guide explaining what is and isn't recoverable (e.g., per-relying-party re-registration necessity, loss of resident/discoverable credentials, biometric enrollment data) beyond this brief FAQ mention. Missing for 10: a structured recovery/lockout doc, explicit treatment of what is NOT recoverable (credentials tied to lost key), and guidance on enrolling multiple backup keys per service rather than just a generic FAQ answer.

   • [claimed-docs] “The dedicated users can still logon to the account by using back-up security key or other method.”
   • [claimed-docs] “The dedicated users can still logon to the account by using back-up security key or other method. Then user can disable the lost security ke…”

   proof ↗⚑ flag

   Token2~partialclaimed3/10

   Token2's FAQ includes a 'How Do I Set Up a Backup Key?' entry, indicating some guidance exists, but the evidence pack contains no actual content on what is/isn't recoverable if a key is lost (e.g., resident credentials, PINs, biometrics, or TOTP seeds). Missing for 10: detailed recovery/lockout policy content, explicit statement of non-recoverable data (e.g., resident key private keys), and any independent corroboration of the backup-key workflow.

   • [claimed-docs] “How Do I Set Up a Backup Key?”

   proof ↗⚑ flag

Setup

1. power userFirst-time setup is guided — clear instructions or a setup app walk me through registering the key with my accounts

   weight 2 · round to Feitian FIDO Keys
   Feitian FIDO Keys~partialclaimed7/10

   Feitian provides first-party guided documentation for pairing keys (BLE setup guide), registering with specific platforms (Windows, Azure AD, Microsoft, GitHub/Linux via OpenSSH), and a dedicated SK Manager desktop app for configuring FIDO/PIV/OTP functions, which together resemble a guided enrollment flow for a power user. However, missing for 10: independent/hands-on user reports confirming the setup experience is clear in practice, and no single unified 'wizard' walkthrough spanning consumer-account registration (e.g., Google/Microsoft account UI) rather than platform/OS-level docs.

   • [claimed-docs] “Learn how to pair your FEITIAN Bluetooth FIDO2 security key to your device.”
   • [claimed-docs] “Learn how to apply FEITIAN FIDO security keys with OpenSSH connections including remotely connecting Github and Linux server.”
   • [claimed-docs] “Learn how to use your FEITIAN FIDO2 security key to protect your personal Windows.”
   • [claimed-docs] “Learn how to use your FEITIAN FIDO2 security key to protect your Azure AD joined Windows 10.”
   • [claimed-docs] “Learn how to use FEITIAN SK Manager tool to manager your security key 's functions including FIDO, PIV, OTP.”
   • [claimed-docs] “Learn how to use your FEITIAN FIDO2 security key to protect your Microsoft application.”

   proof ↗⚑ flag

   Token2~partialclaimed6/10

   Token2 provides multiple avenues for onboarding: a browser-based FIDO2/passkey demo to test registration (token2-docs-5, token2-docs-16), OS-native guidance for macOS/Linux/Chrome and Windows control panel (token2-docs-13/14/15), a companion GUI app for device/passkey management (token2-docs-1/7/8), and an FAQ entry on setting up a backup key (token2-docs-17). This gives a reasonably guided path but is scattered across docs/tools rather than a single cohesive first-time setup wizard that walks a user through registering with specific real-world accounts (e.g., Google, Microsoft, GitHub). Missing for 10: a unified step-by-step onboarding flow/app tailored to major account providers, and independent user reports confirming ease of first-time setup.

   • [claimed-docs] “Register a security key or passkey, then log in with it — all in your browser using the WebAuthn API.”
   • [claimed-docs] “Explore FIDO2 and passkey authentication hands-on. Register a security key or passkey, then log in with it — all in your browser using the W…”
   • [claimed-docs] “No special tool installation is needed to start using the FIDO keys, as most modern browsers will prompt to set a PIN when required”
   • [claimed-docs] “If you are using macOS or Linux, you can manage your FIDO2 keys using the tool integrated into the latest Chromium based browsers, such as G…”
   • [claimed-docs] “You can use the standard Windows control panel tool to manage your key, as long as you run Windows 10 build 1903 or later.”
   • [claimed-docs] “How Do I Set Up a Backup Key?”
   • [claimed-docs] “Open-source cross-platform desktop companion application for managing FIDO2 security keys.”
   • [claimed-docs] “It provides a simple interface to view device information, manage passkeys, change PINs, and perform factory resets.”
   • [claimed-docs] “fido2-manage is an open-source tool allowing to manage FIDO2.1 devices over USB or NFC, including Passkey (resident keys) management. It als…”

   proof ↗⚑ flag

Source

1. security engineerThe firmware is open source or independently audited, so I don't have to take the vendor's word for what runs on the device

   weight 2 · round to Feitian FIDO Keys
   Feitian FIDO Keys~partialclaimed5/10

   Feitian offers a specific OpenSK hardware variant where users can build firmware from Google's open-source OpenSK repo and flash it themselves, directly addressing the transparency concern for that model. However, the flagship BioPass and MultiPass FIDO keys firmware is not documented as open source or independently audited, and no third-party security audit reports are cited anywhere in the pack. missing for 10: independent firmware audit reports for mainstream product lines, confirmation that BioPass and MultiPass firmware not just the niche OpenSK SKU is open or audited, and hands-on verification that shipped OpenSK devices match the public source

   • [claimed-docs] “Users can build firmware from the source code of Google OpenSK Github repository without changing anything, provision it to this OpenSK hard…”
   • [claimed-docs] “Users can build firmware from the source code of Google OpenSK Github repository without changing anything, provision it to this OpenSK hard…”

   proof ↗⚑ flag

   Token2—none0/10

   All evidence concerns open-source host-side management tools (fido2-manage GUI, companion app, bulk-enrollment scripts) that run on a computer to manage the keys — none of it addresses whether the actual device firmware running on the Token2 hardware key itself is open source or has undergone independent security audit.

   ⚑ flag

Updates

1. security engineerThe vendor has a clear firmware update and vulnerability-response story — advisories, affected-model lookup, and how fixes reach devices

   weight 2 · round drawn
   Feitian FIDO Keys—none0/10

   No evidence of security advisories, CVE tracking, affected-model lookup tools, or a documented firmware update delivery mechanism; only general product/setup docs and an OpenSK build guide are present, none of which address vulnerability response or patch distribution.

   ⚑ flag

   Token2—none0/10

   Evidence covers key management tools (PIN, passkeys, PIV, SSH) but contains no security advisories, CVE/vulnerability disclosure process, affected-model lookup tool, or firmware update delivery mechanism for Token2 devices.

   ⚑ flag

Agent provisioning

1. ai-native userAn agent can drive key provisioning end to end — ordering, assignment, pre-registration — through documented enterprise APIs instead of a human-only console

   weight 2 · round to Token2
   Feitian FIDO Keys—none0/10

   No evidence of any enterprise API for provisioning, ordering, or assignment of keys — all documentation is consumer/end-user setup guides, and probes for API/docs endpoints returned 404s.

   • [probe] “PROBE llms.txt: HTTP 404 at https://fido.ftsafe.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://fido.ftsafe.com/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://fido.ftsafe.com/openapi.json, https://fido.ftsafe.com/swagger.json, https://fido.ftsafe.com/…”

   proof ↗⚑ flag

   Token2~partialprobed3/10

   Token2 ships an open-source CLI (fido2-manage) for local device configuration and a PowerShell bulk-enrollment script that automates pre-registering keys into Microsoft Entra ID via Microsoft's Graph API — some scriptable, agent-drivable provisioning exists. However, there is no evidence of Token2's own documented enterprise API for ordering or assigning keys to users, and probes confirm no OpenAPI/swagger spec exists on their site. missing for 10: a Token2-owned ordering API, an assignment/fleet-management API, and any documented enterprise API surface beyond third-party (Microsoft) integration scripts.

   • [claimed-docs] “This tool streamlines the process of registering FIDO2 security keys in Microsoft Entra ID by leveraging the FIDO2 Provisioning Graph API.”
   • [github] “Resident credentials (passkeys): list (with user handle), delete, edit metadata”
   • [github] “SSH security keys: generate, list resident, download (rehydrate), upload to a remote (`ssh-copy-id`), add to the local ssh-agent”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.token2.com/openapi.json, https://www.token2.com/swagger.json, https://www.token2.com/api…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Token2's open-source fido2-manage — 'An open-source FIDO2.1 key management tool (with a GUI) under diff…”

   proof ↗⚑ flag

Delivery

1. it adminAn enterprise delivery service ships keys directly to distributed employees, driven by an API or console rather than manual logistics

   weight 2 · round drawn
   Feitian FIDO Keys—none0/10

   No evidence of any API, console, or enterprise fulfillment/logistics/shipping-management capability; probes confirm no API/docs exist for this. Evidence covers only device features (FIDO2, biometrics, NFC/BLE/USB) and setup guides, nothing about distributed shipping orchestration.

   • [probe] “PROBE llms.txt: HTTP 404 at https://fido.ftsafe.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://fido.ftsafe.com/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://fido.ftsafe.com/openapi.json, https://fido.ftsafe.com/swagger.json, https://fido.ftsafe.com/…”

   proof ↗⚑ flag

   Token2—none0/10

   Evidence covers device management, bulk enrollment, and provisioning tools but nothing about a logistics/delivery service (e.g., automated shipping of physical keys to distributed employees) driven by API or console. No fulfillment, shipping, or distribution capability is documented anywhere in the evidence pack.

   ⚑ flag

Idp

1. it adminThe key integrates with my identity provider — Okta, Entra ID, Google Workspace — and I can enforce policies requiring hardware-key authentication

   weight 2 · round to Feitian FIDO Keys
   Feitian FIDO Keys~partialclaimed6/10

   Feitian keys are documented as fully W3C WebAuthn/FIDO2-compliant HID devices with explicit setup guides for Azure AD-joined Windows, Microsoft applications, and Google Advanced Protection, which implies interoperability with major identity providers. However, there is no explicit documentation or guide for Okta or Google Workspace integration, nor any mention of admin-side policy enforcement (e.g., requiring hardware-key-only auth) within these IdPs. Missing for 10: Okta-specific integration guide, Google Workspace-specific setup docs, and evidence of IdP admin policy controls enforcing hardware-key requirements.

   • [claimed-docs] “Fully compatible to W3C's Web Authentication Standard with HID interface. Plug in and secure your web applications easily.”
   • [claimed-docs] “Learn how to use your FEITIAN FIDO2 security key to protect your Azure AD joined Windows 10.”
   • [claimed-docs] “Learn how to use your FEITIAN FIDO2 security key to protect your Microsoft application.”
   • [claimed-docs] “Introduction about how FEITIAN Security Keys works with Google advanced protection.”
   • [claimed-docs] “Seamlessly support Windows Hello (Within an Azure AD).”

   proof ↗⚑ flag

   Token2~partialprobed4/10

   Token2 documents a dedicated Entra ID bulk-enrollment tool leveraging the Graph API, showing concrete IdP integration for one provider, and its keys are standard FIDO2 devices that any IdP could require via WebAuthn policy. However, there is no evidence of Okta or Google Workspace-specific integration tooling, nor documentation of admin-side policy enforcement (e.g., conditional access rules mandating hardware-key auth) — these are typically the IdP's own settings, not something Token2 documents supporting or configuring. Missing for 10: Okta integration evidence, Google Workspace integration evidence, and any documentation of fleet-wide policy enforcement/reporting.

   • [claimed-docs] “This tool streamlines the process of registering FIDO2 security keys in Microsoft Entra ID by leveraging the FIDO2 Provisioning Graph API.”
   • [probe] “PROBE runtime (recorded 2026-09-15): Token2's open-source fido2-manage — 'An open-source FIDO2.1 key management tool (with a GUI) under diff…”
   • [claimed-docs] “the miniDriver is needed to configure smartcard-based certificate enrollment and login with Windows on-premises Active Directory.”

   proof ↗⚑ flag

Provisioning

1. it adminProvision keys across an organization at scale — pre-registration, bulk configuration, and lifecycle tracking of issued keys

   weight 3 · round to Token2
   Feitian FIDO Keys—none0/10

   Evidence only shows per-device configuration tools (SK Manager, iePassManager) for individual FIDO/PIV/OTP settings, not organization-wide bulk provisioning, pre-registration workflows, or lifecycle/inventory tracking across a fleet of keys. No admin console, CSV/bulk import, or enterprise deployment tooling is documented.

   • [claimed-docs] “Learn how to use FEITIAN SK Manager tool to manager your security key 's functions including FIDO, PIV, OTP.”
   • [claimed-docs] “Learn how to use FEITIAN SK Manager to configure macOS PIV smart card log on.”
   • [claimed-docs] “Learn how to use iePassManager at Android OS to manage your FIDO devices(including FIDO PIN and credential related operations).”
   • [claimed-docs] “Learn how to use OTP Tool to switch protocol with FEITIAN FIDO security key.”

   proof ↗⚑ flag

   Token2~partialprobed5/10

   Token2 offers a PowerShell-based bulk enrollment tool for Entra ID (fido2_bulkenroll_entraid) and an open-source fido2-manage CLI/GUI for per-key PIN, biometric, and passkey configuration, which supports pre-registration and bulk configuration workflows. However, there is no evidence of an organization-wide inventory, dashboard, or lifecycle-tracking system for issued keys beyond individual device management and Entra-specific scripting. Missing for 10: centralized fleet inventory/dashboard, cross-platform (non-Entra ID) bulk provisioning, and lifecycle status tracking (issued/revoked/expired) across an organization.

   • [claimed-docs] “This tool streamlines the process of registering FIDO2 security keys in Microsoft Entra ID by leveraging the FIDO2 Provisioning Graph API.”
   • [github] “Resident credentials (passkeys): list (with user handle), delete, edit metadata”
   • [github] “PIN management: set, change, set minimum PIN length, min-PIN-length RP allow-list... Biometric templates (bio models): list, rename, delete,…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Token2's open-source fido2-manage — 'An open-source FIDO2.1 key management tool (with a GUI) under diff…”
   • [claimed-docs] “fido2-manage is an open-source tool allowing to manage FIDO2.1 devices over USB or NFC, including Passkey (resident keys) management. It als…”

   proof ↗⚑ flag

Certifications

1. it adminCertified models exist for regulated environments — FIPS 140 validated or Common Criteria certified — with documented durability (water/crush resistance)

   weight 2 · round drawn
   Feitian FIDO Keys—none0/10

   The evidence pack contains no mention of FIPS 140 validation, Common Criteria certification, or durability testing (water/crush resistance) for any Feitian key; all citations focus on protocol compatibility, interfaces, and setup guides. Missing for 10: FIPS 140 validation documentation, Common Criteria certification documentation, water/crush resistance durability specs.

   ⚑ flag

   Token2—none0/10

   The evidence pack covers management tools and software (companion apps, FIDO2 demo, PIV miniDriver) but contains no mention of FIPS 140 validation, Common Criteria certification, or physical durability specifications (water/crush resistance) for any Token2 hardware devices. missing for 10: FIPS 140 validation certificates, Common Criteria certification listings, IP rating or crush-resistance test documentation for hardware keys.

   ⚑ flag

Connectors

1. power userThe lineup covers my ports and carry style — USB-C and USB-A models, keychain and low-profile nano form factors

   weight 2 · round drawn
   Feitian FIDO Keys—none0/10

   The evidence pack covers interfaces (USB/NFC/BLE), biometric and OpenSK products, but never mentions specific form factors like USB-C vs USB-A connectors, keychain design, or nano/low-profile sizing — no product lineup breakdown by physical form is shown.

   ⚑ flag

   Token2—none0/10

   The evidence pack focuses entirely on software tools (FIDO2 management apps, TOTP toolset, PIV drivers) and never describes Token2's physical hardware lineup, connector types (USB-C/USB-A), or form factors (keychain, nano). No mention of product SKUs, dimensions, or port types is present, so there's no basis to confirm coverage of power-user form-factor variety. Missing for 10: hardware product listings, connector-type specs, form-factor descriptions (nano/keychain), any comparison chart of models.

   ⚑ flag

Nfc

1. power userTap the key on my phone over NFC to authenticate in mobile browsers and apps

   weight 2 · round to Feitian FIDO Keys
   Feitian FIDO Keys~partialclaimed6/10

   MultiPass FIDO Security Key explicitly supports NFC as one of three interfaces and is documented compatible with Android/iOS platforms, implying tap-to-authenticate via NFC on mobile; however, evidence doesn't explicitly confirm NFC (vs BLE) works with specific mobile browsers/apps or provide hands-on confirmation. missing for 10: explicit mobile browser/app NFC tap walkthrough, independent hands-on verification of NFC mobile authentication.

   • [claimed-docs] “USB, NFC, and BLE, MultiPass FIDO® Security Key employs three communication interfaces.”
   • [claimed-docs] “USB, NFC, and BLE, MultiPass FIDO® Security Key employs three communication interfaces. Users can use any of these interfaces to complete FI…”
   • [claimed-docs] “MultiPass FIDO® Security Key is also compatible with any Android / iOS platforms with Bluetooth v4.0+.”

   proof ↗⚑ flag

   Token2~partialclaimed4/10

   Token2's own tooling confirms its FIDO2 keys support NFC as a communication transport (used by the fido2-manage companion app to manage keys over USB or NFC), which implies NFC-capable hardware, but there is no explicit documentation stating that users can tap the key on a phone to authenticate within mobile browsers or apps via WebAuthn/CTAP2 NFC. Missing for 10: explicit end-user documentation or demo of phone-NFC-based authentication in mobile browsers/apps, and any independent confirmation of this specific mobile use case.

   • [claimed-docs] “fido2-manage is an open-source tool allowing to manage FIDO2.1 devices over USB or NFC, including Passkey (resident keys) management. It als…”
   • [github] “fido2-manage is a tool allowing to manage FIDO2.1 devices over USB or NFC, including Passkey (resident keys) management”
   • [claimed-docs] “This manufacturer-agnostic tool works with any FIDO2.1 device.”

   proof ↗⚑ flag

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

   weight 2 · round to Token2
   Feitian FIDO Keys—none0/10

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

   ⚑ flag

   Token2~partialprobed4/10

   Token2 ships an open-source CLI (fido2-manage) that overlaps with much of the companion GUI's functionality — resident credential/passkey management, PIN setup, biometric template management, and SSH key operations can all be scripted — giving some AI-native/automation parity with the desktop UI. However, there is no true REST/HTTP API (probes confirm openapi.json/swagger.json all 404), and several UI-only web tools (TOTP toolset, WebAuthn browser demo, factory reset) have no documented programmatic equivalent. Missing for 10: a formal API surface (REST/OpenAPI) covering all UI functions, CLI/API parity for the web-based demo and TOTP tools, and independent confirmation that CLI coverage is fully equivalent to the GUI.

   • [github] “Resident credentials (passkeys): list (with user handle), delete, edit metadata”
   • [github] “PIN management: set, change, set minimum PIN length, min-PIN-length RP allow-list... Biometric templates (bio models): list, rename, delete,…”
   • [github] “SSH security keys: generate, list resident, download (rehydrate), upload to a remote (`ssh-copy-id`), add to the local ssh-agent”
   • [claimed-docs] “It provides a simple interface to view device information, manage passkeys, change PINs, and perform factory resets.”
   • [claimed-docs] “Generate and verify TOTP codes entirely in your browser. Algorithm: SHA-1. All computation happens locally — no seed is ever sent to a serve…”
   • [claimed-docs] “Register a security key or passkey, then log in with it — all in your browser using the WebAuthn API.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.token2.com/openapi.json, https://www.token2.com/swagger.json, https://www.token2.com/api…”
   • [probe] “official CLI documented at https://github.com/token2/fido2-manage”
   • [probe] “PROBE runtime (recorded 2026-09-15): Token2's open-source fido2-manage — 'An open-source FIDO2.1 key management tool (with a GUI) under diff…”

   proof ↗⚑ flag

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

   weight 3 · round to Token2
   Feitian FIDO Keys—none0/10

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

   ⚑ flag

   Token2~partialprobed5/10

   Token2 supports exporting TOTP seeds as open CSV/JSON files for Entra ID import, and its open-source fido2-manage tool lets users list, download, and rehydrate resident credentials and SSH keys from FIDO2 devices, plus it's explicitly manufacturer-agnostic (works with any FIDO2.1 key), supporting migration away from Token2 hardware without lock-in. However, this covers only specific data types (TOTP seeds, credentials, SSH keys) rather than a full account/data export, and there's no unified 'export everything' feature or documentation. Missing for 10: comprehensive account-wide data export, first-party documentation framing this as a full data portability/exit feature, independent verification of export completeness.

   • [claimed-docs] “Export the current seed as an Entra ID hardware-token import file (CSV or JSON).”
   • [github] “Resident credentials (passkeys): list (with user handle), delete, edit metadata”
   • [github] “SSH security keys: generate, list resident, download (rehydrate), upload to a remote (`ssh-copy-id`), add to the local ssh-agent”
   • [claimed-docs] “This manufacturer-agnostic tool works with any FIDO2.1 device.”
   • [probe] “PROBE runtime (recorded 2026-09-15): Token2's open-source fido2-manage — 'An open-source FIDO2.1 key management tool (with a GUI) under diff…”

   proof ↗⚑ flag

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

   weight 2 · round to Token2
   Feitian FIDO Keys~partialclaimed4/10

   Feitian ships a specific 'OpenSK' hardware variant that can run firmware built from Google's open-source OpenSK repository, giving some access to readable/open-licensed source for that SKU, but this is a third-party (Google) codebase, not Feitian's own firmware for its mainstream BioPass/MultiPass keys, which remain closed. Missing for 10: evidence that Feitian's own primary product firmware/source is published under an open license, and no indication of a public source repo, license file, or docs-as-markdown/API spec for the broader product line.

   • [claimed-docs] “Users can build firmware from the source code of Google OpenSK Github repository without changing anything, provision it to this OpenSK hard…”
   • [claimed-docs] “Users can build firmware from the source code of Google OpenSK Github repository without changing anything, provision it to this OpenSK hard…”

   proof ↗⚑ flag

   Token2~partialprobed6/10

   Token2 open-sources some companion tooling on GitHub (fido2-manage, fido2_bulkenroll_entraid) with real activity (112 stars, recent pushes), letting an AI-native user inspect that code, but the core hardware product/firmware and several web tools (TOTP toolset, FIDO2 demo) are not shown to have public source, and no explicit license file/type is cited. Missing for 10: confirmed OSI license text, source availability for the full product line (not just auxiliary management tools).

   • [claimed-docs] “Open-source cross-platform desktop companion application for managing FIDO2 security keys.”
   • [github] “Resident credentials (passkeys): list (with user handle), delete, edit metadata”
   • [github] “fido2-manage is a tool allowing to manage FIDO2.1 devices over USB or NFC, including Passkey (resident keys) management”
   • [claimed-docs] “This tool streamlines the process of registering FIDO2 security keys in Microsoft Entra ID by leveraging the FIDO2 Provisioning Graph API.”
   • [probe] “PROBE runtime (recorded 2026-09-15): Token2's open-source fido2-manage — 'An open-source FIDO2.1 key management tool (with a GUI) under diff…”

   proof ↗⚑ flag

4. ai-native userSelf-host the core product

   weight 3 · round to Feitian FIDO Keys
   Feitian FIDO Keys~partialclaimed5/10

   The FIDO key is inherently a local, on-device hardware authenticator (not a hosted service), and Feitian explicitly documents that users can build firmware from Google's open-source OpenSK repository and provision it onto the hardware themselves, giving genuine control over the 'core product' without vendor cloud dependency. This is a reasonable analog to self-hosting for a hardware device, but it's not a full self-hostable software stack with deployment docs, and there's no evidence of self-hosted backend/server components (e.g., FIDO server, attestation service) that would round out a complete self-hosting story. Missing for 10: documentation of self-hosting any server-side/relying-party components, deployment guides beyond firmware flashing, and independent confirmation of OpenSK build success.

   • [claimed-docs] “Users can build firmware from the source code of Google OpenSK Github repository without changing anything, provision it to this OpenSK hard…”
   • [claimed-docs] “Users can build firmware from the source code of Google OpenSK Github repository without changing anything, provision it to this OpenSK hard…”

   proof ↗⚑ flag

   Token2—none0/10

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

   ⚑ flag

1. ai-native userControl data retention and deletion

   weight 2 · round to Token2
   Feitian FIDO Keys—none0/10

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

   ⚑ flag

   Token2~partialclaimed5/10

   Token2's tools give users direct control to delete data stored on their own security keys — resident credentials/passkeys can be listed, edited, and deleted, biometric templates can be deleted, and factory resets are supported (token2-gh-1, token2-gh-3, token2-docs-7). This covers device-level data deletion but there is no documentation of server-side retention policies, account-level data deletion, or how long any cloud-side telemetry/data is retained. Missing for 10: server-side/account data retention policy documentation, explicit data-deletion request process for any cloud-stored data, independent confirmation of retention practices.

   • [github] “Resident credentials (passkeys): list (with user handle), delete, edit metadata”
   • [github] “PIN management: set, change, set minimum PIN length, min-PIN-length RP allow-list... Biometric templates (bio models): list, rename, delete,…”
   • [claimed-docs] “It provides a simple interface to view device information, manage passkeys, change PINs, and perform factory resets.”
   • [claimed-docs] “fido2-manage is an open-source tool allowing to manage FIDO2.1 devices over USB or NFC, including Passkey (resident keys) management. It als…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Feitian FIDO Keys—none0/10

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

   ⚑ flag

   Token2—none0/10

   The evidence pack contains no mention of telemetry, analytics, or usage tracking, nor any settings to opt out of such tracking, for Token2's desktop companion app, fido2-manage tool, or web tools. missing for 10: any documentation of data collection practices, a privacy policy reference, or a telemetry opt-out mechanism.

   ⚑ flag

Credential management

1. power userList and delete the passkeys stored on my key and know its credential capacity before it fills up

   weight 2 · round to Token2
   Feitian FIDO Keys~partialclaimed4/10

   FEITIAN provides tools (SK Manager, iePassManager) described as managing 'FIDO PIN and credential related operations' on the key, implying some list/delete capability, and one product page claims 'no limit to accounts' for the MultiPass key. However, there is no explicit documentation of a list/delete-passkey UI, no discussion of credential capacity limits for other models, and no guidance on capacity awareness before a key fills up. missing for 10: explicit list/delete UI screenshots or steps, documented per-model credential capacity limits, and warnings/behavior when storage is full.

   • [claimed-docs] “Learn how to use FEITIAN SK Manager tool to manager your security key 's functions including FIDO, PIV, OTP.”
   • [claimed-docs] “Learn how to use iePassManager at Android OS to manage your FIDO devices(including FIDO PIN and credential related operations).”
   • [claimed-docs] “There is no limit to the number of accounts registered in MultiPass FIDO® Security Key.”

   proof ↗⚑ flag

   Token2~partialprobed7/10

   fido2-manage (with GUI and CLI) lists resident credentials/passkeys with user handle, allows delete and edit metadata, and works over USB/NFC for any FIDO2.1 device, directly covering list/delete of passkeys stored on the key. However, there is no explicit evidence of a feature reporting remaining credential capacity or slot count before the key fills up. Missing for 10: explicit credential-capacity/slots-remaining reporting, independent hands-on confirmation of listing/deleting behavior.

   • [github] “Resident credentials (passkeys): list (with user handle), delete, edit metadata”
   • [github] “fido2-manage is a tool allowing to manage FIDO2.1 devices over USB or NFC, including Passkey (resident keys) management”
   • [github] “PIN management: set, change, set minimum PIN length, min-PIN-length RP allow-list... Biometric templates (bio models): list, rename, delete,…”
   • [claimed-docs] “It provides a simple interface to view device information, manage passkeys, change PINs, and perform factory resets.”
   • [claimed-docs] “fido2-manage is an open-source tool allowing to manage FIDO2.1 devices over USB or NFC, including Passkey (resident keys) management. It als…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Token2's open-source fido2-manage — 'An open-source FIDO2.1 key management tool (with a GUI) under diff…”

   proof ↗⚑ flag

Fido2

1. security engineerThe key stores discoverable FIDO2 credentials (resident keys / device-bound passkeys) so users can sign in to WebAuthn services without typing a username

   weight 3 · round to Token2
   Feitian FIDO Keys~partialclaimed5/10

   Feitian's keys are explicitly W3C WebAuthn/FIDO2 compliant and marketed for passwordless sign-in scenarios like Windows Hello and Google Advanced Protection, which typically rely on discoverable credentials, but the evidence never explicitly names 'resident keys' or 'discoverable credentials' or confirms a specific stored-credential capacity/no-username login flow. Missing for 10: explicit documentation of resident-key/discoverable-credential support, stated credential storage limits, and a hands-on demonstration of username-less WebAuthn sign-in.

   • [claimed-docs] “Fully compatible to W3C's Web Authentication Standard with HID interface. Plug in and secure your web applications easily.”
   • [claimed-docs] “Seamlessly support Windows Hello (Within an Azure AD).”
   • [claimed-docs] “Introduction about how FEITIAN Security Keys works with Google advanced protection.”
   • [claimed-docs] “Users can build firmware from the source code of Google OpenSK Github repository without changing anything, provision it to this OpenSK hard…”

   proof ↗⚑ flag

   Token2✓fullprobed8/10

   Token2 sells FIDO2 hardware keys explicitly supporting resident/discoverable credentials (passkeys), with documentation and an open-source companion tool (fido2-manage) that lists, edits, and manages resident credentials including user handles, plus a browser-based demo to register and authenticate via WebAuthn without typing a username. Independent GitHub evidence corroborates the resident-key management feature set (list with user handle, delete, edit metadata). missing for 10: no explicit third-party/independent test confirming passwordless username-less sign-in flow in production RP scenarios, and no FIDO Alliance certification citation for discoverable credential compliance.

   • [github] “Resident credentials (passkeys): list (with user handle), delete, edit metadata”
   • [github] “fido2-manage is a tool allowing to manage FIDO2.1 devices over USB or NFC, including Passkey (resident keys) management”
   • [claimed-docs] “Register a security key or passkey, then log in with it — all in your browser using the WebAuthn API.”
   • [claimed-docs] “It provides a simple interface to view device information, manage passkeys, change PINs, and perform factory resets.”
   • [claimed-docs] “fido2-manage is an open-source tool allowing to manage FIDO2.1 devices over USB or NFC, including Passkey (resident keys) management. It als…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Token2's open-source fido2-manage — 'An open-source FIDO2.1 key management tool (with a GUI) under diff…”

   proof ↗⚑ flag

2. power userThe key works as a WebAuthn/U2F second factor across the major services I already use — Google, GitHub, Microsoft, password managers

   weight 2 · round to Feitian FIDO Keys
   Feitian FIDO Keys~partialclaimed7/10

   First-party docs confirm W3C WebAuthn/U2F compliance and dedicated guides for GitHub (OpenSSH), Microsoft/Azure AD, and Google Advanced Protection, showing broad cross-service compatibility. Missing for 10: explicit password-manager (e.g., 1Password/Bitwarden) integration guidance and independent/hands-on verification beyond vendor documentation.

   • [claimed-docs] “Fully compatible to W3C's Web Authentication Standard with HID interface. Plug in and secure your web applications easily.”
   • [claimed-docs] “Learn how to apply FEITIAN FIDO security keys with OpenSSH connections including remotely connecting Github and Linux server.”
   • [claimed-docs] “Learn how to use your FEITIAN FIDO2 security key to protect your Azure AD joined Windows 10.”
   • [claimed-docs] “Learn how to use your FEITIAN FIDO2 security key to protect your Microsoft application.”
   • [claimed-docs] “Introduction about how FEITIAN Security Keys works with Google advanced protection.”

   proof ↗⚑ flag

   Token2~partialclaimed6/10

   Token2 provides standards-based FIDO2/WebAuthn/U2F hardware keys with strong first-party tooling for Microsoft Entra ID enrollment and a general WebAuthn demo/testing tool, implying broad cross-service compatibility as a certified FIDO2.1 device. However, there is no direct documentation or independent confirmation of successful registration/use with Google, GitHub, or specific password managers. Missing for 10: explicit vendor or third-party evidence of working as a 2FA/passkey with Google, GitHub, and named password managers.

   • [claimed-docs] “This tool streamlines the process of registering FIDO2 security keys in Microsoft Entra ID by leveraging the FIDO2 Provisioning Graph API.”
   • [claimed-docs] “Register a security key or passkey, then log in with it — all in your browser using the WebAuthn API.”
   • [claimed-docs] “This manufacturer-agnostic tool works with any FIDO2.1 device.”
   • [claimed-docs] “Explore FIDO2 and passkey authentication hands-on. Register a security key or passkey, then log in with it — all in your browser using the W…”
   • [github] “fido2-manage is a tool allowing to manage FIDO2.1 devices over USB or NFC, including Passkey (resident keys) management”

   proof ↗⚑ flag

User verification

1. security engineerThe key supports on-device user verification — a FIDO2 PIN or built-in biometric — so a stolen key alone cannot authenticate

   weight 2 · round to Token2
   Feitian FIDO Keys✓fullclaimed7/10

   Feitian documents biometric (fingerprint) on-device user verification for BioPass keys, explicitly noting 'losing the key will cause no security risk at all,' and separately documents FIDO PIN management via iePassManager for PIN/credential operations, satisfying the on-device UV requirement. Missing for 10: independent/hands-on verification of PIN enforcement or biometric FAR/FRR, and no explicit CTAP2 'uv' flag documentation.

   • [claimed-docs] “Biometric technology makes BioPass FIDO2 Security Key one of the most secure tokens.”
   • [claimed-docs] “The fingerprint module prevents any misuses of the token from people other than authorized user, and losing the key will cause no security r…”
   • [claimed-docs] “Learn how to use iePassManager at Android OS to manage your FIDO devices(including FIDO PIN and credential related operations).”
   • [claimed-docs] “Learn how to use FEITIAN SK Manager tool to manager your security key 's functions including FIDO, PIV, OTP.”

   proof ↗⚑ flag

   Token2✓fullprobed8/10

   Evidence confirms FIDO2 PIN setup/change and biometric template enrollment/management via the companion tool and fido2-manage (PIN management, min PIN length, biometric templates: list, rename, delete, enroll), and browsers/OS natively prompt for PIN when required, satisfying on-device user verification against theft. missing for 10: no independent/hands-on third-party testing confirming UV enforcement during actual authentication ceremonies, and no explicit CTAP2 'uv' flag/attestation documentation.

   • [github] “PIN management: set, change, set minimum PIN length, min-PIN-length RP allow-list... Biometric templates (bio models): list, rename, delete,…”
   • [claimed-docs] “It provides a simple interface to view device information, manage passkeys, change PINs, and perform factory resets.”
   • [claimed-docs] “No special tool installation is needed to start using the FIDO keys, as most modern browsers will prompt to set a PIN when required”
   • [claimed-docs] “fido2-manage is an open-source tool allowing to manage FIDO2.1 devices over USB or NFC, including Passkey (resident keys) management. It als…”
   • [probe] “PROBE runtime (recorded 2026-09-15): Token2's open-source fido2-manage — 'An open-source FIDO2.1 key management tool (with a GUI) under diff…”

   proof ↗⚑ flag