VTEX IO rootPath for multi-binding stores

When this skill applies

Use this skill when building VTEX IO apps that must work in stores with multi-binding configurations—typically cross-border stores where multiple bindings share a single domain with path prefixes (e.g. store.com/us/, store.com/br/, store.com/mx/).

• Your app generates URLs (links, redirects, API endpoints, canonical URLs) that must include the binding's path prefix
• Your app loads assets (images, scripts, stylesheets) that break when the store uses a sub-path binding
• Your backend routes need to construct URLs for sitemaps, canonical links, or cross-binding references
• You're debugging 404s or wrong links that only appear in multi-binding stores but work fine in single-binding

Do not use this skill for:

• Single-binding stores with a dedicated domain per locale (no path prefix needed)
• General IO backend patterns (use vtex-io-service-apps)
• CDN/edge caching configuration (use vtex-io-service-paths-and-cdn)

Decision rules