VTEX scores Band B on The Headless Index and rates AI-Ready on JAIRF (82.3/100). Its strongest area for agent use is schema observability; its weakest is MCP and agent posture.

Does VTEX publish an OpenAPI spec?

Yes. VTEX 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 VTEX's Headless Index score?

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

03 / Scorecard / Commerce

VTEX

Headless Index

65/100

JAIRF

82.3/100

AI-Ready

Verified

AUG 20, 2026

Methodology v1 · JAIRF v1.0.0

VTEX earns Band B in the Commerce category of The Headless Index, with a thesis-fit score of 65/100 and a JAIRF rating of 82.3/100 (AI-Ready). Its strongest dimension is schema observability (18/20); its weakest scored dimension is MCP and agent posture (4/20). VTEX publishes a machine-readable OpenAPI specification, which is what lets an agent discover and operate it without human glue code.

Editorial verdict

VTEX is solidly built for programmatic consumption. The Headless Index thesis-fit score of 65/100 lands it in the upper-middle of the index, and JAIRF v1.0.0 puts it at 82.3/100 (Level 3, AI-Ready). 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 VTEX lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. VTEX ships a wide REST estate across catalog, checkout and orders on the account host ({account}.vtexcommercestable.com.br/api), authenticated with app key and token headers (X-VTEX-API-AppKey). The weak link is client tooling: @vtex/api is a VTEX IO runtime client, not a general commerce SDK, and there is no maintained Python, PHP or Go equivalent. Agents write raw HTTP. 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: Storefront and app lifecycle genuinely live in code through the vtex CLI (npm package vtex, 4.4.3), with workspaces, promotions on the Promotions API and full order manipulation over REST. What does not move is merchandising and store settings, where the Admin remains the practical path, and there is no Terraform provider or declarative config format for account state.^[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: Nothing exists. A repository search across the vtex organisation returns no MCP server (org:vtex mcp, zero results), there is no registry listing, and the developer portal carries no agent-facing guide. For a platform with roughly ninety published API specs, this is a conspicuous omission: the schema work is done, the agent packaging around it has not started.^[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. Two mechanisms, neither modern. Order state changes push to a URL you register through the orders hook endpoint (POST /api/orders/hook/config), and Feed v3 offers a pull queue with explicit commit so nothing is lost. There is no HMAC body signature; you authenticate the callback with headers you chose yourself, and the catalogue stops at order status. Net assessment: VTEX can be operated by agents for the majority of practical workflows. The closest thing to a gap is MCP posture^[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 intent15/20

scored

VTEX ships a wide REST estate across catalog, checkout and orders on the account host ({account}.vtexcommercestable.com.br/api), authenticated with app key and token headers (X-VTEX-API-AppKey). The weak link is client tooling: @vtex/api is a VTEX IO runtime client, not a general commerce SDK, and there is no maintained Python, PHP or Go equivalent. Agents write raw HTTP.

signals (6)

+AI review appliedReviewer: Editorial review on 2026-08-19
+OpenAPI specPublished, 208 operations
−GraphQL endpointNot discovered (5 probes; project-scoped endpoints require a real project ID)
+SDKs maintained4 (javascript, typescript); top by stars: vtex/node-vtex-api (78 stars)
+SDK recency1 of 4 SDK repos pushed within 30 days (most recent SDK commit: 2026-08-05)
·npm weekly downloads8.3k across published packages; top: @vtex/api @ 8.2k/week

cite (1)

github.sdks@2026-08-19

Headless operation15/20

scored

Storefront and app lifecycle genuinely live in code through the vtex CLI (npm package vtex, 4.4.3), with workspaces, promotions on the Promotions API and full order manipulation over REST. What does not move is merchandising and store settings, where the Admin remains the practical path, and there is no Terraform provider or declarative config format for account state.

signals (9)

+AI review appliedReviewer: Editorial review on 2026-08-19
+API operations exposed208 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 posture4/20

scored

Nothing exists. A repository search across the vtex organisation returns no MCP server (org:vtex mcp, zero results), there is no registry listing, and the developer portal carries no agent-facing guide. For a platform with roughly ninety published API specs, this is a conspicuous omission: the schema work is done, the agent packaging around it has not started.

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 SDKs4 TS/JS SDKs available; top: @vtex/api (8.2k/week downloads)

cite (1)

ai_review_browser.mcp@2026-08-19

Schema observability18/20

scored

This is where VTEX outperforms most of commerce. Roughly ninety OpenAPI 3.0 documents sit in a public, Spectral-linted repository (github.com/vtex/openapi-schemas) and sync to the developer portal, covering Catalog, Checkout, Orders and Intelligent Search. Each file is fetchable raw, so an agent can generate a typed client for a specific domain without reading a single prose page.

signals (3)

+AI review appliedReviewer: Editorial review on 2026-08-19
+OpenAPIPublished at https://raw.githubusercontent.com/vtex/openapi-schemas/master/VTEX%20-%20Catalog%20API.json (OpenAPI 3.0.0, 208 operations)
−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 & events13/20

scored

Two mechanisms, neither modern. Order state changes push to a URL you register through the orders hook endpoint (POST /api/orders/hook/config), and Feed v3 offers a pull queue with explicit commit so nothing is lost. There is no HMAC body signature; you authenticate the callback with headers you chose yourself, and the catalogue stops at order status.

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

100/100

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

DXJDeveloper Experience & Tooling Compatibility

93.3/100

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

ARAXAI-Readiness & Agent Experience

69.4/100

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

AUAgent Usability

61.7/100

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

SECSecurity

100/100

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

AIDAI Discoverability

70.5/100

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

Band rationale:B band: JAIRF=82.3 HeadlessIndex=65

04 / Embed

Show VTEX'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 65 vs external median 0

No external scores available to calibrate against.

Peers in Commerce

WixB

Headless Index 68/100

MedusaB

Headless Index 70/100

MagentoB

Headless Index 60/100

See full Commerce ranking →

FAQ

VTEX and agent readiness

Is VTEX agent-ready?: VTEX scores Band B on The Headless Index and rates AI-Ready on JAIRF (82.3/100). Its strongest area for agent use is schema observability; its weakest is MCP and agent posture.
Does VTEX publish an OpenAPI spec?: Yes. VTEX 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 VTEX's Headless Index score?: VTEX scores 65/100 on the Headless Index thesis-fit rubric and sits in Band B in the Commerce category. The score weighs API-first design, headless operation, MCP and agent posture, schema observability, and webhooks.