Visanetperu API Change Product
Browse all Swaggerhub Visanetperu APIs73
AI ReadinessAI-Aware (A-)73/100
Community OpenAPI document · agent-readyE CommerceStorefrontapiKey1 EndpointsREST
Know of an official OpenAPI document? Contribute it →
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.
Install Jentic One Beta
Connect the API Change Product to your agent
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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.visanetperu%2Fapi-change-product" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.visanetperu%2Fapi-change-product" | 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.
Capabilities
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
Monitor API Change Product operational status and events
Use Cases
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
Key Endpoints
1 endpoints — api related to recurrence.
METHOD
PATH
DESCRIPTION
POST
/service/recurrence.changeProduct
Change Product
POST
/service/recurrence.changeProduct
Change Product
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
A
API Change Product
- AI-Aware (A-)73/100
93
Foundational Compliance87
Developer Experience & Jentic Compatibility55
AI-Readiness & Agent Experience94
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
93
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
87
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: ASignals: 4
79%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
75%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
93%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
55
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: CSignals: 4
71%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the API Change Product by hand means obtaining an access token from Niubiz api.security, passing it in the Authorization header, and coding the recurrence change-product call yourself. Through Jentic you install once, import the API Change Product from the API Directory, store the key once, and your agent calls it.
Permission scoping
The API Change Product carries its details in the request body, not as a resource in the URL path, so limit the agent to the operations it needs, such as changing a recurrence product with POST /service/recurrence.changeProduct. You choose the operations it may call, so this stays the single operation you grant rather than a broader set.
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.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Alternative e commerce API
Choose Stripe when you need a different approach to e commerce operations
FAQs
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.
Can I limit what my agent is allowed to do with the API Change Product?
Yes. Jentic One is self-hosted, so the operator sets the rules that decide which operations and credentials the agent may use. Because this API exposes a single operation, POST /service/recurrence.changeProduct, you can grant your agent only that call and nothing more. The change details travel in the request body rather than the URL path, so scoping the agent to this one operation keeps its access to exactly the recurrence product changes you allow.
GET STARTED