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.