DotAAS Part 2 | HTTP/REST | Asset Adminstration Shell API

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

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputenone20 EndpointsREST

For Agents

Connect the DotAAS Part 2 | HTTP/REST | Asset Adminstration Shell 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 Adminstration Shell 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 Adminstration Shell API API.

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

GET STARTED

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

Explore with Jentic

View OpenAPI Document

Use Cases

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

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

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.

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.

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

Key Endpoints

20 endpoints — an exemplary api combination for the use case of a standalone asset administration shell, e.

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

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

Why though Jentic?

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

Credential isolation

DotAAS Part 2 | HTTP/REST | Asset Adminstration Shell 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., 'returns the asset administration shell') and Jentic returns the matching DotAAS Part 2 | HTTP/REST | Asset Adminstration Shell 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 Adminstration Shell 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

Amazonaws

Alternative cloud infrastructure API

Choose Amazonaws when you need a different approach to cloud infrastructure operations

Alternative

Azure

Alternative cloud infrastructure API

Choose Azure when you need a different approach to cloud infrastructure operations

Complementary

Googleapis

Complementary cloud infrastructure API

Choose Googleapis when you need a complementary approach to cloud infrastructure operations

Complementary

Digitalocean

Complementary cloud infrastructure API

Choose Digitalocean when you need a complementary approach to cloud infrastructure operations

FAQs

Specific to using DotAAS Part 2 | HTTP/REST | Asset Adminstration Shell API API through Jentic.

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