Your own AI key beats credits — the honest math

Most SEO plugins sell AI features through credits: a monthly allowance, top-ups when you run out, and a hard stop in the middle of a rewrite. The economics behind the model are simple — the vendor buys tokens wholesale and sells them to you at a markup — and the markup is rarely printed anywhere. Bring-your-own-key (BYOK) is the opposite model: your WordPress site talks to your AI provider directly, and nobody stands in between.

The credit math, with a real number

Credit pricing sounds harmless until you divide. One documented example: Yoast's AI+ subscription costs $358.80 per year and includes five AI visibility questions per week. Five questions a week is 260 a year — about $1.38 per question. The underlying API call to the same class of model costs a few cents at list price. The difference is not infrastructure; it is margin, priced into every question you ask.

Credits also meter the wrong thing. You budget in "credits" whose token value the vendor sets and can change, instead of in the one currency that is transparent: your provider's public price list.

There is a subtler cost too: rationing changes behavior. When every question depletes an allowance, teams start skipping the second visibility run, the extra rewrite, the alt texts for older posts — precisely the routine work that compounds. A meter you do not fear gets used; a meter you fear gets avoided, and the site pays for the avoidance.

What BYOK changes

With your own API key, requests go from your server straight to your provider — OpenAI, Anthropic or Google. You pay list price, nothing on top. A month of heavy content work, a few hundred rewrites and meta descriptions, typically costs less than a single credit top-up. And when a better or cheaper model ships, you switch the same day, because the model choice is a dropdown in your settings, not a line on some vendor's roadmap. In AI search, where measurement runs and rewrites recur monthly, that difference compounds fast.

Control you keep

AI Rank Suite records every request in a usage ledger with its real cost and lets you set a monthly budget that hard-stops spending — reached mid-month, the plugin refuses new AI work instead of quietly overrunning. Connecting a key takes five minutes: create it at the provider, paste it, click test.

The privacy angle

Credits mean your content flows through the plugin vendor's servers, under the vendor's data agreement. With BYOK, your drafts and pages go only to the provider you chose, under the contract you accepted — nothing flows through airanksuite.com, and the key itself is stored encrypted in your own WordPress database. For agencies with client NDAs this is not a nice-to-have; it is the difference between allowed and not allowed. It also simplifies compliance paperwork: your data-processing inventory lists one AI provider, chosen by you, instead of a plugin vendor plus whatever subprocessors sit behind it.

The honest catch

BYOK means you need a key, and creating one is a five-minute detour many users have not made yet. That is why the plugin's split matters: everything keyless — llms.txt, schema, crawler control, the scores, the entire classic layer of the WordPress SEO plugin — works without any key at all, and the setup wizard treats the key as an upgrade, not an entry fee. The Pro price buys software, not tokens; the tokens stay a matter between you and your provider.

Which model for which job

BYOK also unbundles a decision credits hide: which model does which work. Cheap, fast models are perfectly adequate for meta descriptions, alt texts and short summaries; the stronger models earn their price on article drafts, rewrites of sensitive pages and the visibility simulation, where nuance matters. With your own key this is a per-task choice you can revise weekly. Inside a credit system, the vendor makes it for you — usually in the direction that protects the vendor's margin, not your output.

FAQ

Which providers work?

OpenAI, Anthropic and Google AI — you pick provider and model in a dropdown and can change both at any time. Cheaper models are fine for meta descriptions and alt texts; the stronger ones pay off for article drafts and the visibility simulation.

What does a typical month cost?

For a small business doing regular content work: usually cents to a few dollars in provider fees. The usage ledger shows every request with its real cost, so the answer for your site is a lookup, not an estimate.

Can spending run away?

No — set a monthly budget and the stop is hard. On top of that, most providers let you set a spending cap on the key itself, so you have two independent brakes.

Is a credit model ever the better deal?

If you use AI a handful of times a year and never want to see a provider dashboard, prepaid simplicity has a value. For everyone doing weekly content or visibility work, the arithmetic above answers the question.