Automation Config UI

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

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlnone156 EndpointsREST

For Agents

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

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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# 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 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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Automation Config UI 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., 'bin-typespost') and Jentic returns the matching Automation Config UI operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Automation Config UI integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.