For Agents
Programmatically get sku bindings by sku id, get sku bindings information. Covers 12 operations with apiKey authentication.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SKU Bindings API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with SKU Bindings API API.
Get SKU Bindings by SKU ID
Bind a seller's SKU to another SKU
Change Notification with SKU ID
Query and filter SKU Bindings API records by parameters
GET STARTED
Use for: I need to sku bindings by sku id, I want to sku bindings information, Search for details of a seller's sku, Find all bind a seller's sku to another sku
Not supported: Does not handle payments, communications, or crm — use for developer tools only.
Jentic publishes the only available OpenAPI document for SKU Bindings API, keeping it validated and agent-ready.
vtex.local/SKU-Bindings-API version 1.0. The API exposes 12 endpoints secured with apiKey authentication.
Monitor SKU Bindings API operational status and events
Patterns agents use SKU Bindings API API for, with concrete tasks.
★ Developer Tools Operations
Use the SKU Bindings API to perform developer tools operations programmatically. The API provides 12 endpoints covering core functionality including get sku bindings by sku id, get sku bindings information, get details of a seller's sku.
Call GET /catalog/pvt/skusellers/{skuId} to get sku bindings by sku id
Automated SKU Bindings Management
Automate sku bindings operations by combining multiple SKU Bindings API endpoints. Agents can get sku bindings information and then get details of a seller's sku in a single workflow.
Call GET /sku-binding/pvt/skuseller/admin to get sku bindings information, then verify the result
AI Agent Integration via Jentic
AI agents discover and call SKU Bindings API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'get sku bindings by sku id', load the operation schema, and execute with Jentic-managed credentials
12 endpoints — vtex.
METHOD
PATH
DESCRIPTION
/catalog/pvt/skusellers/{skuId}
Get SKU Bindings by SKU ID
/sku-binding/pvt/skuseller/admin
Get SKU Bindings information
/sku-binding/pvt/skuseller/{sellerId}/{sellerSkuId}
Get details of a seller's SKU
/sku-binding/pvt/skuseller/{sellerId}/{sellerSkuId}
Bind a seller's SKU to another SKU
/sku-binding/pvt/skuseller/list/bysellerId/{sellerId}
Get all SKU Bindings by Seller ID
/sku-binding/pvt/skuseller/paged/sellerid/{sellerId}
Get paged SKU Bindings by Seller ID
/sku-binding/pvt/skuseller/changenotification/{skuId}
Change Notification with SKU ID
/sku-binding/pvt/skuseller/changenotification/{sellerId}/{sellerSkuId}
Change Notification with Seller ID and Seller SKU ID
/catalog/pvt/skusellers/{skuId}
Get SKU Bindings by SKU ID
/sku-binding/pvt/skuseller/admin
Get SKU Bindings information
/sku-binding/pvt/skuseller/{sellerId}/{sellerSkuId}
Get details of a seller's SKU
/sku-binding/pvt/skuseller/{sellerId}/{sellerSkuId}
Bind a seller's SKU to another SKU
/sku-binding/pvt/skuseller/list/bysellerId/{sellerId}
Get all SKU Bindings by Seller ID
Three things that make agents converge on Jentic-routed access.
Credential isolation
SKU Bindings API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'get sku bindings by sku id') and Jentic returns the matching SKU Bindings API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct SKU Bindings API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
Gitlab
Alternative developer tools API
Choose Gitlab when you need a different approach to developer tools operations
Specific to using SKU Bindings API API through Jentic.
What authentication does the SKU Bindings API use?
The SKU Bindings API uses an API key passed in the `X-VTEX-API-AppKey` header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I get sku bindings by sku id with the SKU Bindings API?
Yes. Use the GET /catalog/pvt/skusellers/{skuId} endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the SKU Bindings API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I get sku bindings by sku id through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'get sku bindings by sku id'. Jentic returns the matching SKU Bindings API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the SKU Bindings API have?
The SKU Bindings API exposes 12 endpoints covering sku bindings operations.
/sku-binding/pvt/skuseller/paged/sellerid/{sellerId}
Get paged SKU Bindings by Seller ID
/sku-binding/pvt/skuseller/changenotification/{skuId}
Change Notification with SKU ID
/sku-binding/pvt/skuseller/changenotification/{sellerId}/{sellerSkuId}
Change Notification with Seller ID and Seller SKU ID