Install Jentic One Beta

Connect the Auth Service to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Auth Service, 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.hypatos.ai%2Fswaggerhub-hypatos" | 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.hypatos.ai%2Fswaggerhub-hypatos" | 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 Auth Service API.

Request an access token

Manage identity auth data programmatically

Integrate Auth Service into automated workflows

Query and filter Auth Service records by parameters

Monitor Auth Service operational status and events

GET STARTED

Start building with Auth Service API

Explore with Jentic One

View OpenAPI Document

Data Retrieval and Monitoring

Query Auth Service 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 Service endpoint, compare response to last known state, and alert if changed

AI Agent Integration via Jentic

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

Search Jentic for 'request an access token', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

1 endpoints — auth service provides programmatic access to identity auth functionality.

METHOD

PATH

DESCRIPTION

POST

/auth/token

Request an access token

POST

/auth/token

Request an access token

Why Jentic?

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

Setup

Wiring the Hypatos Auth Service by hand means handling its OAuth2 client-credentials and basic auth, choosing the right EU (api.cloud.hypatos.ai) or US (api.cloud.hypatos.com) host, and requesting tokens yourself. Through Jentic you install once, import the Auth Service from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

The token request travels in the request body against /auth/token, so scope the agent to the operations it needs, such as requesting an access token, rather than to a single resource. You choose the operations it may call, so only that request is included unless you add more.

Credential isolation

Your Hypatos client 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 'request an access token', and Jentic returns the matching Auth Service operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Auth Service API through Jentic.

What authentication does the Auth Service use?

The Auth Service uses basic, oauth2 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 request an access token with the Auth Service?

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

What are the rate limits for the Auth Service?

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 request 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 'request an access token'. Jentic returns the matching Auth Service operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Auth Service have?

The Auth Service exposes 1 endpoints covering authorization operations.

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

Yes. Because Jentic One is self-hosted, you set the rules that decide which operations and credentials your agent may use. The Auth Service exposes a single operation, POST /auth/token to request an access token, so you scope the agent to just that call and it can do nothing more unless you allow it. Your Hypatos client credentials stay stored in your own Jentic One instance and are injected only when a permitted operation runs.

Hypatos Auth Service

Name: Auth Service API
Brand: Auth Service
Availability: InStock

Community OpenAPI document · agent-readyIdentity AuthAuthenticationbasic, oauth21 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically request an access token. Covers 1 operations with basic, oauth2 authentication.

Use for: I need to request an access token, Find available identity auth operations, Get the current status of Auth Service resources, List all records from Auth Service

Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.

Auth Service provides programmatic access to identity auth functionality. The API exposes 1 endpoints secured with basic, oauth2 authentication.

Jentic One on Github View OpenAPI Document

Connect the Auth Service to your agent

Capabilities

Start building with Auth Service API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Hypatos Auth Service