POST /api/v1/scans
Queue a scan from a trusted script, deploy hook or CI workflow.
Developer automation
Put PageLens AI in your delivery workflow.
Run audits from CI, deploy previews, release scripts, or your AI coding assistant. PageLens AI developer access is for teams that want website QA to happen repeatedly, not only when somebody remembers to open a dashboard. API keys, CLI scans and deploy hooks are included on Solo, Pro and Agency plans.
Choose the surface that matches the job.
Every surface exists for a different part of the same workflow: trigger scans, inspect reports, and turn findings into fixes.
CLI
Run PageLens AI scans from a terminal, CI job, preview deploy, or agency release checklist.
Open CLI docsAPI keys
Create scoped keys for programmatic scans without using a browser session.
Create a keyGitHub Action
Trigger PageLens AI from pull requests and post score or regression context back into review.
Set up accessDeploy hooks
Connect release events to PageLens AI so checks happen when production or preview URLs change.
Create a hookMCP for agents
Let Cursor, Claude, Codex, or another MCP client read reports and work the fix list with context.
Connect MCPBuilt around the automation that exists today.
PageLens AI developer access is intentionally focused: trigger scans, inspect status, use reports with agents, and wire those steps into release workflows before adding more platform-specific plugins.
GET /api/v1/scans/{id}
Read scan status, score, report URL and regression context.
GitHub Action
Pin production workflows to a release tag such as v1.
MCP
Use agents to inspect reports and work accepted-decision context, not as the scan trigger.