A synthetic developer who has already seen the payload and read API.

One domain, with its environments. A site slot is counted per domain, so example.com, www.example.com and any environment copy on a subdomain of it — staging., stage., dev., develop., test., testing., qa., uat., sandbox. or preview. — all share a single slot. Run any or all of them and it still costs one site. Separate domains, and other subdomains such as shop.example.com, demo.example.com or beta.example.com, each take a slot of their own. Local environments — localhost, *.local, *.test, and private IP addresses — are always free and never count against your site limit.

Yes, and they do not cost you an extra slot. Local environments — localhost, *.local, *.test, and private IP addresses — are detected automatically and never consume a license slot, so you can run unlimited local installs on any plan. A public staging or dev site shares the slot of the domain it belongs to whenever it sits on one of the recognised environment subdomains — staging., stage., dev., develop., test., testing., qa., uat., sandbox. or preview. — so example.com, staging.example.com and dev.example.com together use one site. It works the other way round too: a license used only on staging.example.com, with no production site activated yet, still counts as a single site. A staging copy kept on a separate domain, such as example-staging.com, is a different domain and does take its own slot.

Two things that run on our infrastructure rather than yours: hosted AI credits, so Build with AI works without you managing an API key, and External Cron, which drains the delivery queue reliably without depending on WP-Cron. Plus priority support. Everything else — Code Glue, dynamic URLs, unlimited conditions and condition groups, per-webhook retry and backoff settings, the queue, the logs, the REST API and MCP — is in the free plugin, on unlimited sites. Starter, Business and Agency differ only in the number of production sites allowed (each one including its staging and dev copies) and the size of the monthly AI credit pool.

The plugin keeps working exactly as-is — no features are locked or disabled. You lose access to updates and priority support until you renew. All your data stays intact.

Yes. Contact us and we'll upgrade your plan. We apply fair prorated pricing.

Downgrades are not supported during the billing period. You can switch to a lower plan at renewal.

Credits are charged by usage — how much the agent actually processes on each request — so you never overpay for a quick question or a small build, and heavier builds simply cost a bit more. A typical request runs about 11 credits, and a complete integration — the agent planning it, reading your site's hooks and REST routes, creating the webhook, mapping the fields, writing a Code Glue snippet, and test-firing it — usually lands around 25 credits total, even for an advanced multi-step build. So 5,000 credits a month is around 200 integrations, far more than most sites ever need. The plugin shows your remaining balance while you work.

Build with AI pauses and tells you, with a link to buy a top-up pack ($19 for 2,000 credits, $49 for 6,000). Top-up credits never expire and are only spent after each month's included pool. Your included credits reset automatically every month. Nothing else in the plugin is affected — webhooks, queue, retries, Code Glue and External Cron all keep running normally.

No. Included credits run on our servers with our provider keys, so there is nothing to sign up for and no per-token bill. If you would rather use your own key — Anthropic, OpenAI, Google, or a WordPress AI connector — that option stays available on every plan, including the free plugin. You can switch back and forth at any time in the plugin settings.

Yes. The free plugin comes with 55 AI credits, granted automatically the first time you send a prompt to Build with AI — no key, no signup, no card. That is about five requests, or two complete automations: enough to watch the agent plan an integration, map the fields, and test-fire it on your own site. When the trial credits are gone, Build with AI keeps working on your own Anthropic, OpenAI or Google key, or you can move to Pro for a monthly pool of hosted credits. Every Pro purchase is also covered by a 14-day money-back guarantee — a full refund for any reason, provided no more than 5% of your plan's monthly AI credits have been used, since credits are spent on our servers at real cost.

We accept all major credit and debit cards via Stripe. Payments are processed securely — we never store card details.

No — prices shown exclude VAT. Any applicable VAT or sales tax is calculated based on your billing country and shown before you confirm payment at checkout. If you are a VAT-registered business in the EU, you can enter your VAT number at checkout.