You open a WordPress AI plugin and hit a credit meter. Fifty generations left. Mystery markup on every token. The model you already pay for at OpenAI, Anthropic, Google, or Moonshot sits unused while a middleman resells you a slower pool. That is not “AI for WordPress.” That is a vending machine bolted onto your dashboard.
Generatify Pro takes the opposite path: connect your own ChatGPT, Claude, Gemini, or Kimi account with an API key you supply. You pay the model provider directly for usage. There is no AI markup in DaftPlug’s price. The free version has no model connected. You can switch providers any time. Faster models suit quick tasks. More powerful models suit content generation. The assistants, helpdesk, compose tools, and automations all ride on that key. The key is the foundation. Everything else is what you build on it.
Generatify is the DaftPlug AI plugin. This post is about bring-your-own API key connectivity (ChatGPT, Claude, Gemini, Kimi), direct provider billing, free versus Pro model access, and switching providers. Not inventing credit packs. Not claiming the free plugin includes model access. Not rewriting every Generatify feature as if the topic were summarize-only or helpdesk-only. Those tools matter, and they depend on the key. For an editor-side example that assumes a connected model, keep WordPress AI summarize long-form content nearby.
What Generatify actually ships here
Stay inside the real feature set:
- Pro connectors for your own ChatGPT, Claude, Gemini, or Kimi account via an API key you supply
- You pay the model provider directly for usage
- No AI markup in DaftPlug pricing for that usage
- Free version has no model connected (connectors are a Pro feature)
- Switch providers any time
- Guidance to use faster models for quick tasks (for example alt text style work) and more powerful models for content generation
- Downstream Generatify surfaces (assistant, helpdesk, smart compose, content generation, automations, and related tools) run on the model you already connected
This post does not invent DaftPlug-sold token packs, “unlimited AI” claims, or a promise that free installs ship a hosted model. The FAQ is explicit: you need your own AI provider account, connectors are Pro, free has no model connected. Stay honest.
Why bring-your-own-key matters on WordPress
Cost transparency. Provider dashboards show tokens, rate limits, and invoices you can audit. Resold credits hide the real unit economics until the pack runs out mid-campaign.
No double margin. DaftPlug charges for the WordPress product (one Pro membership across plugins). Model usage is between you and OpenAI, Anthropic, Google, or Kimi. That split keeps incentives clean.
Model choice is strategy, not a SKU. Some days you want a fast model for alt text and short rewrites. Some days you want a stronger model for long drafts. Generatify lets you connect the account you already have and switch when the work changes.
Data and vendor posture stay yours. Your API relationship, spend caps, and provider-side controls remain in your cloud console. You are not trapped in a plugin-specific wallet when finance asks who approved AI spend.
Free stays honest. A free plugin that pretends to include “AI” without a model is worse than a free plugin that says connectors are Pro. Generatify’s free surface exists. Model connection does not. That clarity avoids support tickets rooted in false expectations.
Features share one connection. Assistant, helpdesk, compose, generation, and automations should not each demand a different credit system. One key, many tools. That is the architecture this post is about.
How to connect your own key in wp-admin
Assume Generatify is installed and you have an active Pro path for connectors (DaftPlug Pro membership or the Generatify Pro capability that unlocks connectors).
1. Create or open the provider account you already trust
Pick ChatGPT (OpenAI), Claude (Anthropic), Gemini (Google), or Kimi. Use whichever account your team already pays for when you can. Generate an API key in that provider’s console with the least privilege you need. Store it in a password manager. Do not paste keys into Slack.
2. Open Generatify connection settings
In wp-admin, open Generatify and find the provider / API key connection (Pro). Paste the key for ChatGPT, Claude, Gemini, or Kimi. Save. Confirm the plugin reports a healthy connection before you invite the whole editorial team to smash Generate.
If you are on free Generatify, expect no model connected. That is the product rule, not a bug. Upgrade when you are ready to attach your own provider.
3. Choose model class for the work you do most
Faster models suit quick tasks (alt text style passes, short rewrites, light classification). More powerful models suit content generation and longer drafts. Start with one default that matches your main workload. Switch when a campaign needs heavier writing. You can change providers any time. Document which provider is “production” so freelancers do not rotate keys casually.
4. Set spend guardrails at the provider
- Enable billing alerts in the provider console.
- Set hard or soft caps if the vendor supports them.
- Use a dedicated project or sub-account for WordPress if your org separates environments.
- Rotate keys if someone with dashboard access leaves.
Generatify runs on your key. Finance still owns the cloud bill.
5. Smoke-test the surfaces that matter to you
After connect:
- Run a small assistant or compose action on a staging post.
- Generate a short draft or summary you will discard.
- If you use helpdesk or automations, fire one low-risk path.
- Confirm usage appears in the provider dashboard (not a DaftPlug credit meter).
- Switch to a second provider on staging once, then switch back, so you know the “any time” path works before a production incident.
Nothing should go live until a human approves and publishes. Connection is not publication.
6. Keep secrets out of backups and tickets
Do not paste API keys into support threads. Do not commit them to git. If you restore a staging database from production, rotate keys if staging is widely shared. Treat the Generatify key like any other production secret.
What good looks like
- Generatify Pro is connected to ChatGPT, Claude, Gemini, or Kimi with a key you control.
- Usage bills at the model provider. There is no AI markup line item inside DaftPlug pricing for tokens.
- Free installs correctly show no model connected until Pro connectors are available.
- You can switch providers without rebuilding the site.
- Faster versus more powerful model choice matches the task mix (quick tasks vs content generation).
- Assistant, helpdesk, compose, generation, and automations share that connection instead of inventing separate wallets.
- You did not claim free includes hosted model access or invent DaftPlug credit packs.
If a feature fails with an auth error, check the provider key and billing status first. Most “AI is down” tickets are expired cards or revoked keys.
Pitfalls (the ones that bite)
Expecting free Generatify to answer with a model. Free has no model connected. Plan the Pro connector step explicitly.
Sharing one key across every client site without isolation. Agencies should separate keys or projects per client when contracts demand it.
Picking the strongest model for every alt-text pass. Cost and latency climb. Match model class to task.
Leaving unlimited spend with no alerts. A runaway loop or scraped form can burn budget. Set provider alerts the same day you paste the key.
Pastoring credit-pack marketing language. Generatify’s differentiator is direct provider pay. Do not reintroduce middleman myths in your own docs.
Testing only in the assistant and ignoring helpdesk. If visitors hit helpdesk on the same key, validate that path too.
Treating connection as optional for “just trying compose.” Without a connected model, generation features have nothing to call. Connect first.
Committing keys into migration zips. Scrub secrets when you hand databases between environments.
Practical checklist before you call it done
- Confirm Generatify Pro connectors are available on the site.
- Create an API key at ChatGPT, Claude, Gemini, or Kimi.
- Paste the key into Generatify and verify a healthy connection.
- Set provider billing alerts and caps.
- Pick a default model class for quick tasks versus content generation.
- Smoke-test one editor action and one visitor-facing action if you use helpdesk.
- Confirm usage appears at the provider, not as DaftPlug AI credits.
- Document which provider is production and who may rotate keys.
- Practice a provider switch on staging once.
- Remind the team: free means no model connected. Pro means your key.
Takeaway
WordPress AI that resells you mystery credits hides cost and locks your model choice. Generatify Pro connects your own ChatGPT, Claude, Gemini, or Kimi key so you pay the provider directly, with no AI markup in DaftPlug’s price. Free stays honest: no model connected until Pro connectors are in play. Switch providers when the work changes. Point faster models at quick tasks and stronger models at generation. Then let assistant, helpdesk, compose, and automations share that one foundation.
Generatify is built around that bring-your-own-key model rather than a token storefront. Connect once. Guard the bill at the provider. Keep humans in the publish loop.
One Pro membership unlocks Generatify plus Progressify, Lightify, Rankify, and Snapshotify. New Pro plugins join existing memberships. Plans differ by site count only (Pro $37.99 for 1 site, Pro Plus $74.99 for 5, Pro Max $138.99 for 100), with a 14-day money-back guarantee. See pricing when WordPress AI should run on the model account you already trust instead of a second credit meter.
Paste your key. Run one staging generation. When the provider dashboard shows the usage and the post still needs your publish click, you have AI wired the adult way.