Mkhisa7 Auth
Browse all Swaggerhub Mkhisa7 APIsCommunity OpenAPI document · agent-readyIdentity AuthAuthorizationbasic1 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically provide client and merchant credentials to obtain an access token.. Covers 1 operations with basic authentication.
Use for: I need to provide client and merchant credentials to obtain an access token., Find available identity auth operations, Get the current status of Auth resources, List all records from Auth
Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.
This API enables an application or service (by extension and organization) access the mapped resources that it has been granted to. The API exposes 1 endpoints secured with basic authentication.
Install Jentic One Beta
Connect the Auth to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Auth, 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.mkhisa7%2Fauth" | 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.mkhisa7%2Fauth" | 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 Auth API.
Provide Client and Merchant Credentials to obtain an Access Token.
Manage identity auth data programmatically
Integrate Auth into automated workflows
Query and filter Auth records by parameters
Monitor Auth operational status and events
Use Cases
Patterns agents use Auth API for, with concrete tasks.
★ Identity and Authentication Operations
Use the Auth to perform identity auth operations programmatically. The API provides 1 endpoints covering core functionality including provide client and merchant credentials to obtain an access token..
Call POST /merchant-token to provide client and merchant credentials to obtain an access token.
Data Retrieval and Monitoring
Query Auth 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 Auth endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call Auth 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 basic tokens manually.
Search Jentic for 'provide client and merchant credentials to obtain an access token.', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
1 endpoints — this api enables an application or service (by extension and organization) access the mapped resources that it has been granted to.
METHOD
PATH
DESCRIPTION
POST
/merchant-token
Provide Client and Merchant Credentials to obtain an Access Token.
POST
/merchant-token
Provide Client and Merchant Credentials to obtain an Access Token.
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Equity Bank Auth API by hand means learning its HTTP basic auth over client and merchant credentials, targeting its sandbox identity host, and handling retries yourself. Through Jentic you install once, import the Auth API from the API Directory, store the basic credentials once, and your agent calls it.
Permission scoping
This API carries its credentials in the request body rather than the URL path, so scope the agent to the single operation it needs: obtaining a merchant token. You choose the operations it may call, so nothing beyond that token exchange runs unless you add it.
Credential isolation
Your Auth API basic credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get a merchant access token', and Jentic returns the matching Auth API 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.
FAQs
Specific to using Auth API through Jentic.
What authentication does the Auth use?
The Auth uses HTTP Basic authentication with username and password. 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 provide client and merchant credentials to obtain an access token. with the Auth?
Yes. Use the POST /merchant-token endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Auth?
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 provide client and merchant credentials to obtain an access token. through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'provide client and merchant credentials to obtain an access token.'. Jentic returns the matching Auth operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Auth have?
The Auth exposes 1 endpoints covering auth operations.
Can I limit what my agent is allowed to do with the Auth API?
Yes. Because you run Jentic One yourself, you decide which operations and credentials the agent may use, and your rules are enforced at execution time. This API exposes a single operation, POST /merchant-token, which exchanges client and merchant credentials for an access token, so you can scope the agent to only that token exchange and nothing else runs unless you add it. The basic-auth credentials travel in the request body rather than the URL, and they stay stored on your own instance and are injected at call time rather than exposed to the agent.
GET STARTED