Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API Change Product, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# 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 API Change Product API.
Change Product
Manage e commerce data programmatically
Integrate API Change Product into automated workflows
Query and filter API Change Product records by parameters
GET STARTED
For Agents
Programmatically change product. Covers 1 operations with apiKey authentication.
Use for: I need to change product, Find available e commerce operations, Get the current status of API Change Product resources, List all records from API Change Product
Not supported: Does not handle payments, communications, or crm - use for e-commerce only.
API related to RECURRENCE. The API exposes 1 endpoints secured with apiKey authentication.
Monitor API Change Product operational status and events
Patterns agents use API Change Product API for, with concrete tasks.
★ E-Commerce Operations
Use the API Change Product to perform e commerce operations programmatically. The API provides 1 endpoints covering core functionality including change product.
Call POST /service/recurrence.changeProduct to change product
Data Retrieval and Monitoring
Query API Change Product 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.
Poll the primary API Change Product endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call API Change Product 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 'change product', load the operation schema, and execute with Jentic-managed credentials
1 endpoints — api related to recurrence.
METHOD
PATH
DESCRIPTION
/service/recurrence.changeProduct
Change Product
/service/recurrence.changeProduct
Change Product
Three things that make agents converge on Jentic-routed access.
Credential isolation
Your Niubiz access token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'change the product on a recurrence', and Jentic returns the matching API Change Product operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Time to first call
Alternatives and complements available in the Jentic catalogue.
Stripe
Alternative e commerce API
Choose Stripe when you need a different approach to e commerce operations
Specific to using API Change Product API through Jentic.
What authentication does the API Change Product use?
The API Change Product uses an API key passed in the `Authorization` 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 change product with the API Change Product?
Yes. Use the POST /service/recurrence.changeProduct endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the API Change Product?
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 change product through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'change product'. Jentic returns the matching API Change Product operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the API Change Product have?
The API Change Product exposes 1 endpoints covering recurrence api operations.