Agentabile First Look: A Free WordPress Plugin That Turns Your WooCommerce Catalog Into an AI Agent-Ready Feed
Some links in this guide are affiliate links. If you sign up through them, Day Zero Guides may earn a commission at no extra cost to you. This never affects which products we cover or what we say about them. See our affiliate disclosure for details.

What Agentabile Actually Does
Agentabile is a free WordPress plugin, listed on WordPress.org, that watches your WooCommerce catalog and exposes it as a structured JSON feed at a fixed REST endpoint: /wp-json/agentabile/v1/feed/acp. The pitch is straightforward — as AI shopping agents (think ChatGPT's shopping features, Perplexity's commerce integrations, and any bot built on the emerging Agentic Commerce Protocol spec) start crawling and querying stores programmatically, your site needs a machine-readable catalog that isn't just an HTML product grid. Agentabile builds that feed automatically on activation, with no settings page to configure and no mapping fields to fill in.
That "zero config" claim is the headline feature, and based on the plugin's description it appears to hold up for the ACP feed specifically: install it, activate it, and the JSON endpoint starts responding using your existing WooCommerce product data (titles, prices, availability, URLs) without you touching a settings screen.
About That Name: ACP, UCP, MCP
The plugin's title advertises readiness for three protocols — ACP (Agentic Commerce Protocol), UCP, and MCP (Model Context Protocol). Worth being precise here for anyone evaluating it today: the concretely documented, working feature is the ACP JSON feed endpoint. If you're installing this specifically because you need MCP tool-calling support or a UCP-compliant integration right now, verify current plugin version notes on WordPress.org before assuming full parity — protocol support for a fast-moving spec like this tends to roll out incrementally, and the ACP feed is the part with a working, testable URL today.
Setup, Realistically
- Requires WooCommerce active on the site (it reads from the WC product data layer).
- Install and activate like any WordPress.org plugin — search "Agentabile" in Plugins > Add New, or upload the zip.
- No configuration screen to visit. The endpoint becomes live immediately at
yoursite.com/wp-json/agentabile/v1/feed/acp. - Runs entirely in PHP on standard WordPress hosting — no external service, no API key, no cron job to schedule (feed generation appears to be handled on request rather than via a separate export job, based on the described architecture).
This matters for who should try it: if you're on shared hosting or a managed WordPress host with no shell access and no appetite for a build pipeline, this is about as low-friction as catalog-to-feed tooling gets.
Concrete Use Cases
- A WooCommerce store wanting to appear in AI shopping assistants without hiring a developer to hand-roll a feed — activate the plugin, hand the endpoint URL to whatever agent/platform requests it.
- Agencies managing multiple small WooCommerce clients who need a fast, repeatable way to make each site agent-readable without customizing an integration per client.
- Developers prototyping against ACP who need a real WooCommerce-backed feed to test an agent or shopping bot integration against, rather than mocking JSON by hand.
- Stores that already tried a Google Shopping feed plugin and assumed it covers AI agent discovery too — it doesn't; Google Merchant Center feeds and ACP feeds serve different consumers and schemas, so this fills a gap those plugins don't address.
Where It Doesn't Fit
If you need custom field mapping, filtered product subsets (e.g., only in-stock items over $50), or multi-currency feed variants, there's currently no settings UI described for that — you're getting the full catalog, as-is. Stores with complex catalog logic (bundles, variable products with dozens of variations, subscription products) should test the actual feed output before relying on it for anything customer-facing.
How It Compares
| Agentabile | WooCommerce Feed Plugins (e.g. CTX Feed, WooCommerce Google Product Feed) | Zapier / Make | Custom REST API | |
|---|---|---|---|---|
| Price | Free (WordPress.org, open source) | Free tier limited; paid tiers typically $49–$99/year | Zapier: $19.99–$69+/month depending on task volume; Make: $9–$29+/month | Developer time: roughly $2,000–$10,000+ depending on scope, plus ongoing hosting/maintenance |
| Setup time | Minutes — activate, done | 30–60 minutes to map fields and choose feed format (Google, Meta, etc.) | Hours to build and test a multi-step Zap/scenario | Days to weeks for a developer to build and test |
| AI agent (ACP) readiness | Built specifically for this; feed shape targets agentic commerce consumption | Not designed for AI agents — built for shopping ad platforms (Google, Meta, Bing) | Possible but requires manually building the ACP-shaped payload yourself | Fully possible, but you own the entire schema and spec compliance |
| Maintenance | None described — feed reflects live catalog automatically | Occasional field remapping when WooCommerce updates | Scenario can break silently when a connected app changes its API | Ongoing — your team owns bug fixes and spec updates |
| Best for | Stores wanting a zero-effort, no-cost path to an AI-agent-readable catalog | Stores primarily running Google Shopping / Meta ads and needing those specific feed formats | Teams needing custom, multi-app data flows beyond just a product feed (e.g., syncing orders to a CRM) | Teams with unique catalog logic or compliance needs a plugin can't accommodate |
Should You Install It Today
Given it's free, requires no configuration, and doesn't touch your storefront's frontend or checkout flow, the downside risk of trying it is close to zero — worst case, you deactivate it and lose nothing. The realistic use case right now is defensive and exploratory: get an ACP feed live so you're not caught flat-footed as agent-based shopping traffic grows, and so you have a working endpoint to test against if a marketplace or AI platform asks for one. It's not yet a replacement for your Google Shopping feed plugin or a Zapier workflow that syncs orders into your CRM — it's a narrow, well-scoped tool for one emerging job. Check the WordPress.org plugin page for the current version and changelog before installing, since protocol support in this space is likely to expand quickly.