Install Jentic One Beta

Connect the Account Master API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Account Master 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%2Fswaggerhub.igtbdigital%2Faccount-master-api" | 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%2Fswaggerhub.igtbdigital%2Faccount-master-api" | 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 Account Master API.

To get the Accounts details

Delete Accounts Details

Adds new Account numbers to the system

Get all Accounts details

Update Account Details

GET STARTED

Start building with Account Master API

Explore with Jentic One

View OpenAPI Document

Automated Account Master Management

Automate account master operations by combining multiple Account Master API endpoints. Agents can delete accounts details and then adds new account numbers to the system in a single workflow.

Call DELETE /v1/common/accounts/{accountNo}/{bankEntityId} to delete accounts details, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Account Master 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 none tokens manually.

Search Jentic for 'to get the accounts details', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

5 endpoints — this is a account master api.

METHOD

PATH

DESCRIPTION

GET

/v1/common/accounts/{accountNo}/{bankEntityId}

To get the Accounts details

DELETE

/v1/common/accounts/{accountNo}/{bankEntityId}

Delete Accounts Details

POST

/v1/common/accounts

Adds new Account numbers to the system

GET

/v1/common/accounts

Get all Accounts details

PUT

/v1/common/accounts

Update Account Details

GET

/v1/common/accounts/{accountNo}/{bankEntityId}

To get the Accounts details

DELETE

/v1/common/accounts/{accountNo}/{bankEntityId}

Delete Accounts Details

POST

/v1/common/accounts

Adds new Account numbers to the system

GET

/v1/common/accounts

Get all Accounts details

PUT

/v1/common/accounts

Update Account Details

Why Jentic?

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

Setup

Wiring the Account Master API by hand means pointing at its SwaggerHub-hosted mock server, tracking the version in the base path, and handling the account request shapes yourself. Through Jentic you install once, import the Account Master API from the API Directory, and your agent calls it.

Permission scoping

The API puts the account number and bank entity id in the URL path (/v1/common/accounts/{accountNo}/{bankEntityId}), so a rule can pin your agent to one account: it can read that account and nothing else. You choose the operations it may call, so destructive ones like account deletion are not included unless you add them.

Credential isolation

This API declares no authentication, so there is no secret to pass. If the live endpoint later requires a credential, it is stored once, encrypted, by your own Jentic One instance and injected at execution time, never entering the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get an account by number and bank entity', and Jentic returns the matching Account Master API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Account Master API through Jentic.

What authentication does the Account Master API use?

The Account Master API uses no authentication. 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 to get the accounts details with the Account Master API?

Yes. Use the GET /v1/common/accounts/{accountNo}/{bankEntityId} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Account Master 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 to get the accounts details through Jentic?

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

How many endpoints does the Account Master API have?

The Account Master API exposes 5 endpoints covering account master operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Account Master API operations and credentials the agent can use. Since the account number and bank entity id sit in the URL path (/v1/common/accounts/{accountNo}/{bankEntityId}), you can pin the agent to a single account so it reads that account and nothing else. You also choose which operations it may call, so destructive ones like DELETE /v1/common/accounts/{accountNo}/{bankEntityId} stay out of reach unless you explicitly allow them.

Igtbdigital Account Master API

Name: Account Master API
Brand: Account Master API
Availability: InStock

Browse all Swaggerhub Igtbdigital APIs

AI ReadinessAI-Aware (A-)74/100

See full scorecard

Community OpenAPI document · agent-readyDeveloper ToolsSource Controlnone5 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically to get the accounts details, delete accounts details. Covers 5 operations.

Use for: I need to to get the accounts details, I want to accounts details, Search for adds new account numbers to the system, Find all all accounts details

Not supported: Does not handle payments, communications, or crm - use for developer tools only.

This is a Account Master API. The API exposes 5 endpoints.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

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

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: B-Signals: 4

39%

Example Density

How richly the API is illustrated with examples.

56%

Example Validity

Percentage of examples that conform to their schemas.

55%

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: C-Signals: 4

57%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

80%

OperationId Quality

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

71%

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.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

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.

Connect the Account Master API to your agent

Capabilities

Start building with Account Master API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Igtbdigital Account Master API

Jentic AI Readiness Score

Account Master 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