ax-check.com
by Gauge
W
WPML
wpml.org
ax-check.com
Checked 19 September 2026
C
55/100
Agents haven’t verified setup
WPML pricing is clear, but there's no quickstart guide for AI agents
Pricing shows openly: €39/€99/€199 tiers plus per-word AI translation rates. But there's no llms.txt index or Markdown version of the docs, so agents must parse the full HTML site.
4 fixes to start with
Concrete changes, backed by what we found.
https://wpml.org/llms.txt returns HTTP 404, so no documentation index exists.
Publish a text or Markdown version of the quickstart.
No site-published Markdown guide; /llms.txt returns 404 and homepage ignores Markdown negotiation.
Recorded coding sessions
Same task, 3 models, no wpml.org account. Recorded 19 September 2026 on Pi.
3 recorded · 4m 50s
4m 50s · recorded
Session findings
Select a finding to see it in context.
›Thinking…
The user is asking about WPML (WordPress Multilingual Plugin) — a commercial WordPress plugin. They want me to build a simple example using WPML, explain the pricing mechanism, and determine whether it's easy to manage. They've asked me to use the hosted product via SDK/API, and if there's no developer workflow I can execute, to plainly state that and stop.
Let me think about what WPML actually is. WPML is a WordPress plugin for creating multilingual websites. It's not a hosted service with an API/SDK. There's no public API or SDK that an agent can use. To install it, you need a WordPress site.
First, let me check the environment. What's in the current working directory? Let me look.
The instructions say: "If this product has no developer workflow I can execute, plainly state that and stop."
I should verify quickly. Let me check the sandbox — maybe there's something there.
Honestly, the answer is: WPML is a WordPress plugin distributed as a ZIP download via wpml.org, requires registration/login and a subscription key. There's no hosted API or SDK that can be called. To build a "simple example" I'd need a WordPress stack (local or remote), which contradicts the "don't spin up a local service stack" condition.
The pricing mechanism is something I can explain. Let me recall WPML's pricing: WPML offers three subscription plans (annual and lifetime):
- Multilingual Blog: ~$39/year (or $99 lifetime?)
- Multilingual CMS: ~$99/year ($149 lifetime?)
- Multilingual Agency: ~$199/year ($249 lifetime?)
Let me recall the actual numbers as of recently. WPML pricing (2024/2025):
- Blog: $39/year, $99 lifetime
- CMS: $99/year, $149 lifetime
- Agency: $249/year, $499 lifetime
Actually, the Agency lifetime has changed. Let me check — I think currently: Multilingual Blog $39/year / $99 lifetime; Multilingual CMS $99/year / $149 lifetime; Multilingual Agency $249/year / $499 lifetime. Hmm, I'm not 100% sure. Previously Agency was $159/year / $399 lifetime, then it went up to $199/year? Let me be cautious and present it as an approximate value with a note.
Actually, as of 2023–2025, WPML pricing has been:
- Multilingual Blog: $39/year ($99 lifetime)
- Multilingual CMS: $99/year ($149 lifetime)
- Multilingual Agency: $249/year ($499 lifetime)
I think Agency went from $159 → $199 → $249. Should I verify via a web fetch? I don't have web access tools. Only bash, read, edit, write. Can I curl? Let me try curl on wpml.org's pricing page. This is "using the hosted product" — hmm, fetching a pricing page is fine, and it's not a long-running command. Let me try.
There might be no network in the sandbox. I can try quickly with a short timeout.
Plan:
- Check the contents of the sandbox.
- Try curl on wpml.org/pricing with a short timeout.
- Determine: is there a developer workflow I can execute? WPML has no public REST API/SDK for provisioning. It's a plugin that runs inside WordPress. To build an example I'd need a running WordPress installation (local stack), which is forbidden. WPML also requires a subscription key tied to an account with payment.
Therefore the honest answer is: WPML has no hosted API/SDK I can execute — I cannot build a working example without a WordPress stack and a paid subscription key. State this plainly and stop. But I should explain the pricing mechanism and answer "is it easy to manage?"
Wait — maybe I should check whether there are any hints in the environment. The repo directory is /sandbox/repo. Let me look. There might be an existing project. Let me check.
Also "tell me whether this product is easy to manage" — i.e., whether it would be easy for me (the agent) to manage WPML. WPML is managed through the WordPress admin UI. There are some WP-CLI-ish things? Actually, WPML has limited WP-CLI support. WPML has a REST API? There are hooks for programmatic translation. But provisioning/managing subscriptions requires account login.
User's framing: "Stay lightweight: use the hosted product via its SDK or API." WPML is not a hosted product — it's a plugin that installs on your own WordPress. wpml.org provides downloads, not an API. So the correct action is: plainly state that WPML has no developer workflow I can execute (no public SDK/API, plugin requires a WordPress install and a paid subscription key), and stop — without building anything.
But wait — should I double-check whether there's some WPML API? WPML has "WPML REST API" but? I don't think there's a public one. There are integrations with translation services (ATE — Advanced Translation Editor) that call remote services, but those are internal. wpml.org has no documented public REST API for external developers to manage sites. There are PHP hooks (filters/actions) for developers working inside WordPress themes/plugins, but that requires a WordPress codebase, not a hosted API.
Therefore my answer:
- Briefly check the environment (ls).
- Try to reach wpml.org to confirm pricing (quick curl with timeout). If blocked/no network, state so.
- Explain the pricing mechanism (plans: Blog/CMS/Agency, annual vs lifetime, what each includes, renewal = access to updates/support, sites continue to work after expiration).
- Brief manageability assessment.
- State plainly: no hosted SDK/API; building a working example would require WordPress install (local stack, which is forbidden) + subscription key (payment), so I'll stop here.
Let me run the checks. Do bash calls in parallel: ls of repo, curl pricing page with short timeout.
Actually, guideline: multiple independent calls go in the same block. Let me do:
- ls -la /sandbox/repo
- curl -sL --max-time 10 https://wpml.org/purchase/ (or /pricing/)
Then respond.
Pricing details from memory (to be verified via curl): WPML subscriptions (per year, with a lifetime option):
- Multilingual Blog — $39/year, $99 lifetime: 1 production site… actually, Blog allows unlimited? No. Blog: 1 site? Hmm. Let me recall:
- Multilingual Blog: $39/year — unlimited? No. I think Blog is 1 production site? Actually I recall Blog allows unlimited sites? No…
- The tiers differ by features: Blog lacks WooCommerce multilingual, string translation for themes/plugins (partial), WPML Media is included? CMS adds string translation, translation management, WooCommerce Multilingual, Multilingual CMS. Agency adds unlimited sites + Multilingual Agency for client sites.
- Site limits: Blog = unlimited? I recall Blog was 1 site… hmm. Historically: Blog $29/year unlimited sites? No. Let me think: CMS is 3 sites? Hmm.
Current wpml.org pricing (as of 2024–2025):
- Multilingual Blog: $39/year or $99 lifetime — 1 production site? I really recall Blog was limited… actually no: does Blog allow unlimited sites? Let me verify facts: WPML's plans are distinguished by features, and site limits are: Blog — unlimited? CMS — 3 production sites? Agency — unlimited production sites + client sites. Hmm, I think CMS is unlimited too? No.
From memory of wpml.org/purchase:
- Multilingual Blog: $39/year, $99 lifetime. "For blogs and simple sites" — 1 production site? Hmm, I think Blog = unlimited sites was wrong…
Actually now I recall more specifically:
- Blog: unlimited? No…
Anyway let me fetch the page. If network fails, I'll present approximate numbers with a caveat.
Agency was I think $199/year and $499 lifetime? Or $249/$499? Recently (2024) I recall: Blog $39/$99, CMS $99/$149, Agency $249/$499. Earlier Agency was $159/$399. Hmm, I've seen $199 somewhere too… The Agency plan's "for agencies with client sites" price went up around 2023 to $199/year? And then $249? I'll verify with curl.
Let me also quickly check the network. Run both commands in parallel.
On manageability: WPML is fairly manageable via the WordPress admin, and there are PHP hooks, but from the agent's perspective: updates via WordPress plugin updates; subscription key management requires logging into wpml.org; no public REST API; WP-CLI support is limited (WPML doesn't officially fully support WP-CLI; some commands exist via add-ons?). So: manageable within a WordPress site (theme/plugin code, hooks, wpml-config.xml), but not remotely manageable via API.
Okay, let me run the commands.
Another consideration: "Help me build a simple example using WPML." If it's impossible to execute, per the instructions I should plainly state that and stop. I could propose a code snippet example that doesn't require installation (e.g., a wpml-config.xml, or a PHP snippet using icl_object_id / apply_filters('wpml_object_id')) — but the instructions say if there's no developer workflow I can execute, plainly state it and stop. Providing a static snippet file could be borderline; the instructions say "plainly state and stop." I think the spirit is: don't fabricate a build, don't spin up stacks. A small illustrative snippet is not "building a working example," but the instruction says stop. State plainly, explain pricing, give a manageability verdict, and then stop — maybe offer that I can write snippets if they provide access to a WordPress environment. Actually, offering follow-up options is fine, but I shouldn't build anything now.
Hmm, but is that too strict? "If this product has no developer workflow I can execute, plainly state that and stop." WPML: developer workflow = writing PHP code inside WordPress using WPML hooks (wpml_object_id, wpml_register_string, etc.). I could definitely execute it by writing a small plugin file in the repo. But without a WordPress site, it can't run or be tested. The user said "use the hosted product via SDK/API" — WPML isn't a hosted product with an SDK/API. Therefore the condition "no developer workflow I can execute" applies to the hosted/API sense. State that and stop. That's what they're asking for: honesty over fabrication.
Now let me run the environment check.
✓$ ls -la /sandbox/repo && cat /sandbox/repo/README* 2>/dev/null | head -40✓└{"content":[{"text":"total 16\ndrwxr-xr-x 3 root root 4096 Sep 18 08:00 .\ndrwxr-xr-x 7 root root 4096 Sep 19 01:06 ..\ndrwxr-xr-x 8 root root 4096 Sep 18 08:00…ctrl+o
{"content":[{"text":"total 16\ndrwxr-xr-x 3 root root 4096 Sep 18 08:00 .\ndrwxr-xr-x 7 root root 4096 Sep 19 01:06 ..\ndrwxr-xr-x 8 root root 4096 Sep 18 08:00 .git\n-rw-r--r-- 1 root root 408 Sep 18 08:00 .gitignore\n","type":"text"}]}✓$ curl -sL --max-time 12 -o /tmp/wpml_pricing.html -w "HTTP %{http_code}\n" https://wpml.org/purchase/ ; curl -sL --max-time 12 -o /dev/null -w "HTTP %{http_code}\n" https://wpml.org/documentation/✓└{"content":[{"text":"HTTP 200\nHTTP 200\n","type":"text"}]}
›Thinking…
The repository is empty (only .git and .gitignore). Network access is working properly, and I fetched the pricing page. Let me parse the pricing page to get the actual prices.
Network works and I pulled the official pricing page. Let me extract the actual plan details.
✓$ python3 - <<'EOF'✓└{"content":[{"text":"(no output)","type":"text"}]}ctrl+o
python3 - <<'EOF'
import re, html
raw = open('/tmp/wpml_pricing.html', encoding='utf-8', errors='ignore').read()
text = re.sub(r'<script.*?</script>|<style.*?</style>', ' ', raw, flags=re.S|re.I)
text = re.sub(r'<[^>]+>', '\n', text)
text = html.unescape(text)
lines = [l.strip() for l in text.split('\n') if l.strip()]
# find pricing-relevant lines
keys = ['Multilingual Blog','Multilingual CMS','Multilingual Agency','$','lifetime','per year','site','Renewal','production']
for i,l in enumerate(lines):
if any(k.lower() in l.lower() for k in ['$','lifetime','renewal']) and len(l) < 160:
print(i, '|', l)
EOF
›Thinking…
The pricing page might be rendered with JS. Let me check the contents of the fetched HTML — maybe it's a redirect to a purchase page with a different structure, or the prices are embedded in JSON. Let me try searching for the "$" character in the raw HTML.
✓$ grep -oE '"[^"]*\$[0-9]+[^"]*"' /tmp/wpml_pricing.html | head -20; echo ---; grep -oiE '(blog|cms|agency)[^<]{0,80}' /tmp/wpml_pricing.html | head -20; echo ---; wc -c /tmp/wpml_pricing.html; grep -oE…✓└{"content":[{"text":"---\nagency accounts. Buy WPML and start translating today.\">\nagency accounts. Buy WPML and start translating today.\">\nBlog\",\nblog\",…ctrl+o
grep -oE '"[^"]*\$[0-9]+[^"]*"' /tmp/wpml_pricing.html | head -20; echo ---; grep -oiE '(blog|cms|agency)[^<]{0,80}' /tmp/wpml_pricing.html | head -20; echo ---; wc -c /tmp/wpml_pricing.html; grep -oE '<title>[^<]*</title>' /tmp/wpml_pricing.html
{"content":[{"text":"---\nagency accounts. Buy WPML and start translating today.\">\nagency accounts. Buy WPML and start translating today.\">\nBlog\",\nblog\",\nCMS\",\ncms\",\nAgency\",\nagency\",\nblog/\" class=\"inline-block rounded-md px-3 py-2 no-underline hover:text-brand-700 ho\nBlog \nblog\" data-collapse=\"#mobile-sub-blog\" aria-controls=\"mobile-sub-blog\" aria-expanded\nBlog\nblog\" class=\"collapse-target pb-2\">\nblog/\" class=\"block py-1.5 text-sm no-underline text-fg-muted\">All Blog Posts\nBlog\nblogs\nblog\">€39 | Buy now\nCMS\ncms\">€99 | Buy now\nAgency\n---\n151214 /tmp/wpml_pricing.html\n<title>WPML Pricing - Find the Right Plan for Your Multilingual WordPress Site</title>\n","type":"text"}]}›Thinking…
The prices are denominated in euros: Blog €39, CMS €99, Agency is probably €249. Let me extract the plan block more completely, including the lifetime prices and number of sites. Search for "lifetime", "€", and the plan descriptions.
✓$ grep -oE '€[0-9]+[^<]{0,60}' /tmp/wpml_pricing.html | head -30; echo ---LIFETIME---; grep -oiE 'lifetime[^<]{0,80}' /tmp/wpml_pricing.html | head -10; echo ---SITES---; grep -oiE '[^<>]{0,60}(producti…✓└{"content":[{"text":"€39 a year\">\n€39 | Buy now\n€99 | Buy now\n€199 | Buy now\n€39 | Buy now\n€99 | Buy now\n€199 | Buy now\n---LIFETIME---\n---SITES---\n","…ctrl+o
grep -oE '€[0-9]+[^<]{0,60}' /tmp/wpml_pricing.html | head -30; echo ---LIFETIME---; grep -oiE 'lifetime[^<]{0,80}' /tmp/wpml_pricing.html | head -10; echo ---SITES---; grep -oiE '[^<>]{0,60}(production|client) site[^<>]{0,60}' /tmp/wpml_pricing.html | head -15
{"content":[{"text":"€39 a year\">\n€39 | Buy now\n€99 | Buy now\n€199 | Buy now\n€39 | Buy now\n€99 | Buy now\n€199 | Buy now\n---LIFETIME---\n---SITES---\n","type":"text"}]}›Thinking…
The page displays €39 (Blog), €99 (CMS), and €199 (Agency) on an annual basis. On this page (or within the fetched variant), I don't see a lifetime option in the HTML. Maybe the lifetime price is behind a toggle that's rendered by JS, or perhaps it's listed somewhere else. Let me check for "one-time" or "Lifetime" in another case, or check a section with plan features. Let me try extracting the plan descriptions.
✓$ python3 - <<'EOF'✓└{"content":[{"text":"Multilingual Blog\nThe basic option for multilingual WordPress blogs\n€39 | Buy now\nMost Popular\nMultilingual CMS\nThe complete solution …ctrl+o
python3 - <<'EOF'
import re, html
raw = open('/tmp/wpml_pricing.html', encoding='utf-8', errors='ignore').read()
text = re.sub(r'<script.*?</script>|<style.*?</style>', ' ', raw, flags=re.S|re.I)
text = re.sub(r'<[^>]+>', '\n', text)
text = html.unescape(text)
lines = [l.strip() for l in text.split('\n') if l.strip()]
start = next(i for i,l in enumerate(lines) if 'Multilingual Blog' in l)
for l in lines[start:start+120]:
print(l)
EOF
{"content":[{"text":"Multilingual Blog\nThe basic option for multilingual WordPress blogs\n€39 | Buy now\nMost Popular\nMultilingual CMS\nThe complete solution for multilingual WordPress\n€99 | Buy now\nMultilingual Agency\nThe complete solution for agencies, building many multilingual websites\n€199 | Buy now\nStandard translation controls\nTranslate content using the WordPress editor\nUnlimited\nUnlimited\nUnlimited\nAdvanced Translation Editor\nUse WPML’s side-by-side translation editor\nNot included\nIncluded\nIncluded\nAI Translation\nHuman quality at machine speed and cost\nNot included\n22,500 words of AI translation included\n45,000 words of AI translation included\nString Translation\nTranslate any text coming from any theme or plugin\nNot included\nIncluded\nIncluded\nTranslation Management\nWork with your team of translators or translation services\nNot included\nIncluded\nIncluded\nPage Builders support\nTranslate your designs from Elementor and other page builders\nNot included\nIncluded\nIncluded\nMenu translation\nTranslate any kind of menu you can build with WordPress\nNot included\nIncluded\nIncluded\nE-Commerce support\nTranslate WooCommerce sites and popular extensions\nNot included\nIncluded\nIncluded\nFull Site Editing support\nTranslate headers, footers, templates and more from Gutenberg\nNot included\nIncluded\nIncluded\nTranslation Services Integration\nUse WPML’s partner services to translate content professionally\nNot included\nIncluded\nIncluded\nWebsites\nDevelopment sites show a WPML banner on the front end\n1 production\n3 development\n3 production\n9 development\n∞\nUnlimited\nSupport & updates\nOne year\nOne year\nOne year\n€39 | Buy now\n€99 | Buy now\n€199 | Buy now\nWant to learn more first?\nWPML features »\n/\nwith chevron affordance -->\nFrequently Asked Questions\nIs WPML compatible with my theme?\nWPML is compatible with hundreds of WordPress themes, and has an ongoing collaboration with theme authors to ensure compatibility. To confirm your theme is compatible with WPML, see our\ncompatible themes directory\n.\nWhat happens if I don’t renew my WPML account?\nWPML will continue to work on your site and all translations will keep showing up. However, you won’t be able to update WPML to new versions. This puts your site at risk as WPML will eventually become outdated and may cause issues.\nWhich WordPress versions is WPML compatible with?\nWPML is compatible with WordPress versions 4.7 and above.\nWill WPML slow down my site?\nWPML should never slow down your site. If WPML causes any performance issues and we can’t fix them, we’ll refund you up to 12 months after your purchase.\nCan I use AI to translate my website with WPML?\nYes. WPML offers AI-powered translations, with our own\nPTC engine\ndelivering human quality at machine speed and cost. You can also use\nDeepL\n,\nGoogle Translate\n, or\nMicrosoft Translator\nif you prefer.\nLearn more about AI translations\nand calculate costs.\nCan I upgrade my plan after buying WPML?\nYes, you can always upgrade your WPML plan. When upgrading, you only need to pay the difference.\nCan I get a refund if I’m not happy with WPML?\nYes, you can\nget a full refund\nfor your WPML license within 30 days of purchase. Unused prepaid AI translation words are refundable too; once you've translated, refunds follow the\n60-day Translation Quality policy\nfor PTC translations.\nHow does WPML compare to other multilingual plugins?\nCheck out our\ncomparing WPML to free and paid alternatives\ntable to learn how WPML stands against other multilingual plugins.\nWhich professional translation services can I use with WPML?\nWPML offers complete integration with many of the industry’s\nleading translation services\nand\ntranslation management systems\n. This integration allows you to send your site’s content directly from the WordPress admin and receive back translations, free of technical issues. If your favorite service is not on that list, we can easily add them for you.\n","type":"text"}]}›Thinking…
Already fetched official latest pricing info from wpml.org (EUR):
- Multilingual Blog: €39/year — 1 production site + 3 development sites; basic translation management; no ATE, no string translation, no WooCommerce, no AI credit.
- Multilingual CMS: €99/year — 3 production + 9 development sites; ATE, string translation, translation management, page builder support, menu translation, WooCommerce, FSE, translation service integration, 22,500 AI words included.
- Multilingual Agency: €199/year — unlimited sites; 45,000 AI words included.
- Support and updates for 1 year. Even if not renewed, WPML keeps working and translations continue to be displayed, but no updates (risk). Upgrades only pay the difference. 30-day refund available.
The retrieved page has no lifetime plans listed — WPML used to sell lifetime licenses, but the current purchase page only shows annual pricing. Should mention that the current page shows annual plans (lifetime was offered in the past; the current purchase page only shows annual). Better not to overstate — just say that the current page lists annual subscriptions only.
Also to confirm: does WPML have an SDK/API for developers to operate against? The developer workflow for WPML = PHP hooks/filters within WordPress (wpml_object_id, wpml-config.xml, etc.), requires installation on a WordPress site. No public REST API/SDK, no hosted sandbox either. Downloading the plugin requires a paid subscription/account. Therefore, to build a working sample, one of the following is needed:
- A local/remote WordPress stack (forbidden by the user's constraints — "don't spin up a local service stack"), plus
- A paid WPML account + subscription key (payment, account login).
Therefore per instructions: candidly state that WPML has no hosted SDK/API I can operate against, and stop. Don't build.
What to provide:
- Pricing explanation (verified, with source).
- Manageability verdict: hard for me to manage remotely — plugin-based, managed via wp-admin UI and PHP hooks; no public API; provisioning requires account + payment; WP-CLI support is limited/unofficial. Within a WordPress codebase, it's fairly manageable via hooks and wpml-config.xml, but I can't operate against it from here.
- Candid statement + stop. Maybe attach a one-line offer: if you provide a WordPress environment + subscription key, I can write plugin/theme snippets (e.g., wpml_object_id usage examples, wpml-config.xml). This is a reasonable offer to attach, and it's not "building" right now.
Should I reconfirm the claim that no public API exists? I know WPML well enough: wpml.org's docs cover PHP hooks (WPML PHP API: filters like wpml_object_id, wpml_register_single_string; actions), wpml-config.xml for theme/plugin compatibility, REST endpoints?? Hmm. WPML added some REST endpoints for the editor in recent versions (internal use, not documented for third-party provisioning). There's no documented public API for managing translations externally, and no SDK in package managers (no official composer/npm package). Let me quickly check composer/npm for "wpml" — quick check: search composer? Composer search API can be curled quickly. Let me verify to strengthen the claim. packagist.org/search.json?q=wpml and npm registry search. Quick and fast.
Let me run these two quick curls to verify there's no official SDK package.
Pricing confirmed from wpml.org. Quick verification that there's no official SDK package I could use programmatically:
✓$ curl -s --max-time 10 "https://packagist.org/search.json?q=wpml" | python3 -c "import json,sys; d=json.load(sys.stdin); [print(r['name'],'-',r.get('description','')[:70]) for r in d.get('results',[])[…✓└{"content":[{"text":"lucguerraz/wpml-installer - A composer plugin to make installing wpml.org plugins with composer ea\nwpml/wp - Class and utilities to interf…ctrl+o
curl -s --max-time 10 "https://packagist.org/search.json?q=wpml" | python3 -c "import json,sys; d=json.load(sys.stdin); [print(r['name'],'-',r.get('description','')[:70]) for r in d.get('results',[])[:8]]"; echo ---NPM---; curl -s --max-time 10 "https://registry.npmjs.org/-/v1/search?text=wpml&size=8" | python3 -c "import json,sys; d=json.load(sys.stdin); [print(o['package']['name'],'-',(o['package'].get('description') or '')[:70]) for o in d.get('objects',[])]"
{"content":[{"text":"lucguerraz/wpml-installer - A composer plugin to make installing wpml.org plugins with composer ea\nwpml/wp - Class and utilities to interface with WordPress from WPML\nwpml/fp - \nwpml/core-api - Class and utilities to interface with WPML core functionality\nwpml/collect - Collect - Illuminate Collections as a separate package.\notgs/multilingual-tools - Set of tools related to WPML plugin bundle. Created with tendency to e\notgs/installer - Installs and updates WPML and Toolset dependencies automatically\notgs/icons - Toolset and WPML icons\n---NPM---\nwpml - Markup Language for Web Publications\n@lumikmz/kmz - DJI KMZ/WPML domain model + plan() algorithm + validate(), spec-aligne\ngridsome-source-wordpress-wpml - WordPress source for Gridsome with image processing support and wpml\n@wpml/language-selector - \n@styleflow.app/flowpress-routing - Editorial 404, portable redirects and telemetry for FlowPress.\n@konnectio/core - Konnectio Core Frontend Integration.\n@plaudit/webpack-extensions - A webpack configuration and plugin suite designed specifically for Wor\ngatsby-source-wordpress-menus - gatsby source plugin to fetch menus via wordpress rest api\n","type":"text"}]}›Thinking…
Confirmed: The composer packages under wpml/* (wpml/wp, wpml/core-api) are internal libraries used by WPML's own code inside WordPress — they are not an external SDK for managing a hosted service. npm results are irrelevant. There is no hosted WPML API/SDK.
Conclusion: WPML is a self-hosted WordPress plugin, not a hosted product. There's no public SDK/API to call, and the purchase/download requires a paid account and subscription key. Furthermore, running the sample requires a WordPress site (a local stack or a remote host) — this is excluded by the user's constraints. Per the instructions: state this clearly and stop.
What I'll provide next:
- Pricing mechanism (from the official page, with the euro amount verified).
- A concise manageability assessment.
- A clear description of "there's no executable developer workflow" + stopping, and adding a one-line suggestion for what would be needed.
Keep it concise.
I got what I need and hit the stop condition you defined. Here's the honest picture:
Pricing (verified today from wpml.org/purchase, annual plans, EUR)
| Plan | Price | Sites | Key features |
|---|---|---|---|
| Multilingual Blog | €39/yr | 1 production + 3 dev | Basic translation via the WordPress editor only |
| Multilingual CMS | €99/yr | 3 production + 9 dev | Advanced Translation Editor, String Translation, Translation Management, page builders, menus, WooCommerce, Full Site Editing, 22,500 AI-translated words included |
| Multilingual Agency | €199/yr | Unlimited | Same as CMS + 45,000 AI words included |
How it works: it's an annual subscription covering support + updates for one year. If you don't renew, WPML keeps working and translations keep showing, but you lose access to updates (they warn this becomes a compatibility/security risk over time). Upgrades between plans cost only the difference; 30-day full refund. Dev sites show a WPML banner. The current purchase page lists annual plans only (they've sold lifetime licenses historically, but none are shown now). AI translation beyond the included words is prepaid credit.
Will it be easy for me to manage?
No — not from here. WPML is not a hosted product. It's a plugin that lives inside your WordPress installation. Everything about it is managed through wp-admin and PHP hooks (wpml_object_id, wpml-config.xml, etc.). There is no public REST API, no CLI, no provisioning endpoint. The wpml/* Composer packages I found are internal libraries used by the plugin's own code, not an external SDK. Subscription/site registration is done by pasting a subscription key from a paid wpml.org account into wp-admin — an account + payment flow I can't act on.
Blocked — stopping as instructed
WPML has no developer workflow I can act on. Building a working example would require (a) a running WordPress site — a local service stack or remote host, which your constraints exclude — and (b) a paid subscription key to download and activate the plugin. There's no SDK or API to use "through the hosted product," because there is no hosted product.
If you later want this, the minimal unblock is: a WordPress URL + admin credentials + an active WPML subscription key. With that, I could quickly write the example code (a small plugin using wpml_object_id / string-translation hooks, plus a wpml-config.xml). Until then, per your instruction, I'm stopping.
AX Fundamentals
23 checks. Open an area for details.
This check is a quick preview. Test more tasks and models with Gauge Agents.
Test your product with Gauge Agents