WhoCites
WhoCites for AI Agents - Visibility Tests Inside Builder Workflows
WhoCites brings the visibility test for AI-built apps into agent workflows. Agents can create paid Stripe Checkout, read owned report JSON, pull builder-ready fixes, start the owned post-fix re-scan, and verify opted-in public scan proof without bypassing the payment or privacy boundaries.
Run an AI visibility scanHosted MCP endpoint
The hosted MCP endpoint is https://whocites.com/api/mcp. It supports initialize, tools/list, and tools/call for the WhoCites tool surface.
Agent repair loop
The agent flow is: create checkout, wait for payment-backed scan completion, read the owned report, apply fixes in the builder, and re-scan to prove movement.
Available tools
The MCP surface exposes five tools.
- whocites_start_scan(domain)
- whocites_get_report(auditId)
- whocites_get_fixes(auditId)
- whocites_start_rescan(auditId)
- whocites_verify_public_scan(token)
Payment and privacy boundaries
$49 checkout remains the gate before scan-provider calls. Owned report, fix, and re-scan actions require report ownership and omit customer contact data, Stripe IDs, raw AI excerpts, and citation URLs.