canonical: https://jentic.com/apis/swaggerhub.plattform-i40/dotaas-part-2-httprest-asset-administration-shell- # Plattform I40 DotAAS Part 2 | HTTP/REST | Asset Administration Shell Environment API An exemplary API combination for the use case of an Asset Administration Shell Environment. The API exposes 43 endpoints. ## For AI agents Programmatically creates a new asset administration shell, returns all asset administration shells. Covers 43 operations. ## Scope Does not handle payments, communications, or crm - use for developer tools only. ## Capabilities - Creates a new Asset Administration Shell - Returns all Asset Administration Shells - Updates an existing Asset Administration Shell - Deletes an Asset Administration Shell - Monitor DotAAS Part 2 | HTTP/REST | Asset Administration Shell Environment API operational status and events ## Use cases ### Developer Tools Operations Use the DotAAS Part 2 | HTTP/REST | Asset Administration Shell Environment API to perform developer tools operations programmatically. The API provides 43 endpoints covering core functionality including creates a new asset administration shell, returns all asset administration shells, returns a specific asset administration shell. Example prompt: Call POST /shells to creates a new asset administration shell ### Automated Concept Descriptions Management Automate concept descriptions operations by combining multiple DotAAS Part 2 | HTTP/REST | Asset Administration Shell Environment API endpoints. Agents can returns all asset administration shells and then returns a specific asset administration shell in a single workflow. Example prompt: Call GET /shells to returns all asset administration shells, then verify the result ### AI Agent Integration via Jentic AI agents discover and call DotAAS Part 2 | HTTP/REST | Asset Administration Shell Environment 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 'creates a new asset administration shell', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/shells` | Creates a new Asset Administration Shell | | GET | `/shells` | Returns all Asset Administration Shells | | GET | `/shells/{aasIdentifier}` | Returns a specific Asset Administration Shell | | PUT | `/shells/{aasIdentifier}` | Updates an existing Asset Administration Shell | | DELETE | `/shells/{aasIdentifier}` | Deletes an Asset Administration Shell | | GET | `/shells/{aasIdentifier}/asset-information` | Returns the Asset Information | | PUT | `/shells/{aasIdentifier}/asset-information` | Updates the Asset Information | | POST | `/shells/{aasIdentifier}/submodels` | Creates a submodel reference at the Asset Administration Shell | ## Key resources - **Concept Descriptions** — Operations for concept descriptions - **Serialization** — Operations for serialization - **Shells** — Operations for shells - **Submodels** — Operations for submodels ## Why Jentic - **Setup:** Wiring the Asset Administration Shell Environment API by hand means resolving its templated protocol, host, port, and version prefix into a base URL, threading shell and submodel identifiers through each route, and parsing the shell, submodel, and concept-description responses yourself. Through Jentic you install once, import the Asset Administration Shell Environment API from the API Directory, and since it takes no credential your agent calls it straight away. - **Permission scoping:** The Asset Administration Shell Environment API puts the shell identifier in the URL path (`/shells/{aasIdentifier}`), so a rule can pin your agent to one shell and nothing else. You choose the operations it may call, so a destructive one like deleting a shell is not included unless you add it. - **Credential handling:** The Asset Administration Shell Environment 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 'list all shells' or 'read a concept description', and Jentic returns the matching Asset Administration Shell Environment API 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 DotAAS Part 2 | HTTP/REST | Asset Administration Shell Environment API use? The DotAAS Part 2 | HTTP/REST | Asset Administration Shell Environment 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 creates a new asset administration shell with the DotAAS Part 2 | HTTP/REST | Asset Administration Shell Environment API? Yes. Use the POST /shells 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 Administration Shell Environment 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 creates a new 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 'creates a new asset administration shell'. Jentic returns the matching DotAAS Part 2 | HTTP/REST | Asset Administration Shell Environment 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 Administration Shell Environment API have? The DotAAS Part 2 | HTTP/REST | Asset Administration Shell Environment API exposes 43 endpoints covering concept descriptions, serialization, shells operations. ### Can I limit what my agent is allowed to do with the Asset Administration Shell Environment API? Yes. Because you run Jentic One yourself, your own rules decide which of this API's operations your agent may call, so you can grant read and list calls like GET /shells while withholding a destructive one such as DELETE `/shells/{aasIdentifier}.` Since the shell identifier sits in the URL path, a rule can pin the agent to a single shell and block every other one. The API needs no credential, so there is nothing extra to expose when you scope it this way.