External services CheckFox integrates with.
Browserless (scanner)
Powers automated scanning of samples. The scanner runs the page in a headless browser, runs axe-core together with CheckFox's own rules, maps what it finds to the audit's referential criteria, and proposes findings for auditor review.
- Included from the Pro plan; available as the Scanner add-on on Free and Starter.
- Workspaces may use CheckFox's shared Browserless key or provide their own (BYOK). The shared key is metered per month; a BYOK key is not.
- Output is always reviewed by the auditor before being persisted as findings.
See procedures / use the scanner.
Issue trackers
Findings can be pushed as issues to the tool the remediation team already uses. Included from the Starter plan, and available as the Integrations add-on on Free.
- Jira - workspace-level connection, per-audit field mapping, and an optional Jira workspace assigned per CheckFox workspace.
- GitHub - issues pushed to a chosen repository.
- Linear - issues pushed to a chosen team.
A finding that has been pushed keeps a reference to its ticket, so the same failure is not pushed twice.
Browser extension
A Chrome and Firefox extension that runs scans in the auditor's own browser, with no headless infrastructure, and pushes pre-filled findings into the matching audit. It reaches CheckFox with an API key.
API keys
API keys belong to the user, not to the workspace. A key is single-purpose: either a browser-extension key or an MCP key, never both. An extension key reaches every audit its owner can reach; an MCP key is checked per audit against the MCP entitlement of that audit's workspace. Keys are created in user settings and the key itself is shown once, at creation.
MCP
An MCP key connects an AI agent to CheckFox so it can work through an audit criterion by criterion. See mcp.
AI features
The AI add-on unlocks the CheckFox assistant and AI fix suggestions on a failing criterion. It is an add-on on every plan, never bundled, and it carries a monthly credit budget.