Is Bagisto agent-ready?

Bagisto 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 webhooks and events.

Does Bagisto publish an OpenAPI spec?

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

What is Bagisto's Headless Index score?

Bagisto scores 52/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

Bagisto

Headless Index

52/100

JAIRF

N/A

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

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

Editorial verdict

Bagisto is partially headless and partly UI-led. The Headless Index thesis-fit score of 52/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 Bagisto lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. The API is a package you install, not the platform itself. Bagisto ships REST and GraphQL as separate Composer add-ons (bagisto/rest-api, bagisto/graphql-api) on top of a Laravel admin, and api-docs.bagisto.com documents both transports. There are no client SDKs in any language; every consumer writes raw HTTP against their own domain. 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: Self-hosting is the whole model, so nothing is gated behind a vendor console. Artisan commands cover installation and packaging (php artisan bagisto:install, bagisto:publish), and bagisto/bagisto-docker gives a reproducible box. Catalogue, orders and customers are reachable over REST and GraphQL, but tax rules, channels, locales and theme settings are still configured through the admin panel.^[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: Bagisto is one of very few open-source carts with an MCP server under its own org (github.com/bagisto/mcp), and it deserves credit for that. Read the tools though: search_api_docs, list_endpoints, get_doc and refresh_api_docs index 753 doc pages from api-docs.bagisto.com/llms-full.txt. It helps an agent write integration code; it does not operate a store, so the gap between documentation and control stays open.^[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. There is no first-party outbound event catalogue. Bagisto fires Laravel events inside the process (checkout.order.save.after, sales.order.update-status.after), which a PHP listener in your own package can catch, but nothing signs, queues, retries or replays an HTTP delivery. Every store that needs an ERP or fulfilment feed builds that transport itself, and none of them build it the same way. Net assessment: integrators can build agent flows against Bagisto, but the rough edge to plan around is webhooks and events^[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 intent12/20

scored

The API is a package you install, not the platform itself. Bagisto ships REST and GraphQL as separate Composer add-ons (bagisto/rest-api, bagisto/graphql-api) on top of a Laravel admin, and api-docs.bagisto.com documents both transports. There are no client SDKs in any language; every consumer writes raw HTTP against their own domain. Version pinning follows the Bagisto core release, not an independent API version.

signals (5)

+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 maintained3 (php); top by stars: bagisto/rest-api (28 stars)
+SDK recency1 of 3 SDK repos pushed within 30 days (most recent SDK commit: 2026-08-17)

cite (1)

github.sdks@2026-08-19

Headless operation12/20

scored

Self-hosting is the whole model, so nothing is gated behind a vendor console. Artisan commands cover installation and packaging (php artisan bagisto:install, bagisto:publish), and bagisto/bagisto-docker gives a reproducible box. Catalogue, orders and customers are reachable over REST and GraphQL, but tax rules, channels, locales and theme settings are still configured through the admin panel.

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)

github.sdks@2026-08-19

MCP & agent posture12/20

scored

Bagisto is one of very few open-source carts with an MCP server under its own org (github.com/bagisto/mcp), and it deserves credit for that. Read the tools though: search_api_docs, list_endpoints, get_doc and refresh_api_docs index 753 doc pages from api-docs.bagisto.com/llms-full.txt. It helps an agent write integration code; it does not operate a store, so the gap between documentation and control stays open.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
+Official MCP serverhttps://github.com/bagisto/mcp (0 stars, last commit 65 days ago)
−Community MCP serversNone found
−Agent-friendly SDKsNo TypeScript/JavaScript SDK published (agents commonly run in TS/JS)

cite (1)

ai_review_browser.mcp@2026-08-19

Schema observability10/20

scored

No OpenAPI document is published at any Bagisto host. What exists instead is a 4.6MB llms-full.txt covering the REST and GraphQL reference (api-docs.bagisto.com/llms-full.txt), which is machine-readable prose rather than a typed contract. GraphQL introspection works, but only against your own deployment. An agent can read fast; it still cannot generate a client from the document alone.

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)

github.sdks@2026-08-19

Webhooks & events6/20

scored

There is no first-party outbound event catalogue. Bagisto fires Laravel events inside the process (checkout.order.save.after, sales.order.update-status.after), which a PHP listener in your own package can catch, but nothing signs, queues, retries or replays an HTTP delivery. Every store that needs an ERP or fulfilment feed builds that transport itself, and none of them build it the same way.

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)

github.sdks@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 Bagisto'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

WooCommerceC

Headless Index 52/100

Tiendanube / NuvemshopC

Headless Index 51/100

EcwidC

Headless Index 51/100

See full Commerce ranking →

FAQ

Bagisto and agent readiness

Is Bagisto agent-ready?: Bagisto 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 webhooks and events.
Does Bagisto publish an OpenAPI spec?: No published OpenAPI specification was found when Bagisto was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.
What is Bagisto's Headless Index score?: Bagisto scores 52/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.