Is Spryker agent-ready?

Spryker 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 headless operation; its weakest is MCP and agent posture.

Does Spryker publish an OpenAPI spec?

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

What is Spryker's Headless Index score?

Spryker scores 48/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

Spryker

Headless Index

48/100

JAIRF

N/A

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

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

Editorial verdict

Spryker is partially headless and partly UI-led. The Headless Index thesis-fit score of 48/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 Spryker lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Spryker's Glue API is architecturally central rather than bolted on: JSON:API conventions, split into Storefront and Backend applications (spryker/glue-application, 2.5 million Packagist installs). But it is a PHP framework you compile and host, not a hosted endpoint, and Spryker publishes no client SDK in any language. Every integration starts by standing up a project. 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: Because the product ships as Composer modules, almost everything is already code: environment definition through the Docker SDK (github.com/spryker/docker-sdk), data import and cache rebuilds through console commands, deployment YAML per environment. The Back Office still owns merchandising and CMS editing. An agent can operate a Spryker install, but only by driving a shell on infrastructure it controls.^[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: Absent. A search of the organisation returns no MCP server (org:spryker mcp, zero results), no registry entry, and docs.spryker.com carries no agent integration guide. Given that a Spryker deployment is customer-hosted, an official server would be awkward to scope, but nothing stops the vendor shipping a local server over Glue. Nothing has shipped.^[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Spryker has an event system, not a webhook product. Publish and Sync moves domain events over RabbitMQ queues inside your own deployment (spryker/event, spryker/publisher), and outbound HTTP callbacks are something you build. There is no published event catalogue, no signing convention, no retry or replay contract an integrator can rely on across installs. Net assessment: integrators can build agent flows against Spryker, 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 intent12/20

scored

Spryker's Glue API is architecturally central rather than bolted on: JSON:API conventions, split into Storefront and Backend applications (spryker/glue-application, 2.5 million Packagist installs). But it is a PHP framework you compile and host, not a hosted endpoint, and Spryker publishes no client SDK in any language. Every integration starts by standing up a project.

signals (5)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPI specNot found across 34 probe paths
·GraphQL endpointDiscovered at https://spryker.com/graphql, introspection disabled or scoped
+SDKs maintained5 (php); top by stars: spryker/product-api (2 stars)
+SDK recency2 of 5 SDK repos pushed within 30 days (most recent SDK commit: 2026-08-17)

cite (1)

github.sdks@2026-08-19

Headless operation14/20

scored

Because the product ships as Composer modules, almost everything is already code: environment definition through the Docker SDK (github.com/spryker/docker-sdk), data import and cache rebuilds through console commands, deployment YAML per environment. The Back Office still owns merchandising and CMS editing. An agent can operate a Spryker install, but only by driving a shell on infrastructure it controls.

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

Absent. A search of the organisation returns no MCP server (org:spryker mcp, zero results), no registry entry, and docs.spryker.com carries no agent integration guide. Given that a Spryker deployment is customer-hosted, an official server would be awkward to scope, but nothing stops the vendor shipping a local server over Glue. Nothing has shipped.

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.mcp@2026-08-19

Schema observability10/20

scored

There is no vendor-hosted spec to fetch. Spryker instead ships a generator (spryker/documentation-generator-open-api) that emits an OpenAPI file from whichever modules your own project enables, which is defensible for a framework and useless for cold discovery. An agent cannot learn the API surface without first cloning, installing and running the build for that specific store.

signals (3)

+AI review appliedReviewer: Editorial review on 2026-08-19
−OpenAPINot discovered across 34 standard probe paths
·GraphQL introspectionGraphQL endpoint at https://spryker.com/graphql but introspection is disabled, scoped, or behind authentication

cite (1)

ai_review_browser.schema@2026-08-19

Webhooks & events8/20

scored

Spryker has an event system, not a webhook product. Publish and Sync moves domain events over RabbitMQ queues inside your own deployment (spryker/event, spryker/publisher), and outbound HTTP callbacks are something you build. There is no published event catalogue, no signing convention, no retry or replay contract an integrator can rely on across installs.

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 Spryker'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

ShopwareC

Headless Index 50/100

VendureC

Headless Index 50/100

Tiendanube / NuvemshopC

Headless Index 51/100

See full Commerce ranking →

FAQ

Spryker and agent readiness

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