Is PrestaShop agent-ready?

PrestaShop scores Band C on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is API-first design intent; its weakest is MCP and agent posture.

Does PrestaShop publish an OpenAPI spec?

No published OpenAPI specification was found when PrestaShop was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.

What is PrestaShop's Headless Index score?

PrestaShop scores 40/100 on the Headless Index thesis-fit rubric and sits in Band C in the Commerce category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.

03 / Scorecard / Commerce

PrestaShop

Headless Index

40/100

JAIRF

N/A

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

PrestaShop earns Band C in the Commerce category of The Headless Index, with a thesis-fit score of 40/100. Its strongest dimension is API-first design intent (10/20); its weakest scored dimension is MCP and agent posture (4/20). No public OpenAPI specification was found when PrestaShop was scored, which limits how far an agent can go without human integration work.

Editorial verdict

PrestaShop is partially headless and partly UI-led. The Headless Index thesis-fit score of 40/100 puts it mid-table on the index, and JAIRF is recorded as N/A for this vendor because no public OpenAPI specification was reachable for the open-source scorer. In practice, vendors at this tier are partly machine-consumable: the core flows are reachable through code but several adjacent surfaces still expect a human at a dashboard, and the rest of this verdict explains where PrestaShop lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. PrestaShop bolted its API onto a back office, not the other way round. The legacy Webservice is CRUD over ObjectModel and returns XML unless you ask for JSON; PrestaShop 9 answers with an Admin API on API Platform 3 with OAuth2 and CQRS endpoints. An agent can drive parts of this product, but not all of it: integrators should plan for human-in-the-loop checkpoints where the headless surface stops short. On headless operability: Products, orders, customers and stock move through the Webservice, so catalogue automation works. Everything that makes a shop a shop stays in the back office: module installation, theme configuration, carrier rules, payment setup. The Symfony console (bin/console prestashop:...) covers install and cache, not merchandising. Self-hosting is the only deployment model, which at least means no vendor gate.^[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: Nothing exists. The PrestaShop GitHub organisation carries the core, the module repos and translation tooling, and no MCP server (github.com/PrestaShop). No registry entry, no agent documentation, no llms.txt on devdocs. For a platform running on hundreds of thousands of self-hosted shops, that absence hands the whole agent surface to third-party module authors rather than the project.^[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. PrestaShop has no outbound event system. Its hooks are in-process PHP callbacks executed inside the shop (hookActionValidateOrder, hookActionProductUpdate), so consuming them means writing and installing a module that posts somewhere itself. No signed delivery, no retry policy, no replay, no documented event catalogue. Every integration in the ecosystem reinvents this layer, which is why they all differ. Net assessment: integrators can build agent flows against PrestaShop, but the rough edge to plan around is MCP posture^[3]. Expect to wrap missing pieces in bespoke glue or accept human-in-the-loop checkpoints. Workable but requires scaffolding.

Verdict by Headless Index pipeline (auto)

// AI-drafted from the evidence layer. Editorial review pending.

Scores

Scorecard detail

Headless Index · 5 sub-criteria

API-first design intent10/20

scored

PrestaShop bolted its API onto a back office, not the other way round. The legacy Webservice is CRUD over ObjectModel and returns XML unless you ask for JSON; PrestaShop 9 answers with an Admin API on API Platform 3 with OAuth2 and CQRS endpoints. Client tooling is one aging PHP helper (PrestaShop/PrestaShop-webservice-lib), no maintained SDKs elsewhere.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPI specNot found across 34 probe paths
−GraphQL endpointNot discovered (5 probes; project-scoped endpoints require a real project ID)
−SDKs maintainedNone detected in vendor org

cite (1)

github.sdks@2026-08-19

Headless operation10/20

scored

Products, orders, customers and stock move through the Webservice, so catalogue automation works. Everything that makes a shop a shop stays in the back office: module installation, theme configuration, carrier rules, payment setup. The Symfony console (bin/console prestashop:...) covers install and cache, not merchandising. Self-hosting is the only deployment model, which at least means no vendor gate.

signals (9)

+AI review appliedReviewer: Editorial review on 2026-08-19
−API operations exposedNo OpenAPI spec; operations count unknown
·Docs pages crawled0 pages (crawler: none)
·Auth schemes documentedAuth documentation page not reached by crawler
·Setup / quickstart docsNot reached by crawler
·Billing docsNot reached by crawler
·Teams / org docsNot reached by crawler
·CLI docsNot reached by crawler
·Schema / data model docsNot reached by crawler

cite (1)

ai_review_browser.topics_found@2026-08-19

MCP & agent posture4/20

scored

Nothing exists. The PrestaShop GitHub organisation carries the core, the module repos and translation tooling, and no MCP server (github.com/PrestaShop). No registry entry, no agent documentation, no llms.txt on devdocs. For a platform running on hundreds of thousands of self-hosted shops, that absence hands the whole agent surface to third-party module authors rather than the project.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
−Official MCP serverNone found in vendor's GitHub org or the official MCP registry
−Community MCP serversNone found
−Agent-friendly SDKsNo TypeScript/JavaScript SDK published (agents commonly run in TS/JS)

cite (1)

ai_review_browser.pages_fetched@2026-08-19

Schema observability10/20

scored

There is no hosted spec to fetch. On your own install the Webservice answers ?schema=synopsis and ?schema=blank per resource, which is genuinely useful introspection, and the PrestaShop 9 Admin API ships Swagger through API Platform. Both require a running shop and credentials first. An agent cannot build a client cold from anything at prestashop.com (no public OpenAPI document).

signals (3)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPINot discovered across 34 standard probe paths
−GraphQL introspectionNo GraphQL endpoint discovered (5 probes; some vendors use project-scoped endpoints that require a real project handle)

cite (1)

ai_review_browser.schema@2026-08-19

Webhooks & events6/20

scored

PrestaShop has no outbound event system. Its hooks are in-process PHP callbacks executed inside the shop (hookActionValidateOrder, hookActionProductUpdate), so consuming them means writing and installing a module that posts somewhere itself. No signed delivery, no retry policy, no replay, no documented event catalogue. Every integration in the ecosystem reinvents this layer, which is why they all differ.

signals (2)

+AI review appliedReviewer: Editorial review on 2026-08-19
·Webhook docs pageNot reached by crawler within budget (0 pages crawled). Cannot confirm whether vendor offers webhooks.

cite (1)

ai_review_browser.pages_fetched@2026-08-19

JAIRF · 6 dimensions

JAIRF · N/A

This vendor does not publish a public OpenAPI specification. JAIRF cannot be computed. The Headless Index score and editorial verdict carry the readiness assessment.

No public OpenAPI specification discovered during collection

Band rationale:C band: scores 40-75 range

04 / Embed

Show PrestaShop's score on your site.

Drop a live badge into your README, footer, or marketing page. It updates automatically when we re-score, and every embed is a dofollow link back here.

Get embed code

Peers in Commerce

SwellD

Headless Index 32/100

SprykerC

Headless Index 48/100

Elastic PathD

Headless Index 32/100

See full Commerce ranking →

FAQ

PrestaShop and agent readiness

Is PrestaShop agent-ready?: PrestaShop scores Band C on The Headless Index. Its JAIRF rating is not available because no machine-readable spec was scored. Its strongest area for agent use is API-first design intent; its weakest is MCP and agent posture.
Does PrestaShop publish an OpenAPI spec?: No published OpenAPI specification was found when PrestaShop was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.
What is PrestaShop's Headless Index score?: PrestaShop scores 40/100 on the Headless Index thesis-fit rubric and sits in Band C in the Commerce category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.