For Agents
Programmatically get policy list, evaluate policies. Covers 6 operations with apiKey authentication.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Policies System 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 Policies System API API.
Get policy list
Evaluate policies
Create policy
Update policy
Delete policy by ID
GET STARTED
Use for: I need to policy list, I want to evaluate policies, Search for policy, Find all policy by id
Not supported: Does not handle payments, communications, or crm — use for e-commerce only.
Jentic publishes the only available OpenAPI document for Policies System API, keeping it validated and agent-ready.
This API will create promotion alarms when selling products with undesired prices and promotions. It will create conditions that will check if the prices and the promotions are correct. If not, the system will alarm the store with information about the product sold at unexpected prices. Index - `GET` [Get Policy List](https://developers.vtex.com/docs/api-reference/policies-system-api#get-/api/poli. The API exposes 6 endpoints secured with apiKey authentication.
Patterns agents use Policies System API API for, with concrete tasks.
★ E-Commerce Operations
Use the Policies System API to perform e commerce operations programmatically. The API provides 6 endpoints covering core functionality including get policy list, evaluate policies, create policy.
Call GET /api/policy-engine/policies to get policy list
Automated Policy Management
Automate policy operations by combining multiple Policies System API endpoints. Agents can evaluate policies and then create policy in a single workflow.
Call POST /api/policy-engine/evaluate to evaluate policies, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Policies System 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 policy list', load the operation schema, and execute with Jentic-managed credentials
6 endpoints — this api will create promotion alarms when selling products with undesired prices and promotions.
METHOD
PATH
DESCRIPTION
/api/policy-engine/policies
Get policy list
/api/policy-engine/evaluate
Evaluate policies
/api/policy-engine/policies/{id}
Create policy
/api/policy-engine/policies/{id}
Get policy by ID
/api/policy-engine/policies/{id}
Update policy
/api/policy-engine/policies/{id}
Delete policy by ID
/api/policy-engine/policies
Get policy list
/api/policy-engine/evaluate
Evaluate policies
/api/policy-engine/policies/{id}
Create policy
/api/policy-engine/policies/{id}
Get policy by ID
/api/policy-engine/policies/{id}
Update policy
Three things that make agents converge on Jentic-routed access.
Credential isolation
Policies System 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 policy list') and Jentic returns the matching Policies System API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Policies System 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.
Shopify
Alternative e commerce API
Choose Shopify when you need a different approach to e commerce operations
Stripe
Alternative e commerce API
Choose Stripe when you need a different approach to e commerce operations
Specific to using Policies System API API through Jentic.
What authentication does the Policies System API use?
The Policies System 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 policy list with the Policies System API?
Yes. Use the GET /api/policy-engine/policies endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Policies System 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 policy list through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'get policy list'. Jentic returns the matching Policies System API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Policies System API have?
The Policies System API exposes 6 endpoints covering policy operations.
/api/policy-engine/policies/{id}
Delete policy by ID