Build VTEX IO service routes using @vtex/api clients via ctx.clients.
npx skills add https://github.com/exilonX/ap2 --skill vtex-io-service-apps-exilonx
Please help me install this Agent Skill. Skill: vtex-io-service-apps Source: https://github.com/exilonX/ap2/tree/main/.agents/skills/vtex-io-service-apps Command: npx skills add https://github.com/exilonX/ap2 --skill vtex-io-service-apps-exilonx
It solves the reliability and maintainability issues of VTEX IO backend development by standardizing how service apps define routes and how they call VTEX and external APIs.
Service class with typed context and configured routes, resolvers, and event handlers.@vtex/api clients (e.g., JanusClient, ExternalClient, MasterDataClient) instead of raw HTTP libraries to ensure auth injection, caching, retries, and metrics.IOClients registry and access them only through ctx.clients in middleware/resolvers to keep code testable and production-ready.Use vtex-io-service-apps to implement a VTEX IO backend route that fetches and returns data from a VTEX Commerce API using a properly registered JanusClient accessed through ctx.clients.
High-intent search queries and answers about installing and using this skill.
Build secure VTEX IO backend apps by using @vtex/api clients like JanusClient accessed via ctx.clients, which ensures automatic auth injection, caching, retries, and metrics while avoiding raw HTTP libraries for production-ready reliability.
Call external APIs from VTEX IO GraphQL resolvers by registering an ExternalClient in the IOClients registry and accessing it through ctx.clients, ensuring proper authentication and standardized retry behavior without direct client instantiation.
Avoid direct client instantiation in VTEX IO because bypassing the IOClients registry and ctx.clients prevents the VTEX runtime from injecting authentication, managing lifecycle caching, applying retries, and tracking metrics for your service app.
Yes, VTEX IO supports custom middleware chains for REST route orchestration by wiring middleware, handlers, and API clients through the Service entry point class with typed context and configured retry or timeout settings.
Using raw HTTP libraries in VTEX runtime is discouraged because it bypasses the deterministic API access provided by @vtex/api clients, missing built-in auth injection, caching, and metrics required for reliable backend service communication.
vtexDefine runtime composition for VTEX IO backend services with service.json configuration.
vtexdocsStandardize VTEX IO backend services with IOClients and service wiring.
vtexAutomate VTEX IO backend service setup with typed IOClients and REST routes.
exilonXStandardize VTEX IO backend service calls through registered @vtex clients.