WooCommerce is Not Agent-Ready to agents.
Discry independently scored how well an AI agent can discover and understand the WooCommerce API from what’s public — not whether it’s usable. Below: every signal we checked, what’s costing the score, and what to change.
SCORED UNDER RUBRIC 1.2 · A full re-launch under Discry Score 2.5 — a new behavioral instrument, not comparable to these scores — is in progress.
Discovery
45% of score · 31/100Comprehension
55% of score · 41/100What we found
- WooCommerce's API docs are hosted as a single 1.4MB GitHub Pages file with zero agent-discovery signals — no robots.txt, llms.txt, sitemap, or OpenAPI spec from the official org
- Despite poor official documentation posture, the community has built extensive MCP server coverage (5+ servers on Glama/PulseMCP) showing strong demand for agent integration
- WooCommerce repos (woocommerce-payments, woocommerce-google-analytics-integration) have adopted AGENTS.md for coding agents — a progressive signal for the broader ecosystem
- Error documentation lists only 4 status codes with no recovery guidance — an agent encountering errors has no self-correction path
- No rate limit documentation exists, meaning agents cannot proactively manage request throttling
What to change
Prioritized by impact on discoverability. You (or your docs platform) deploy these — Discry never touches your API.
- 01Create llms.txt and llms-full.txt at woocommerce.github.io/woocommerce-rest-api-docs/ covering core commerce operations (products, orders, customers)
- 02Publish an official OpenAPI 3.0 spec — the community version at wtx-labs exists but official support would dramatically improve agent tooling
- 03Add error recovery guidance for common scenarios (invalid product data, auth failures, missing required fields) beyond the current 4 generic error codes
- 04Add rate limit documentation so agents can implement proactive throttling and retry logic
- 05Break the monolithic 1.4MB single-page docs into a structured site with individual endpoint pages, or at minimum add a focused overview under 5000 tokens
Execution coverage · INFORMATIONAL, UNSCORED
Whether an agent can actually complete a call and recover from errors is the deeper Audit layer — documented here, but not part of the Discry Score.
HTTP Basic Auth with consumer key/secret over HTTPS. OAuth 1.0a for HTTP connections. JSON error responses with code, message, and data fields. Page-based pagination with per_page, page, and offset parameters plus X-WP-Total/X-WP-TotalPages headers and Link headers. No rate limits documented. No idempotency support mentioned.