Visanetperu API Merchant

Name: API Merchant API
Brand: API Merchant
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource ControlapiKey4 Endpoints

Install Jentic One Beta

Connect the API Merchant to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API Merchant, 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 | sh

Step 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 instance

Jentic 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 Merchant API.

RetrieveTotal

RetrieveMerchant

Query merchant

update

GET STARTED

Start building with API Merchant API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use API Merchant API for, with concrete tasks.

★ Developer Tools Operations

Use the API Merchant to perform developer tools operations programmatically. The API provides 4 endpoints covering core functionality including retrievetotal, retrievemerchant, query merchant.

Call GET /getTotal/{operation} to retrievetotal

Automated Merchant API Management

Automate merchant API operations by combining multiple API Merchant endpoints. Agents can retrievemerchant and then query merchant in a single workflow.

Call GET /list/{operation}/{initPage}/{finalPage} to retrievemerchant, then verify the result

AI Agent Integration via Jentic

AI agents discover and call API Merchant 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 'retrievetotal', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

4 endpoints — **api merchant** *version 1.

METHOD

PATH

DESCRIPTION

GET

/getTotal/{operation}

RetrieveTotal

GET

/list/{operation}/{initPage}/{finalPage}

RetrieveMerchant

POST

/querybyRUC

Query merchant

POST

/update

update

GET

/getTotal/{operation}

RetrieveTotal

GET

/list/{operation}/{initPage}/{finalPage}

RetrieveMerchant

POST

/querybyRUC

Query merchant

POST

/update

update

Why Jentic?

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 'get the total for an operation' or 'look up a merchant by RUC', and Jentic returns the matching API Merchant operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using API Merchant API through Jentic.

What authentication does the API Merchant use?

The API Merchant 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 retrievetotal with the API Merchant?

Yes. Use the GET /getTotal/{operation} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the API Merchant?

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 retrievetotal through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'retrievetotal'. Jentic returns the matching API Merchant operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the API Merchant have?

The API Merchant exposes 4 endpoints covering merchant API operations.

Can I limit what my agent is allowed to do with the API Merchant?

Yes. Because Jentic One is self-hosted, you set the rules that decide which API Merchant operations your agent may call, so you can allow read-only calls like GET /getTotal/{operation} for totals and GET /list/{operation}/{initPage}/{finalPage} for merchant listings while withholding the rest. Lookups such as POST /querybyRUC and writes like POST /update are only available if you explicitly add them. Your Niubiz access token is stored encrypted by your own instance and injected at execution time, never entering the agent's prompt or logs.