Overview
Capabilities depend on the effective account, configuration and action surface. The platform can publish reviewed articles through supported connections even though Buddy and MCP expose narrower tools. How PB Works explains the connected workflow.
Crawler detection and routing evidence
| Category | Available evidence | Site requirement or boundary |
|---|---|---|
| Search and AI-related request patterns | Recorded requests can be classified by supported user-agent patterns | Classification is not authenticated operator identity or proof of indexing, training or citation |
| Meta-related request patterns | Matching Meta-related user agents can be classified separately | Keep request evidence separate from monitored provider answers; inspect actual routing and robots behavior |
| Rendered content delivery | Available response, delivery-source and rendered-content evidence | A successful origin response alone does not verify rendered delivery |
Crawler activity requires a connected request path and recorded evidence. It does not establish that every provider request reaches PB or that a provider will recommend the page.
AI monitoring providers
Supported configured answer-provider adapters include OpenAI/ChatGPT, Perplexity, Anthropic/Claude, Gemini, Grok and optional Meta AI/Muse. Provider selection and coverage depend on the workspace's plan, effective limits and enabled configuration; not every account or collection includes all providers.
These are controlled provider API observations, not private consumer conversations. Weekly tracking and optional eligible daily-slot access have separate allowances; historical restricted-pilot access is not the same as general plan access.
Articles and CMS publishing
Current Starter, Growth and Pro include eligible full-article generation and supported publishing connections. Generation uses retained answer evidence and readable owned-page context, requires confirmation and shares the workspace allowance across the application and authorized tools.
Review and approve an article before delivery. CMS drafts, explicitly confirmed publication and approved publication schedules differ. WordPress, Webflow, Shopify blogs, Wix blogs and Ghost can support their CMS draft/publication workflows; Astro requests a rebuild after feed release, and Keystatic releases through Git. Hosting completion remains separate. A custom publishing webhook needs its own publication verification.
Publishing requires a configured supported destination and the appropriate access; the optional human management purchase is not required for self-service CMS workflows. Read Article Generation, Integrations and the calendar guide.
Advertising providers
| Capability | Available workflow | Requirement or boundary |
|---|---|---|
| ChatGPT/OpenAI Ads | Creative preparation, checks, handoff and supported imported reporting | Eligible PB add-on/credits and separate provider access/configuration for connected functions |
| Official provider preview | Preview for a usable linked external ad | A PB draft alone does not establish a linked provider ad or publication |
| Campaign management | Automatic creation, activation, pausing and budget management are outside the current workflow | Complete the provider's campaign process separately |
An eligible PB add-on cannot grant advertising-provider access. Imported reporting does not establish exact-prompt causal attribution.
Plan capabilities
| Capability | Effective access | What to confirm |
|---|---|---|
| Sites and fresh renders | Current catalog, subscription/trial, overrides and applicable add-ons | Active sites, usage period and remaining allowance |
| AI Visibility and competitor/source evidence | Current eligible tracking plan and provider configuration | Questions, provider set, cadence, history and coverage |
| Page Health and monitored URLs | Manual/automated monitoring entitlement and URL capacity | Configured URLs, cadence and alerts |
| Full article drafts | Eligible content access and shared generation allowance | Available retained evidence, site context and explicit generation confirmation |
| CMS delivery and publication schedules | Eligible publishing account and usable destination | Reviewed version, destination and release/schedule confirmation |
| Buddy | Available site/workspace evidence and message allowance | Read/explain assistance; no autonomous generation, publishing, repairs or spending |
| Developer API | Current Starter/Growth/Pro or effective legacy entitlement | Operation-specific scopes and existing allowances |
| Optional human account management | Eligible current monthly software plan and separate management enrollment | Bounded reviewed outputs, monthly human review/report and approved publishing help |
| AI Ads | Eligible optional add-on, credits and provider prerequisites | Active access, configuration and reporting availability |
Trial and legacy limits can differ from a current public plan name. Pricing describes the offers; the account reports effective access. API or assistant access does not create additional generation or rendering allowance.
Public versus authenticated developer tools
| Tool surface | Access | Execution and scope |
|---|---|---|
| Public web tools | Public URL and the tool's usage limits | Focused page evidence; rendering support differs by tool |
| Local CLI and MCP public diagnostics | No workspace key for public checks | HTTP diagnostics without browser JavaScript execution |
| Published local MCP workspace reads | Eligible scoped API key | Bounded saved evidence and content metadata; no generation or publishing |
| Hosted MCP | Authorized compatible client and eligible scopes | Evidence, proposals and confirmed unapproved drafts; no approval, delivery or schedule tool |
| Developer API | Eligible workspace and operation-specific key scopes | Evidence/rendering operations plus reviewed article generation, approval, delivery and scheduling |
| Self-hosted engine | Operator-run deployment | Separate rendering core; no hosted dashboard, publishing or billing entitlement |
| Agent plugin | Host-specific package/setup support | The Cursor source package provides public diagnostics and optional read-only workspace evidence; manual installation and marketplace approval differ |
Automation installation also differs: n8n's published community node supports self-hosted installation, Zapier and Make use invitations, and Activepieces requires an eligible custom-piece deployment. Public-directory approval is separate. See the automation setup guide and developer tools.