canonical: https://jentic.com/apis/swaggerhub.mlostaunau/automation-config-ui

# Mlostaunau Automation Config UI

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

## For AI agents

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

## Scope

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

## Capabilities

- Bin-typesPost
- Bin-typesGet
- Bin-typesPut
- Bin-typesDelete
- V1Bin-typesPost
- V1Bin-typesGet
- V1Bin-typesPut

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'bin-typespost', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

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

## Key resources

- **Bin Types** — Operations for bin types
- **Facilities** — Operations for facilities
- **Healthcheck** — Operations for healthcheck
- **Log** — Operations for log
- **Machines** — Operations for machines

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

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