canonical: https://jentic.com/apis/vtex.local/pricing-hub-deprecated

# Vtex Pricing Hub (DEPRECATED)

>⚠️ This API has been deprecated. If you need to associate prices with customers, we recommend using the [Audience API](https://developers.vtex.com/docs/api-reference/audience-api).\ n\n. In the B2B scenario, it is common for stores to have personalized prices per customer and complex pricing systems that require external integrations. Pricing Hub is a system developed for the B2B context that wor. The API exposes 2 endpoints secured with apiKey authentication.

## For AI agents

Programmatically retrieve prices, configure external price source. Covers 2 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for marketing only.

## Capabilities

- Retrieve prices
- Configure external price source
- Integrate Pricing Hub (DEPRECATED) into automated workflows
- Query and filter Pricing Hub (DEPRECATED) records by parameters
- Monitor Pricing Hub (DEPRECATED) operational status and events

## Use cases

### Marketing Operations

Use the Pricing Hub (DEPRECATED) to perform marketing operations programmatically. The API provides 2 endpoints covering core functionality including retrieve prices, configure external price source.

Example prompt: Call POST `/api/pricing-hub/prices` to retrieve prices

### Data Retrieval and Monitoring

Query Pricing Hub (DEPRECATED) resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Pricing Hub (DEPRECATED) endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Pricing Hub (DEPRECATED) 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.

Example prompt: Search Jentic for 'retrieve prices', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/pricing-hub/prices` | Retrieve prices |
| PUT | `/api/pricing-hub/prices/config` | Configure external price source |

## Key resources

- **Pricing Hub Prices** — Operations related to Pricing Hub Prices

## Why Jentic

- **Setup:** Wiring the VTEX Pricing Hub API by hand means pairing an App Key with an App Token in the X-VTEX-API-AppKey and X-VTEX-API-AppToken headers, and templating the prchub.{environment}.com.br host into each call. Through Jentic you install once, import the Pricing Hub API from the API Directory, store the App Key and App Token once, and your agent calls it.
- **Permission scoping:** The Pricing Hub API carries its price target in the request body rather than a resource id in the path, so limit the agent to the operations it needs, such as reading prices. You choose whether to include writes like updating the price configuration, and this surface is deprecated so keep the grant narrow.
- **Credential handling:** Your VTEX App Key and App Token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'retrieve prices' or 'update the price configuration', and Jentic returns the matching Pricing Hub API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mailchimp** — Alternative marketing API
- **Hubspot** — Alternative marketing API

## FAQ

### What authentication does the Pricing Hub (DEPRECATED) use?

The Pricing Hub (DEPRECATED) uses an API key passed in the `X-VTEX-API-AppKey` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I retrieve prices with the Pricing Hub (DEPRECATED)?

Yes. Use the POST `/api/pricing-hub/prices` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Pricing Hub (DEPRECATED)?

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 retrieve prices through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'retrieve prices'. Jentic returns the matching Pricing Hub (DEPRECATED) operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Pricing Hub (DEPRECATED) have?

The Pricing Hub (DEPRECATED) exposes 2 endpoints covering pricing hub prices operations.

### Can I limit what my agent is allowed to do with the VTEX Pricing Hub API?

Yes. Because you run Jentic One yourself, your own rules decide which of the two operations your agent may call and which credentials it may use. Since the price target rides in the request body rather than a path id, you scope by operation: grant read access to POST `/api/pricing-hub/prices` while withholding the PUT `/api/pricing-hub/prices/config` write that updates the external price source. Given this surface is deprecated, keeping the grant to price reads only is the safest configuration.