canonical: https://jentic.com/apis/swaggerhub.plattform-i40/dotaas-part-2-httprest-asset-adminstration-shell-a

# Plattform I40 DotAAS Part 2 | HTTP/REST | Asset Adminstration Shell API

An exemplary API combination for the use case of a standalone Asset Administration Shell, e.g., an Asset Administration Shell running in a Docker container. The API exposes 20 endpoints.

## For AI agents

Programmatically returns the asset administration shell, updates the asset administration shell. Covers 20 operations.

## Scope

Does not handle payments, communications, or crm - use for cloud infrastructure only.

## Capabilities

- Returns the Asset Administration Shell
- Updates the Asset Administration Shell
- Creates a submodel reference at the Asset Administration Shell
- Deletes the submodel reference from the Asset Administration Shell
- Monitor DotAAS Part 2 | HTTP/REST | Asset Adminstration Shell API operational status and events

## Use cases

### Cloud Infrastructure Operations

Use the DotAAS Part 2 | HTTP/REST | Asset Adminstration Shell API to perform cloud infrastructure operations programmatically. The API provides 20 endpoints covering core functionality including returns the asset administration shell, updates the asset administration shell, returns the asset information.

Example prompt: Call GET /aas to returns the asset administration shell

### Automated Asset Administration Shell API Management

Automate asset administration shell API operations by combining multiple DotAAS Part 2 | HTTP/REST | Asset Adminstration Shell API endpoints. Agents can updates the asset administration shell and then returns the asset information in a single workflow.

Example prompt: Call PUT /aas to updates the asset administration shell, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call DotAAS Part 2 | HTTP/REST | Asset Adminstration Shell API 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 'returns the asset administration shell', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/aas` | Returns the Asset Administration Shell |
| PUT | `/aas` | Updates the Asset Administration Shell |
| GET | `/aas/asset-information` | Returns the Asset Information |
| PUT | `/aas/asset-information` | Updates the Asset Information |
| POST | `/aas/submodels` | Creates a submodel reference at the Asset Administration Shell |
| GET | `/aas/submodels` | Returns all submodel references |
| DELETE | `/aas/submodels/{submodelIdentifier}` | Deletes the submodel reference from the Asset Administration Shell |
| GET | `/aas/submodels/{submodelIdentifier}/submodel` | Returns the Submodel |

## Key resources

- **Asset Administration Shell API** — Operations related to Asset Administration Shell API

## Why Jentic

- **Setup:** Wiring the Asset Administration Shell API by hand means resolving its templated protocol, host, port, and version prefix into a base URL, threading submodel identifiers and idShort paths through each route, and parsing the shell and submodel responses yourself. Through Jentic you install once, import the Asset Administration Shell API from the API Directory, and since it takes no credential your agent calls it straight away.
- **Permission scoping:** The Asset Administration Shell API puts the submodel identifier in the URL path (`/aas/submodels/{submodelIdentifier}/submodel`), so a rule can pin your agent to one submodel and nothing else. You choose the operations it may call, so a destructive one like deleting a submodel is not included unless you add it.
- **Credential handling:** The Asset Administration Shell API needs no credential to call, so there is nothing to store. If you add related services later, any credential is stored once, encrypted, by your own Jentic One instance and injected at execution time, never entering the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'read the asset information' or 'get a submodel element', and Jentic returns the matching Asset Administration Shell API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Amazonaws** — Alternative cloud infrastructure API
- **Azure** — Alternative cloud infrastructure API
- **Googleapis** — Complementary cloud infrastructure API
- **Digitalocean** — Complementary cloud infrastructure API

## FAQ

### What authentication does the DotAAS Part 2 | HTTP/REST | Asset Adminstration Shell API use?

The DotAAS Part 2 | HTTP/REST | Asset Adminstration Shell API 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 returns the asset administration shell with the DotAAS Part 2 | HTTP/REST | Asset Adminstration Shell API?

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

### What are the rate limits for the DotAAS Part 2 | HTTP/REST | Asset Adminstration Shell API?

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 returns the asset administration shell through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'returns the asset administration shell'. Jentic returns the matching DotAAS Part 2 | HTTP/REST | Asset Adminstration Shell API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the DotAAS Part 2 | HTTP/REST | Asset Adminstration Shell API have?

The DotAAS Part 2 | HTTP/REST | Asset Adminstration Shell API exposes 20 endpoints covering asset administration shell API operations.

### Can I limit what my agent is allowed to do with the Asset Administration Shell API?

Yes. Because you run Jentic One yourself, you decide which of the Asset Administration Shell API operations your agent may call, so a destructive route like DELETE `/aas/submodels/{submodelIdentifier}` is off limits unless you add it. Since the submodel identifier sits in the URL path, a rule can pin the agent to a single submodel and block every other one. That lets you grant read-only access to GET /aas and its submodels while keeping the update and delete operations out of the agent's reach.