$HEADLESS SYSTEMS
03 / Scorecard / Content Management

Statamic

C
Headless Index
50/100
JAIRF
N/A
Verified
AUG 20, 2026
Methodology v1 · JAIRF v1.0.0

Powered by JAIRF v1.0.0 by Jentic · open methodology at /the-headless-index/methodology

Statamic earns Band C in the Content Management category of The Headless Index, with a thesis-fit score of 50/100. Its strongest dimension is headless operation (16/20); its weakest scored dimension is webhooks and events (6/20). No public OpenAPI specification was found when Statamic was scored, which limits how far an agent can go without human integration work.

Editorial verdict
Statamic is partially headless and partly UI-led. The Headless Index thesis-fit score of 50/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 Statamic lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Statamic ships a Laravel application first and an API second. Both the Content REST API and the GraphQL API are explicitly read-only (statamic.dev/rest-api), so any agent that needs to create an entry drops into PHP. No first-party JS, Python or Go client exists under the org; the CLI installer (github.com/statamic/cli) is the only published package. 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: Content lives as YAML and Markdown on disk, which makes the whole site config-as-code by default; php please covers collections, blueprints, users and static site generation, and Spock (github.com/statamic/spock) commits content changes to git automatically. Self-hosting is the only mode. Publishing an entry over HTTP, though, still requires the control panel or custom Laravel routes.[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: No MCP server exists under the vendor org (github.com/statamic). The working options are community Composer packages, cboxdk/statamic-mcp for Statamic 6 and chrisvasey/statamic-boost layered on Laravel Boost, both outside vendor control. Statamic does publish a docs index (statamic.dev/llms.txt), which helps a coding agent read prose but hands it nothing callable against a running site.[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Statamic core ships no outbound webhooks at all. What exists is in-process Laravel events (EntrySaved, EntryDeleted, TermSaved) that fire only inside your own PHP application, plus community addons that translate them into git pushes or HTTP calls. No delivery log, no signing scheme, no retry policy, because there is no delivery layer. Net assessment: integrators can build agent flows against Statamic, 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 intent10/20
scored

Statamic ships a Laravel application first and an API second. Both the Content REST API and the GraphQL API are explicitly read-only (statamic.dev/rest-api), so any agent that needs to create an entry drops into PHP. No first-party JS, Python or Go client exists under the org; the CLI installer (github.com/statamic/cli) is the only published package.

signals (4)
  • +AI review appliedReviewer: Editorial review on 2026-08-19
  • OpenAPI specNot found across 0 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 operation16/20
scored

Content lives as YAML and Markdown on disk, which makes the whole site config-as-code by default; php please covers collections, blueprints, users and static site generation, and Spock (github.com/statamic/spock) commits content changes to git automatically. Self-hosting is the only mode. Publishing an entry over HTTP, though, still requires the control panel or custom Laravel routes.

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 posture8/20
scored

No MCP server exists under the vendor org (github.com/statamic). The working options are community Composer packages, cboxdk/statamic-mcp for Statamic 6 and chrisvasey/statamic-boost layered on Laravel Boost, both outside vendor control. Statamic does publish a docs index (statamic.dev/llms.txt), which helps a coding agent read prose but hands it nothing callable against a running site.

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 OpenAPI document and no hosted GraphQL endpoint to introspect; the schema is whatever your own install exposes once you enable the API in config (config/statamic/graphql.php). Blueprints and fieldsets sit as readable YAML under resources/blueprints, so an agent with repo access can infer the content model, but a cold HTTP client cannot.

signals (3)
  • +AI review appliedReviewer: Editorial review on 2026-08-19
  • OpenAPINot discovered across 0 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

Statamic core ships no outbound webhooks at all. What exists is in-process Laravel events (EntrySaved, EntryDeleted, TermSaved) that fire only inside your own PHP application, plus community addons that translate them into git pushes or HTTP calls. No delivery log, no signing scheme, no retry policy, because there is no delivery layer.

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

Powered by JAIRF v1.0.0 by Jentic

Band rationale:C band: scores 40-75 range

04 / Embed

Show Statamic'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.

FAQ

Statamic and agent readiness

Is Statamic agent-ready?
Statamic 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 webhooks and events.
Does Statamic publish an OpenAPI spec?
No published OpenAPI specification was found when Statamic was scored. That caps its JAIRF dimensions and forces agents to rely on documentation or reverse engineering to operate it.
What is Statamic's Headless Index score?
Statamic scores 50/100 on the Headless Index thesis-fit rubric and sits in Band C in the Content Management category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.