WP Suite AI-Kit — Private WP AI, Grounded Answers & Structured Content

AI-Kit combines a site-wide chatbot, semantic DocSearch, selected structured WordPress facts and controlled access to services. WordPress remains your editorial source; the configured AI backend can run in your own AWS account.

• Chatbot (Pro): Answer visitor questions about services, products and documentation with configurable instructions and response rules.
• Semantic DocSearch (Pro): Search approved knowledge and return relevant sources, summaries and citations.
• Governed knowledge: Select posts, pages and supported custom post types with filters and source policies.
• Knowledge Sync: Review and synchronize selected content; inspect ingestion state. Compatible Static Publisher workflows can synchronize after verified public releases.
• Evidence controls: Define required sources and insufficient-evidence behavior.

A chatbot can find the right page but miss a price or specification stored in a custom field. AI-Kit lets you select registered public custom fields for typed Knowledge Sync. With a compatible backend, profile-scoped, read-only own-content record/schema tools can retrieve selected source-bound facts alongside semantic search.

This does not automatically expose private fields or guarantee answer accuracy. Field eligibility, source approval, backend ingestion, access controls and actual answers should be verified.

Extend answers beyond indexed pages with administrator-approved REST/MCP tools and permitted web-grounding sources. Configure access to live product, service or business information, with read-only retrieval or explicitly permitted actions according to tool permissions.

Universal Commerce Protocol (UCP) support includes a Shopify adapter for supported commerce and product-discovery integrations. Available adapter operations depend on the deployed backend and configuration. This listing does not imply checkout, payment processing or order-changing capabilities.

External integrations need compatible endpoints, explicit setup, authentication and appropriate permissions.

Supported on-device features in compatible desktop Chrome environments help with writing, rewriting, translation, proofreading and image/SEO metadata. Media Library bulk workflows support review before saving. Local-only tasks do not require an AI provider account.

Pro can add front-end AI Feature blocks/shortcodes for supported summarizing, writing, rewriting, translation and proofreading workflows, with configured backend-only or fallback execution where available.

• Customer-owned AWS option: Deploy a serverless API through API Gateway and Lambda, with optional Amazon Bedrock Knowledge Base, into your AWS account.
• Explicit processing boundaries: Supported local tasks stay on-device; backend tasks call the endpoint configured for the site. Data paths depend on the deployment.
• Static-friendly frontend: Browser-facing chatbot and search can call the configured AI backend without proxying each request through public WordPress/PHP.
• Security: Supported deployments may use IAM/Cognito, throttling, AWS WAF and optional reCAPTCHA.
• Costs: AWS infrastructure and model/provider usage costs are separate from WP Suite subscriptions and implementation services.

• Answer questions about services and products with sources.
• Search WordPress documentation with semantic DocSearch and citations.
• Retrieve selected public custom-field facts, when supported by the backend.
• Connect approved REST/MCP tools and supported UCP/Shopify product information.
• Keep knowledge aligned with approved content and verified static releases.
• Offer chatbot and search on a statically delivered WordPress frontend.
• Assist editors with translation and metadata.

Remote implementation can cover chatbot/DocSearch setup, source selection, ingestion checks, field mapping, AWS deployment, security, REST/MCP/UCP integration, Shopify adapters and static-site rollout.

Availability: Visitor chatbot, DocSearch, structured record lookups, connected services and UCP features require the appropriate entitlement, compatible backend and explicit configuration. On-device features depend on browser/device support. Capabilities vary by integration and deployment; no specific answer accuracy or commerce transaction workflow is guaranteed.