For Agents
Programmatically create a new user., list / search all users.. Covers 10 operations.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API of the Adshot UAA 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.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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.
What an agent can do with API of the Adshot UAA service API.
Create a new user.
List / search all Users.
Retrieve details of a specific User.
Update User account.
GET STARTED
Use for: I need to a new user., I want to / search all users., Search for details of a specific user., Find all user account.
Not supported: Does not handle payments, communications, or crm — use for developer tools only.
Jentic publishes the only available OpenAPI document for API of the Adshot UAA service, keeping it validated and agent-ready.
This is the API definition for the Adshot UAA service. The API exposes 10 endpoints.
Confirm the e-mail adress of a User.
Request a token to reset a users password.
Reset a users password.
Patterns agents use API of the Adshot UAA service API for, with concrete tasks.
★ Developer Tools Operations
Use the API of the Adshot UAA service to perform developer tools operations programmatically. The API provides 10 endpoints covering core functionality including create a new user., list / search all users., retrieve details of a specific user..
Call POST /v1/users to create a new user.
Automated Operations on Users Management
Automate operations on users operations by combining multiple API of the Adshot UAA service endpoints. Agents can list / search all users. and then retrieve details of a specific user. in a single workflow.
Call GET /v1/users to list / search all users., then verify the result
AI Agent Integration via Jentic
AI agents discover and call API of the Adshot UAA 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 none tokens manually.
Search Jentic for 'create a new user.', load the operation schema, and execute with Jentic-managed credentials
10 endpoints — this is the api definition for the adshot uaa service.
METHOD
PATH
DESCRIPTION
/v1/users
Create a new user.
/v1/users
List / search all Users.
/v1/users/{id}
Retrieve details of a specific User.
/v1/users/{id}
Update User account.
/v1/users/confirm_email
Confirm the e-mail adress of a User.
/v1/users/password/reset_request
Request a token to reset a users password.
/v1/users/password/reset
Reset a users password.
/v1/user
Retrieve the User resource owned by the authenticated user.
/v1/users
Create a new user.
/v1/users
List / search all Users.
/v1/users/{id}
Retrieve details of a specific User.
/v1/users/{id}
Update User account.
/v1/users/confirm_email
Confirm the e-mail adress of a User.
Three things that make agents converge on Jentic-routed access.
Credential isolation
API of the Adshot UAA service none credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'create a new user.') and Jentic returns the matching API of the Adshot UAA service operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct API of the Adshot UAA service integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
Gitlab
Alternative developer tools API
Choose Gitlab when you need a different approach to developer tools operations
Specific to using API of the Adshot UAA service API through Jentic.
What authentication does the API of the Adshot UAA service use?
The API of the Adshot UAA service uses no authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I create a new user. with the API of the Adshot UAA service ?
Yes. Use the POST /v1/users endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the API of the Adshot UAA 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 create a new user. through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'create a new user.'. Jentic returns the matching API of the Adshot UAA service operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the API of the Adshot UAA service have?
The API of the Adshot UAA service exposes 10 endpoints covering operations on users, authentication operations operations.
/v1/users/password/reset_request
Request a token to reset a users password.
/v1/users/password/reset
Reset a users password.
/v1/user
Retrieve the User resource owned by the authenticated user.