Configure PagibleAI CMS

Configure only the services behind the PagibleAI features you plan to use. Unused API keys can stay unset, so you can start with a small setup and add integrations when you need them.

Choose the services you need

Each guide takes you from provider signup to the environment values required by PagibleAI.

Google Gemini

Generate text and images, power the admin AI chat, edit images, and analyze image, video, and audio content. Configure Google Gemini.

OpenAI

Transcribe audio and provide the default text-refinement service. Configure OpenAI.

Mistral

Use Mistral as an alternative provider for content generation. Configure Mistral.

Clipdrop

Erase selected objects, remove backgrounds, extend images, and upscale them with a compatible API key. Configure Clipdrop for PagibleAI.

DeepL

Translate pages and reusable content between languages. Configure DeepL.

Google Search Console

Connect Search Console and Chrome UX Report data for search and real-user performance metrics. Configure Google Search Console.

hCaptcha

Protect contact forms from spam and automated submissions. Configure hCaptcha.

robots.txt & sitemaps

Maintain crawler rules and security contacts on the root page and serve XML and news sitemaps. Configure robots.txt, security.txt and sitemaps.

MCP server

Let external AI agents and assistants manage pages, elements, and files through the MCP tools. Configure MCP.

Recommended starting point

For the full default creative toolset, configure Gemini, OpenAI, DeepL, and a compatible Clipdrop key. Clipdrop now directs new API customers to Jasper while PagibleAI still calls Clipdrop endpoints, so review Configure Clipdrop for PagibleAI before requesting access.

Add hCaptcha when your site uses public forms, and connect Google Search Console when you want search and CrUX reporting. Mistral is an optional alternative for content generation. Store every credential in your .env file or deployment secret store; never add API keys to CMS content or source control.

AI chat

The AI chat in the admin panel uses the write service (CMS_AI_WRITE, Gemini by default), so it needs CMS_AI_WRITE_API_KEY. It works with the CMS tools for pages, shared elements and files, and can use the provider's web search and web fetch tools if the provider supports them.

The chat requires the page:chat permission for pages, element:chat for shared elements and file:chat for files. The built-in publisher, editor and admin roles include them; add them to custom roles as needed.

AI limits

These optional settings in config/cms/ai.php cap the cost and runtime of AI requests:

CMS_AI_MAXSTEPS (default 25) limits the number of tool-calling steps of a single admin AI chat request.
CMS_AI_MAXTOKEN limits the tokens a provider may generate per request; leave it empty to use the provider or model default.
CMS_AI_TIMEOUT (default 300) sets the maximum number of seconds an AI request may run, both for the provider connection and the PHP execution time.
CMS_AI_MAXINPUT (default 1048576) limits the serialized size in bytes of the input sent to a provider.
CMS_AI_MAXDEPTH (default 20) limits the nesting depth of structured content passed to the AI.

AI requests are additionally throttled by the cms-ai rate limiter to 10 requests per minute per user.

Robots, security contacts and sitemaps

/robots.txt, /security.txt and the XML and news sitemaps are generated from the root page configuration and the published page tree. See robots.txt, security.txt and sitemaps for setup and troubleshooting.