BYOK or managed AI credits for WordPress work?
If your agency already pays for OpenRouter, buying another pool of AI credits may feel unnecessary. If nobody wants to manage provider billing or keys, a managed allowance can be simpler. Neither choice tells you, on its own, what a useful WordPress task will cost.
Start by separating the tool that performs the work from the account that pays for model usage. BYOK changes the second part. It does not remove the need to review what the AI proposes or limit what it can change.
What BYOK means in IrmaWP
IrmaWP’s BYOK connection uses a team-scoped OpenRouter key. The workspace uses that provider account for AI requests, and those requests do not consume IrmaWP managed credits. BYOK is available across plans. Your provider account still pays for its own usage.
A failed BYOK request does not silently switch to IrmaWP’s managed balance. That boundary matters when a provider account reaches its limit or a key stops working: the failure stays visible instead of creating a different bill.
OpenRouter’s API quickstart explains how its API key authenticates requests. Treat the key as a credential, not a piece of configuration to paste into screenshots, chat transcripts or client reports. Use the authorized workspace settings to connect it.
Measure a task, not a single reply
An investigation may involve several model calls: reading context, choosing a tool, inspecting the result and preparing a change. A short final answer does not mean the workflow used only one cheap request. Retrying an incomplete task can add more usage.
Choose a small sample of work your agency actually does. For example, inspect a plugin conflict without applying changes, draft a page section and review a proposed code adjustment. Run each with clear boundaries and record whether the result was useful enough to keep.
Compare the whole task’s provider usage and the human review time. The cheapest reply is not always the cheapest completed job. Equally, a more expensive model should earn its place through a better result on the tasks you care about.
Keep the two budgets visible
- Managed credits: check the current conversion, allowance reset and pack terms in the product.
- BYOK: review spending in the provider account that owns the key.
- Human review: track the effort required to verify and apply the output.
IrmaWP’s managed conversion can change globally for future usage, so do not write a client contract that assumes a permanent exchange rate. Included monthly credits reset; purchased credits have different terms. The pricing page keeps the current numbers and rules together.
Choose the ownership model your team can support
A shared agency key can simplify administration but also puts several projects on one provider budget. Decide who monitors it and who can change workspace settings. If a client expects a separate account or data-handling arrangement, settle that before sending their site context to a model.
Review what information the task needs. Do not include customer exports, credentials or unrelated logs merely because a model accepts a large prompt. Provider terms and routing choices deserve attention independently of whether you use BYOK or managed credits.
Try both billing approaches on a low-risk site if you need a comparison. Keep the task and acceptance check the same, then choose based on useful output, cost visibility and account ownership. The IrmaWP workflow overview explains the surrounding review process. Whichever account pays, someone on your team still needs to inspect the proposed change and decide whether it is ready to test.
Have a correction or a workflow we should cover? Tell the IrmaWP team.