DotAAS Part 2 | HTTP/REST | Asset Administration Shell Environment API

Name: DotAAS Part 2 | HTTP/REST | Asset Administration Shell Environment API API
Brand: DotAAS Part 2 | HTTP/REST | Asset Administration Shell Environment API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlnone43 EndpointsREST

For Agents

Connect the DotAAS Part 2 | HTTP/REST | Asset Administration Shell Environment API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DotAAS Part 2 | HTTP/REST | Asset Administration Shell Environment API, 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 DotAAS Part 2 | HTTP/REST | Asset Administration Shell Environment API API.

Creates a new Asset Administration Shell

Returns all Asset Administration Shells

Updates an existing Asset Administration Shell

Deletes an Asset Administration Shell

GET STARTED

Start building with DotAAS Part 2 | HTTP/REST | Asset Administration Shell Environment API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use DotAAS Part 2 | HTTP/REST | Asset Administration Shell Environment API API for, with concrete tasks.

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

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.

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.

Search Jentic for 'creates a new asset administration shell', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

43 endpoints — an exemplary api combination for the use case of an asset administration shell environment.

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

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

Why though Jentic?

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

Credential isolation

DotAAS Part 2 | HTTP/REST | Asset Administration Shell Environment API 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., 'creates a new asset administration shell') and Jentic returns the matching DotAAS Part 2 | HTTP/REST | Asset Administration Shell Environment API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct DotAAS Part 2 | HTTP/REST | Asset Administration Shell Environment API 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 DotAAS Part 2 | HTTP/REST | Asset Administration Shell Environment API API through Jentic.

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