$HEADLESS SYSTEMS
03 / Scorecard / Commerce

Tiendanube / Nuvemshop

C
Headless Index
51/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

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

Editorial verdict
Tiendanube / Nuvemshop is partially headless and partly UI-led. The Headless Index thesis-fit score of 51/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 Tiendanube / Nuvemshop lands inside that pattern. On the API surface, the question is whether the API is the product or a layer beneath the dashboard. Nuvemshop treats the API as the partner contract, and versions it like one: dated releases under https://api.tiendanube.com/2025-03/{store_id}, OAuth2 bearer tokens, a mandatory User-Agent identifying your app. The client libraries undercut that. 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: Resource coverage goes deep for a regional platform: metafields, draft orders, fulfillment orders with tracking events, locations, scripts, payment providers and shipping carriers are all API resources. What stays manual is the partner side, since apps are created and credentialed in the partner admin panel. No CLI and no config-as-code for store setup (nube-sdk builds UI apps, not infrastructure).[1] On the MCP and agent-integration axis, which is the fastest-moving criterion in the index: Absent. The TiendaNube organisation holds SDKs, sample apps and internal libraries, with no MCP server and no registry entry (github.com/TiendaNube). The developer docs have Nexo and Nimbus sections for app UI, nothing for agents, and no llms.txt. For one of the largest commerce platforms in Latin America this leaves a sizeable agent surface unclaimed by the vendor itself.[2] Event posture closes the loop: an agent that cannot react to state changes is reduced to polling. The best event story in this batch. Webhooks are created over the API rather than a settings screen, and each delivery is signed (x-linkedstore-hmac-sha256 computed over the raw body with the app secret). The list is broad: order/paid, order/fulfilled, product/created, fulfillment_order/tracking_event_created, app/uninstalled. Nuvemshop also states plainly that ordering is not guaranteed and duplicates happen, so consumers must be idempotent. Net assessment: integrators can build agent flows against Tiendanube / Nuvemshop, 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

Nuvemshop treats the API as the partner contract, and versions it like one: dated releases under https://api.tiendanube.com/2025-03/{store_id}, OAuth2 bearer tokens, a mandatory User-Agent identifying your app. The client libraries undercut that. tiendanube-php-sdk last shipped in 2023 and tiendanube-python-sdk in 2013, while nube-sdk (github.com/TiendaNube/nube-sdk) targets storefront app UI rather than API access, so most integrators write raw HTTP.

signals (6)
  • +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 maintained7 (php, python, typescript); top by stars: TiendaNube/nube-sdk (12 stars)
  • +SDK recency1 of 7 SDK repos pushed within 30 days (most recent SDK commit: 2026-08-19)
  • npm weekly downloadsNo published npm package detected for the JS/TS SDKs
cite (1)
  • github.sdks@2026-08-19
Headless operation13/20
scored

Resource coverage goes deep for a regional platform: metafields, draft orders, fulfillment orders with tracking events, locations, scripts, payment providers and shipping carriers are all API resources. What stays manual is the partner side, since apps are created and credentialed in the partner admin panel. No CLI and no config-as-code for store setup (nube-sdk builds UI apps, not infrastructure).

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. The TiendaNube organisation holds SDKs, sample apps and internal libraries, with no MCP server and no registry entry (github.com/TiendaNube). The developer docs have Nexo and Nimbus sections for app UI, nothing for agents, and no llms.txt. For one of the largest commerce platforms in Latin America this leaves a sizeable agent surface unclaimed by the vendor itself.

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 SDKs1 TS/JS SDKs available; top: nube-sdk
cite (1)
  • github.sdks@2026-08-19
Schema observability7/20
scored

The docs are readable Docusaurus pages with property tables per resource, and the versioning is disciplined, but no machine-readable contract is published. Guessed spec locations return 404 (tiendanube.github.io/api-documentation/openapi.json, api.tiendanube.com/openapi.json) and there is no GraphQL introspection to fall back on. An agent has to parse prose to learn that products carry variants and price tables.

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)
  • ai_review_browser.pages_fetched@2026-08-19
Webhooks & events15/20
scored

The best event story in this batch. Webhooks are created over the API rather than a settings screen, and each delivery is signed (x-linkedstore-hmac-sha256 computed over the raw body with the app secret). The list is broad: order/paid, order/fulfilled, product/created, fulfillment_order/tracking_event_created, app/uninstalled. Nuvemshop also states plainly that ordering is not guaranteed and duplicates happen, so consumers must be idempotent.

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 Tiendanube / Nuvemshop'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

Tiendanube / Nuvemshop and agent readiness

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