Install Jentic One Beta

Connect the Marketplace & Partner Management API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Marketplace & Partner Management 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.

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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fkapitalbank.az%2Fkapitalbank" | sh

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%2Fkapitalbank.az%2Fkapitalbank" | 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 Marketplace & Partner Management API.

List and create merchant partner records

Retrieve, update, or remove a specific partner

Approve, reject, or deactivate a marketplace

Update a marketplace's details

GET STARTED

Start building with Marketplace & Partner Management API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Marketplace & Partner Management API for, with concrete tasks.

★ Onboard merchant partners

A marketplace operator needs a consistent way to register the businesses that sell through it. The Kapital Bank API creates partner records and lists existing partners, so an onboarding workflow can add a merchant and retrieve its record without manual data entry. Partner records are addressed by identifier for later updates.

Create a partner record for a new merchant and confirm it appears in the partner list.

Manage the marketplace approval flow

New marketplaces usually pass through review before going live. The Kapital Bank API registers a marketplace and exposes approve, reject, and deactivate actions, letting an operations tool drive a marketplace through its lifecycle from a single integration. Each action targets a marketplace by identifier.

Maintain marketplace contacts

Operators need current contact details for each marketplace they oversee. The Kapital Bank API lists and adds contacts for a marketplace, so a back-office system can keep the responsible people up to date as partnerships change. Contacts are scoped to the marketplace they belong to.

Add a new primary contact to a marketplace and verify the contact list reflects the change.

Agent-assisted marketplace operations

An AI operations agent can handle routine partner and marketplace changes without a developer wiring each call. Through Jentic the agent matches an intent such as 'approve this marketplace' to the right Kapital Bank operation, runs it against the marketplace identifier, and reports the outcome. The bearer token stays in the user's Jentic One instance and never reaches the agent's prompt.

Given a marketplace pending review, approve it and update its contact list on behalf of the operations team.

Key Endpoints

14 endpoints — the kapital bank marketplace and partner management api administers merchant partners and their marketplaces.

METHOD

PATH

DESCRIPTION

GET

/partners

List merchant partner records.

POST

/partners

Create a new merchant partner record.

GET

/marketplaces

List registered marketplaces.

POST

/marketplaces

POST

/marketplaces/{id}/approve

Approve a marketplace.

POST

/marketplaces/{id}/deactivate

Deactivate a marketplace.

GET

/marketplaces/{id}/contacts

List the contacts attached to a marketplace.

GET

/partners

List merchant partner records.

POST

/partners

Create a new merchant partner record.

GET

/marketplaces

List registered marketplaces.

POST

/marketplaces

POST

/marketplaces/{id}/approve

Approve a marketplace.

POST

/marketplaces/{id}/deactivate

Deactivate a marketplace.

GET

/marketplaces/{id}/contacts

List the contacts attached to a marketplace.

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring this API yourself means managing a bearer token on every call, threading marketplace and partner identifiers through nested status paths, and sequencing approve, reject, and deactivate actions correctly. With Jentic you install once, import Kapital Bank from the API Directory, and store the token a single time.

Permission scoping

Jentic lets you grant your agent only the operations it needs, such as listing partners and marketplaces without deactivation or deletion, and enforces that on every call.

Credential isolation

Your Kapital Bank bearer token is stored once, encrypted, by your own Jentic One instance. It is injected when a call runs and never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents find this API through Jentic's intent search, matching a request like 'approve this marketplace' to the right operation without hardcoded endpoints.

FAQs

Specific to using Marketplace & Partner Management API through Jentic.

What can an AI agent do with the Kapital Bank Marketplace API through Jentic?

An agent can create and update partner records, register marketplaces, drive them through approval, rejection, and deactivation, and manage marketplace contacts. Through Jentic the agent matches an intent to the right operation and runs it with your bearer token injected at execution time.

How do I authenticate with the Kapital Bank Marketplace API?

Every request uses a bearer token in the Authorization header. You store the token once in your Jentic One instance, which supplies it on each call rather than exposing it to the agent.

Which resources does the API manage?

The API covers merchant partners, their marketplaces, the status actions that move a marketplace through its lifecycle, and the contacts attached to each marketplace. It does not process payments or transactions itself.

Does the API document rate limits?

The OpenAPI specification does not state rate limits; request allowances depend on your agreement with Kapital Bank. Confirm the limits for your integration with Kapital Bank before running bulk partner or marketplace changes.

Can I restrict what my agent is allowed to do with the Kapital Bank Marketplace API?

Yes. Jentic lets you allow only the operations your agent needs, for example listing partners and marketplaces while withholding deactivation and deletion. Your Jentic One instance enforces that boundary on every call and keeps the bearer token outside the agent's context.

Kapitalbank Az Marketplace & Partner Management API

AI ReadinessFoundational (D+)47/100

See full scorecard

Community OpenAPI document · agent-readyE CommerceStorefrontbearer14 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Manage merchant partners and marketplaces: create partners, register marketplaces, run approval and deactivation actions, and maintain contacts.

Use for: I need to onboard a new merchant partner, Approve a pending marketplace, Update the details of an existing marketplace, Deactivate a marketplace that is no longer active

Not supported: Does not process payments, settle transactions, or host storefronts; use it to manage marketplace partners and their status only.

The Kapital Bank Marketplace and Partner Management API administers merchant partners and their marketplaces. It creates and updates partner records, registers marketplaces, moves them through approval, rejection, and deactivation, and manages the contacts attached to each marketplace. Requests and responses are JSON over a single regional host, so an agent can onboard a partner or change a marketplace's status from one integration.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

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).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4

25%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

30%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

21%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

64%

Summary Coverage

Coverage of summaries across operations/tags/info.

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.

Security

Trust, risk posture, and security compliance.

Grade: A-Signals: 1

75%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1

61%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Marketplace & Partner Management API to your agent

Capabilities

Start building with Marketplace & Partner Management API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Kapitalbank Az Marketplace & Partner Management API

Jentic AI Readiness Score

Marketplace & Partner Management API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness