Is Schematic agent-ready?

Schematic scores Band B on The Headless Index and rates AI-Aware on JAIRF (70.4/100). Its strongest area for agent use is API-first design intent; its weakest is headless operation.

Does Schematic publish an OpenAPI spec?

Yes. Schematic publishes an OpenAPI specification, scored under JAIRF v1.0.0. A published spec is what makes an API discoverable and callable by agents rather than only by developers reading docs.

What is Schematic's Headless Index score?

Schematic scores 84/100 on the Headless Index thesis-fit rubric and sits in Band B in the Feature Flags & Config category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.

03 / Scorecard / Feature Flags & Config

Schematic

Headless Index

84/100

JAIRF

70.4/100

AI-Aware

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

Schematic earns Band B in the Feature Flags & Config category of The Headless Index, with a thesis-fit score of 84/100 and a JAIRF rating of 70.4/100 (AI-Aware). Its strongest dimension is API-first design intent (18/20); its weakest scored dimension is headless operation (14/20). Schematic publishes a machine-readable OpenAPI specification, which is what lets an agent discover and operate it without human glue code.

Editorial verdict

Schematic is solidly built for programmatic consumption. The Headless Index thesis-fit score of 84/100 lands it in the upper-middle of the index, and JAIRF v1.0.0 puts it at 70.4/100 (Level 2, AI-Aware). In practice, vendors at this tier ship most of the primitives agents need, with one or two surfaces still leaning on documentation rather than discovery, and the rest of this verdict explains where Schematic lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Schematic treats the spec as the source: 46 paths on api.schematichq.com with explicit operationIds (list-api-keys, check-flag, upsert-company), and Fern generates matching SDKs across eight languages (@schematichq/schematic-js, schematichq on PyPI, schematic-go, schematic-java, schematic-csharp, schematic-ruby, schematic-php). Entitlements, plans, features and flags are first-class resources rather than dashboard concepts with an API bolted on afterwards. An agent can drive this product across most practical workflows, with a handful of edges where documentation reading still beats schema discovery. On headless operability: Catalogue and entitlement work is genuinely API-driven: plans, plan-entitlements, company-overrides, features and flag rules all have CRUD endpoints, and companies and users are upserted by keys rather than internal ids. Operations tooling is where it thins out. No CLI exists, no Terraform provider is published, and pricing components and the customer portal are assembled in the dashboard then rendered by the React embed (@schematichq/schematic-react).^[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: An official server sits in the vendor's own organisation and is registered where agents look (github.com/SchematicHQ/schematic-mcp, listed as io.github.SchematicHQ/schematic-mcp in the Model Context Protocol registry), last commit July 2026. That combination is still uncommon. What is missing is depth around it, no agent-facing documentation section and no published tool list, so discovery ends at the repository README.^[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. The catalogue is large and specific: company.created, company.plan_changed, flag.updated, flag_rules.updated, plan.entitlement.created, subscription.trial.ended, entitlement.limit.reached, entitlement.soft_limit.warning, credit.purchase.success, auto.topup.retry.exceeded and more, each mapped to a named SDK payload type. Requests carry three verification headers (X-Schematic-Webhook-Signature as hex HMAC-SHA256, plus -Version and -Timestamp). Replay semantics are undocumented, and the dashboard log is the only inspection path. Net assessment: Schematic can be operated by agents for the majority of practical workflows. The closest thing to a gap is headless operability^[3], which integrators should sanity-check against their own use case before committing. Strong fit for agent-driven use cases.

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 intent18/20

scored

Schematic treats the spec as the source: 46 paths on api.schematichq.com with explicit operationIds (list-api-keys, check-flag, upsert-company), and Fern generates matching SDKs across eight languages (@schematichq/schematic-js, schematichq on PyPI, schematic-go, schematic-java, schematic-csharp, schematic-ruby, schematic-php). Entitlements, plans, features and flags are first-class resources rather than dashboard concepts with an API bolted on afterwards.

signals (5)

+AI review appliedReviewer: Editorial review on 2026-08-19
+OpenAPI specPublished, 76 operations
·GraphQL endpointDiscovered at https://schematichq.com/graphql, introspection disabled or scoped
·SDKs maintained2 (java, python); top by stars: SchematicHQ/schematic-python (3 stars)
+SDK recency2 of 2 SDK repos pushed within 30 days (most recent SDK commit: 2026-08-19)

cite (1)

github.sdks@2026-08-19

Headless operation14/20

scored

Catalogue and entitlement work is genuinely API-driven: plans, plan-entitlements, company-overrides, features and flag rules all have CRUD endpoints, and companies and users are upserted by keys rather than internal ids. Operations tooling is where it thins out. No CLI exists, no Terraform provider is published, and pricing components and the customer portal are assembled in the dashboard then rendered by the React embed (@schematichq/schematic-react).

signals (9)

+AI review appliedReviewer: Editorial review on 2026-08-19
·API operations exposed76 operations in OpenAPI spec
·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 posture17/20

scored

An official server sits in the vendor's own organisation and is registered where agents look (github.com/SchematicHQ/schematic-mcp, listed as io.github.SchematicHQ/schematic-mcp in the Model Context Protocol registry), last commit July 2026. That combination is still uncommon. What is missing is depth around it, no agent-facing documentation section and no published tool list, so discovery ends at the repository README.

signals (4)

+AI review appliedReviewer: Editorial review on 2026-08-19
+Official MCP serverhttps://github.com/SchematicHQ/schematic-mcp (2 stars, last commit 19 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 observability18/20

scored

Point a generator at docs.schematichq.com/openapi.json and you get a working client: OpenAPI 3.1.0, 46 paths, 345 component schemas, a single declared server (api.schematichq.com), and operationIds on every operation. No prose reading required, no auth needed to fetch it. This is what the criterion is actually asking for, and few vendors in the flag category clear it.

signals (3)

+AI review appliedReviewer: Editorial review on 2026-08-19
+OpenAPIPublished at https://docs.schematichq.com/openapi.json (OpenAPI 3.1.0, 76 operations)
·GraphQL introspectionGraphQL endpoint at https://schematichq.com/graphql but introspection is disabled, scoped, or behind authentication

cite (1)

ai_review_browser.schema@2026-08-19

Webhooks & events17/20

scored

The catalogue is large and specific: company.created, company.plan_changed, flag.updated, flag_rules.updated, plan.entitlement.created, subscription.trial.ended, entitlement.limit.reached, entitlement.soft_limit.warning, credit.purchase.success, auto.topup.retry.exceeded and more, each mapped to a named SDK payload type. Requests carry three verification headers (X-Schematic-Webhook-Signature as hex HMAC-SHA256, plus -Version and -Timestamp). Replay semantics are undocumented, and the dashboard log is the only inspection path.

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

FCFoundational Compliance

85/100

Structural validity, standards conformance, and parsability of the OpenAPI specification.

DXJDeveloper Experience & Tooling Compatibility

51/100

Documentation clarity, example coverage, response completeness, and ingestion health.

ARAXAI-Readiness & Agent Experience

58.8/100

Semantic clarity, intent expression, datatype specificity, and error standardization.

AUAgent Usability

100/100

Operational composability, complexity comfort, navigation affordances, and safety patterns.

SECSecurity

50/100

Authentication strength, transport security, secret hygiene, and OWASP risk posture.

AIDAI Discoverability

65/100

Descriptive richness, intent phrasing, workflow context, and registry signals.

Band rationale:B band: JAIRF=70.4 HeadlessIndex=84

04 / Embed

Show Schematic'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

Calibration

How THI compares to external scorers

Source	Score	Measures	Last checked
Fern Agent Score	not found	Documentation completeness and SDK shape (~22 checks)	—
CLIRank Agent Friendliness	not found	CLI readiness, docs quality, and overall agent affordances	—
Cloudflare Is It Agent Ready?	blocked	Cloudflare's manual agent-readiness heuristic per vendor URL	—
Jentic Scorecard	—	JAIRF-based scorecard requiring a public OpenAPI specification	—

THI 84 vs external median 0

No external scores available to calibrate against.

Peers in Feature Flags & Config

LaunchDarklyB

Headless Index 84/100

GrowthBookB

Headless Index 74/100

FlagsmithB

Headless Index 68/100

See full Feature Flags & Config ranking →

FAQ

Schematic and agent readiness

Is Schematic agent-ready?: Schematic scores Band B on The Headless Index and rates AI-Aware on JAIRF (70.4/100). Its strongest area for agent use is API-first design intent; its weakest is headless operation.
Does Schematic publish an OpenAPI spec?: Yes. Schematic publishes an OpenAPI specification, scored under JAIRF v1.0.0. A published spec is what makes an API discoverable and callable by agents rather than only by developers reading docs.
What is Schematic's Headless Index score?: Schematic scores 84/100 on the Headless Index thesis-fit rubric and sits in Band B in the Feature Flags & Config category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.