Developer automation connects PageLens AI to the tools your team already uses to ship websites. Instead of remembering to start every scan manually, you can trigger checks from scripts, CI, deploy hooks, or AI assistants.
What developer automation includes
PageLens AI supports two automation patterns:
- Scan automation: API keys, CLI scans, GitHub Actions and deploy hooks that create scans from trusted workflows.
- Assistant automation: MCP connections that let approved AI assistants inspect reports, summarize findings, submit feedback and record accepted decisions.
Use scan automation when you want PageLens AI to run. Use MCP when you want an AI assistant to work with an existing report.
Plan availability
Scan automation is available on Solo, Pro and Agency plans. Free accounts can run manual scans and use their included monthly allowance, but API keys, CLI scans, GitHub Actions and deploy hooks require Solo or higher.
| Plan | Scan automation | | --- | --- | | Free | Not included | | Solo | Included | | Pro | Included | | Agency | Included |
MCP connections are managed separately from scan automation. Only approve MCP clients you trust, and revoke access when a tool is no longer needed.
Where to configure it
Go to Settings -> Integrations.
Use Developer access to:
- create API keys
- create deploy hooks
- review key prefixes and last-used dates
- revoke leaked or unused credentials
Use MCP clients on the same page to review and revoke assistant connections.
Common workflows
Teams use developer automation to:
- run a scan after production deploys
- scan a staging URL before launch
- check a client page before handoff
- include PageLens AI in a GitHub Action
- let an AI assistant turn report findings into implementation tasks
- keep launch QA close to the release process
Quotas and safe usage
Automated scans use your normal plan limits. Solo includes 300 scans/month and 10 Deep AI Audits/month. Pro includes 1,500 scans/month and 50 Deep AI Audits/month. Agency includes 10,000 scans/month and 250 Deep AI Audits/month.
Keep keys in secret managers, not source code. Use separate keys or hooks for separate workflows where possible, and revoke anything you do not recognize.
Learn more
For the focused API, CLI, GitHub Action and deploy-hook details, read Scan automation, API keys, CLI and deploy hooks.
For AI assistant access, read MCP, agent feedback, and accepted decisions.