Install Jentic One Beta

Connect the Automation Config UI to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Automation Config UI, 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.mlostaunau%2Fautomation-config-ui" | 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.mlostaunau%2Fautomation-config-ui" | 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 Automation Config UI API.

Bin-typesPost

Bin-typesGet

Bin-typesPut

Bin-typesDelete

V1Bin-typesPost

GET STARTED

Start building with Automation Config UI API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Automation Config UI API for, with concrete tasks.

★ Developer Tools Operations

Use the Automation Config UI to perform developer tools operations programmatically. The API provides 156 endpoints covering core functionality including bin-typespost, bin-typesget, bin-typesput.

Call POST /bin-types to bin-typespost

Automated Bin Types Management

Automate bin types operations by combining multiple Automation Config UI endpoints. Agents can bin-typesget and then bin-typesput in a single workflow.

Call GET /bin-types to bin-typesget, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Automation Config UI 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 'bin-typespost', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

156 endpoints — swaggerhub.

METHOD

PATH

DESCRIPTION

POST

/bin-types

Bin-typesPost

GET

/bin-types

Bin-typesGet

PUT

/bin-types

Bin-typesPut

DELETE

/bin-types

Bin-typesDelete

POST

/v1/bin-types

V1Bin-typesPost

GET

/v1/bin-types

V1Bin-typesGet

PUT

/v1/bin-types

V1Bin-typesPut

DELETE

/v1/bin-types

V1Bin-typesDelete

POST

/bin-types

Bin-typesPost

GET

/bin-types

Bin-typesGet

PUT

/bin-types

Bin-typesPut

DELETE

/bin-types

Bin-typesDelete

POST

/v1/bin-types

V1Bin-typesPost

GET

/v1/bin-types

V1Bin-typesGet

PUT

/v1/bin-types

V1Bin-typesPut

DELETE

/v1/bin-types

V1Bin-typesDelete

Why Jentic?

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

Setup

Wiring the Automation Config UI API by hand means mapping its large surface of configuration routes across versioned and unversioned paths, coding GET, POST, PUT, and DELETE for each, and handling retries yourself. Through Jentic you install once, import the Automation Config UI API from the API Directory, store any host details once, and your agent calls it.

Permission scoping

Many of this API's routes are collection endpoints that carry their target in the request body rather than the URL path, so scope the agent to the operations it needs, such as listing bin types. You choose the operations it may call, so destructive ones like deleting a bin type are not included unless you add them.

Credential isolation

Any access details for the Automation Config UI API 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 'list bin types' or 'create a bin type', and Jentic returns the matching Automation Config UI 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 Automation Config UI API through Jentic.

What authentication does the Automation Config UI use?

The Automation Config UI 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 bin-typespost with the Automation Config UI?

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

What are the rate limits for the Automation Config UI?

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 bin-typespost through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'bin-typespost'. Jentic returns the matching Automation Config UI operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Automation Config UI have?

The Automation Config UI exposes 156 endpoints covering bin types, facilities, healthcheck operations.

Can I limit what my agent is allowed to do with the Automation Config UI API?

Yes. Because you run Jentic One yourself, your own rules decide which Automation Config UI operations and credentials the agent may use. Since many routes are collection endpoints that carry their target in the request body rather than the URL path, you can grant only the operations the agent needs, such as listing bin types, and leave destructive ones like deleting a bin type out unless you explicitly add them. The agent can call nothing beyond the operations you have scoped for it.

Mlostaunau Automation Config UI

Name: Automation Config UI API
Brand: Automation Config UI
Availability: InStock

Browse all Swaggerhub Mlostaunau APIs

Community OpenAPI document · agent-readyDeveloper ToolsSource Controlnone156 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically bin-typespost, bin-typesget. Covers 156 operations.

Use for: I need to bin-typespost, I want to bin-typesget, Search for bin-typesput, Find all bin-typesdelete

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

swaggerhub.mlostaunau/automationcofigui version 1.0.0. The API exposes 156 endpoints.

Jentic One on Github View OpenAPI Document