Overview
Different capabilities have different access requirements. Recognizing a crawler, collecting an AI answer and preparing an advertisement are separate operations. Use the relevant table below, then confirm the options shown in your account.
Crawler detection and routing evidence
| Category | What the available evidence means | What to confirm for your site |
|---|---|---|
| Google/Bing-classified activity | PB can classify matching recorded request user agents in activity reporting | Correct hostname/integration, actual request and delivery evidence |
| AI-related classified activity, including OpenAI, Perplexity, Anthropic/Claude, Gemini, Grok and Copilot patterns | Recorded requests can be grouped by recognized patterns | A recorded row is not an authenticated operator identity or evidence of an answer citation |
| Meta-related request patterns | Source has separate classification for matching Meta-related user agents | Detailed operator purposes and robots behavior require current official verification before explanatory role copy is published |
| Rendered content delivery | A request may carry delivery-source and rendered-content-access evidence | Check that particular row; a successful origin response alone does not verify rendered delivery |
Classification support does not establish that every request is routed through PB or that a provider will index, train on, cite or recommend the page. Confirm the integration and actual delivery path for the site.
AI monitoring providers
| Provider identifier / label | Implementation evidence | Customer access boundary |
|---|---|---|
| OpenAI | Configurable answer-provider adapter | Use only when enabled and available to the workspace |
| Perplexity | Configurable answer-provider adapter | Same; record the actual provider/model context |
| Anthropic | Configurable answer-provider adapter | Same; API observations can differ from consumer-app sessions |
| Gemini | Configurable answer-provider adapter | Same; confirm current provider configuration |
| Grok | Configurable answer-provider adapter | Same; confirm current provider configuration |
| Meta | Optional adapter/configuration exists | Optional capability; confirm whether it is enabled for your workspace |
Source presence is not deployment enablement. Do not infer that all listed providers run in every account or collection.
Advertising providers
| Capability | PB workflow boundary | Prerequisites |
|---|---|---|
| ChatGPT / OpenAI Ads | Creative preparation, checks, handoff and supported imported reporting | Eligible PB Ads access; separate provider-controlled advertising access for connected functions |
| Official provider preview | Preview associated with a linked external ad | Connected account and usable external ad link; PB draft alone is insufficient |
| Campaign management | Automatic creation, activation, pausing and budget management are outside the inspected PB workflow | Complete the appropriate provider workflow separately |
| Other advertising providers | No additional generally available PB integration established by this review | Verify implementation, access and approved release before adding a provider |
Plan capabilities
| Capability | Where effective availability comes from | Customer action |
|---|---|---|
| Sites and fresh renders | Workspace catalog, subscription/trial, stored allowances and applicable add-ons | Read the account's current usage period and limits |
| AI prompts, cadence and history | Effective monitoring entitlement and enabled configuration | Check the limits and available cadence options in the workspace |
| Page-health monitoring and URL capacity | Effective automation/URL allowance | Inspect monitoring settings and configured URL count |
| Agent and content generation | Effective feature and usage allowance | Review the relevant usage display and available controls |
| Developer API and authenticated MCP | Effective API entitlement plus granted key scopes | Check API access, then issue only the required scopes |
| AI Ads | Effective optional add-on and provider prerequisites | Review the available offer and successful activation state |
A plan name alone may not describe a legacy account's effective access. This page does not introduce a new public price catalog or automatically migrate an existing subscription.
Public versus authenticated developer tools
| Tool surface | Access | Execution and scope |
|---|---|---|
| Public checker / public MCP HTTP tools | Approved public URLs; no workspace key for the public MCP checks | HTTP evidence; local MCP does not perform browser rendering |
| Workspace MCP reads | Eligible account and scoped key | Local stdio server reads bounded saved workspace evidence; no current mutations |
| Managed Developer API | Eligible account and scope-appropriate Bearer key | API contract includes rendering/operations and workspace reads; do not equate its whole surface with read-only MCP |
| Self-hosted engine | Operator's infrastructure and release setup | Separate engine deployment; does not grant managed dashboard entitlement |
| Plugin packaging | Depends on package/client validation | Codex local alpha validation exists in reviewed source; Claude native package validation remains pending; no universal marketplace claim |
Review the developer tools overview and the limits and setup shown in your account.