PageFox developer documentation
Pull data on your own schedule with the REST API, react to events as they happen with webhooks, or let an agent ask a site a question directly.
Three surfaces, each documented against the code that implements it
GET https://pagefox.co/api/v1/openapi.jsonThe public REST contract · OpenAPI 3.0
Three surfaces. Start here.
REST API
Read websites, leads, companies, visits and conversations from a trusted server.
Business plan · scoped keys · 60 requests per minute per key
/docs/webhooksWebhooks
Receive signed events the moment they happen instead of polling. Nine event types, one endpoint.
Growth and above · organization owner configures · 3 delivery attempts
/docs/askSite answers
Ask an opted-in website one grounded question over plain HTTP and get cited sources back.
Growth and above · no API key · 500 answers per site per day
/docs/claudeClaude connector
Add PageFox to Claude as a connector: read today's list and lead briefs, and log what happened.
Business plan · OAuth sign-in · never sends to a prospect
Which one do you want?
- A nightly CRM sync, or a backfill.REST API: it paginates and you control when it runs.
- Something must happen within seconds of a lead going hot.Webhooks. Reconcile with the REST API afterwards; there is no delivery replay.
- An AI client needs one factual answer about a public site.Site answers, if that site's owner has enabled it.
- A person is doing the work.Stay in the dashboard.
- You just need the script on the page.Install guide: the one line, where it goes on each stack, and how to confirm it is live.
Not available yet.
Everything public today is read-only. PageFox does not currently publish a supported SDK, a write API, an MCP server, a general agent connection, an A2A endpoint, a connector guarantee, an SLA, or a real-time stream. The canonical wire contract for the REST surface is the public OpenAPI 3.0 document.