Install Jentic One Beta

Connect the Enterprise Admin Service API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Enterprise Admin Service 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.uday730%2Fenterprise-admin-service-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.uday730%2Fenterprise-admin-service-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 Enterprise Admin Service API.

Run

Manage developer tools data programmatically

Integrate Enterprise Admin Service API into automated workflows

Query and filter Enterprise Admin Service API records by parameters

Monitor Enterprise Admin Service API operational status and events

GET STARTED

Start building with Enterprise Admin Service API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Enterprise Admin Service API for, with concrete tasks.

★ Developer Tools Operations

Use the Enterprise Admin Service API to perform developer tools operations programmatically. The API provides 5 endpoints covering core functionality including run, run1, run2.

Call POST /CreateUser to run

Automated Create User Management

Automate create user operations by combining multiple Enterprise Admin Service API endpoints. Agents can run1 and then run2 in a single workflow.

Call GET /GetCompanyById to run1, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Enterprise Admin Service 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 oauth2 tokens manually.

Search Jentic for 'run', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

5 endpoints — enterprise admin service api.

METHOD

PATH

DESCRIPTION

POST

/CreateUser

Run

GET

/GetCompanyById

Run1

POST

/GetUserAuthorizations

Run2

GET

/GetUserByObjectId

Run4

GET

/GetUsersByCompanyId

Run3

POST

/CreateUser

Run

GET

/GetCompanyById

Run1

POST

/GetUserAuthorizations

Run2

GET

/GetUserByObjectId

Run4

GET

/GetUsersByCompanyId

Run3

Why Jentic?

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

Setup

Wiring the Enterprise Admin Service API by hand means implementing its OAuth2 flow, managing token refresh against the Azure API Management host, and building your own retries. Through Jentic you install once, import the Enterprise Admin Service API from the API Directory, store the OAuth2 credentials once, and your agent calls it.

Permission scoping

Limit the agent to the operations it needs, such as looking up a company or reading a user's authorizations, rather than the whole surface. You choose the allowed operations, so user creation is not included unless you add it.

Credential isolation

Your Enterprise Admin Service OAuth2 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 company by id' or 'get users by company id', and Jentic returns the matching Enterprise Admin Service 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

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 Enterprise Admin Service API through Jentic.

What authentication does the Enterprise Admin Service API use?

The Enterprise Admin Service API uses OAuth 2.0 for authorization. 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 run with the Enterprise Admin Service API?

Yes. Use the POST /CreateUser endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Enterprise Admin Service 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 run through Jentic?

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

How many endpoints does the Enterprise Admin Service API have?

The Enterprise Admin Service API exposes 5 endpoints covering create user, get user authorizations details, get user details operations.

Can I limit what my agent is allowed to do with the Enterprise Admin Service API?

Yes. Because Jentic One is self-hosted, you decide which of the five operations your agent may call and which OAuth2 credentials it uses. You can allow read-only operations such as GET /GetCompanyById, GET /GetUserByObjectId, and reading a user's authorizations, while excluding POST /CreateUser so the agent cannot create users unless you add that operation. The credentials the agent runs under are the ones you configure, so its access never exceeds the operations you have permitted.

Uday730 Enterprise Admin Service API

Name: Enterprise Admin Service API
Brand: Enterprise Admin Service API
Availability: InStock

Browse all Swaggerhub Uday730 APIs

Community OpenAPI document · agent-readyDeveloper ToolsSource Controloauth25 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically run, run1. Covers 5 operations with oauth2 authentication.

Use for: I need to run, I want to run1, Search for run2, Find all run4

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

Enterprise Admin Service API. The API exposes 5 endpoints secured with oauth2 authentication.

Jentic One on Github View OpenAPI Document