An AI chatbot you can audit: read the code, inspect the prompts
SleekAI ships as unobfuscated PHP and JavaScript. Read the source, inspect the system prompts at request time, and trace every variable from data mapper to model call. Bring your own OpenAI, Anthropic, Google, or OpenRouter key.
Black-box AI is a trust problem
Closed AI chatbots ask the merchant to trust three layers blindly: the system prompt sent to the model, the data mapping that decided which fields ended up in that prompt, and the routing logic that picked the model and tracked the conversation.
Vendors keep all three opaque, partly for IP protection, partly because revealing the system prompt would reveal how thin the engineering often is. The merchant sees a chat widget and a settings page. Everything between user input and model output is a black box.
SleekAI ships its plugin code unobfuscated. The PHP files in wp-content/plugins/sleek-ai/ are readable. The data mapper resolves variables in PHP that you can step through with Xdebug, Query Monitor, or plain logging. Every hook, every filter, every database write is inspectable.
Features
Readable plugin code
Every PHP file in the plugin is readable in your editor. No license-key-protected ioncube wrappers, no minified PHP via PHP-Beautifier-tricked output. What you see in the file is what runs at request time.
Inspectable prompts
The model never sees more than what you can see.
Answers from your data
Map post titles, content, post meta, taxonomies or a WP_Query into the instruction, and the bot answers from what your site actually publishes.
Where transparent bots earn their keep
Engineering-led teams
Teams whose engineers have the time and instinct to read plugin code before adopting it prefer tools that reward the reading rather than punish it.
Security-conscious deployments
Security teams that run static analysis on plugin code as part of intake gain real signal from unobfuscated source rather than guessing at obfuscated binaries.
Repeat questions
Answer the questions visitors ask every day from the pages and posts where you already answer them.
How SleekAI stays transparent
Ship readable code
PHP files are committed to the plugin ZIP as plain text. No PHP-side obfuscator runs at build time. Auditors and developers can read the request handler, data mapper, and provider client directly without decompilation.
Map your data
Choose the posts, fields, taxonomies or users the bot should know and reference them in the instruction.
Pick a model
Store your OpenAI, Anthropic, Google or OpenRouter key once in the shared AI settings, or add a compatible endpoint, and choose the chatbot’s model.
Set display conditions
Decide which pages, post types, roles or logged-in states show the chatbot.
Why transparency matters more than the license badge
Open source in the OSI sense is a strong norm in WordPress culture, since WordPress itself is GPL. The instinct to favor open source over closed source is well calibrated for most plugin categories.
AI chatbots, however, sit in a category where the model itself is usually closed and the data wiring is what merchants need to inspect. You can read every line that touches your data. You can modify the plugin for your own site. The badge is not the safety check. The readable code is.
Frequently asked questions
Can I modify the code for my own site?
Yes. Common modifications include custom data source adapters, alternative widget chrome, and per-site integrations with other plugins.
Are there hidden minified scripts?
The PHP side is plain text, no encoder, no ioncube, no Source Guardian.
Where can I read the code right now?
After installing the plugin, the source lives at wp-content/plugins/sleek-ai/. Public sample snippets and the changelog live on the SleekAI website.
What about the underlying models?
The model is a separate concern from the plugin. OpenAI’s, Anthropic’s, and Google’s models are closed-weight. If you need open-weight models, route through OpenRouter to a Llama 3, Mistral, or DeepSeek endpoint, or run a self-hosted vLLM or Ollama backend. SleekAI itself does not constrain the model layer.
Which AI providers does it support?
OpenAI, Anthropic, Google and OpenRouter, plus custom OpenAI-compatible endpoints. You bring your own API key and the provider bills you directly.
Where does the chatbot get its answers?
From the WordPress data you map into its instruction: post titles and content, post meta, ACF and Meta Box fields, taxonomies, terms, users and user meta, or a WP_Query. Values resolve on every request.
Can it act on a visitor’s behalf?
No. A chatbot answers questions. It does not submit forms, create bookings, open tickets or send email; put the links for those steps in its instruction so it can point visitors to them.
Can I control where the chatbot appears?
Yes. Display conditions cover post type, post, post status, post template, taxonomy, term, user role, logged-in state and WordPress conditional tags such as front page, archive, search and 404.
Related pages
Pricing
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
…or get the Bundle Deal
and save €250
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
SleekAI
SleekByte
SleekMotion
SleekPixel
SleekView
SleekRank
SleekTrack