DotAAS Part 2 | HTTP/REST | AASX File Server Service Specification

Name: DotAAS Part 2 | HTTP/REST | AASX File Server Service Specification API
Brand: DotAAS Part 2 | HTTP/REST | AASX File Server Service Specification
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlnone6 EndpointsREST

For Agents

Connect the DotAAS Part 2 | HTTP/REST | AASX File Server Service Specification 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 | AASX File Server Service Specification, 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 | AASX File Server Service Specification API.

Stores the AASX package at the server

Returns a list of available AASX packages at the server

Creates or updates the AASX package at the server

Deletes a specific AASX package from the server

GET STARTED

Start building with DotAAS Part 2 | HTTP/REST | AASX File Server Service Specification API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use DotAAS Part 2 | HTTP/REST | AASX File Server Service Specification API for, with concrete tasks.

★ Developer Tools Operations

Use the DotAAS Part 2 | HTTP/REST | AASX File Server Service Specification to perform developer tools operations programmatically. The API provides 6 endpoints covering core functionality including stores the aasx package at the server, returns a list of available aasx packages at the server, returns a specific aasx package from the server.

Call POST /packages to stores the aasx package at the server

Automated Description Management

Automate description operations by combining multiple DotAAS Part 2 | HTTP/REST | AASX File Server Service Specification endpoints. Agents can returns a list of available aasx packages at the server and then returns a specific aasx package from the server in a single workflow.

Call GET /packages to returns a list of available aasx packages at the server, then verify the result

AI Agent Integration via Jentic

AI agents discover and call DotAAS Part 2 | HTTP/REST | AASX File Server Service Specification 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 'stores the aasx package at the server', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

6 endpoints — the file server service specification as part of the [specification of the asset administration shell: part 2](https://industrialdigitaltwin.

METHOD

PATH

DESCRIPTION

POST

/packages

Stores the AASX package at the server

GET

/packages

Returns a list of available AASX packages at the server

GET

/packages/{packageId}

Returns a specific AASX package from the server

PUT

/packages/{packageId}

Creates or updates the AASX package at the server

DELETE

/packages/{packageId}

Deletes a specific AASX package from the server

GET

/description

Returns the self-describing information of a network resource (ServiceDescriptio

POST

/packages

Stores the AASX package at the server

GET

/packages

Returns a list of available AASX packages at the server

GET

/packages/{packageId}

Returns a specific AASX package from the server

PUT

/packages/{packageId}

Creates or updates the AASX package at the server

DELETE

/packages/{packageId}

Deletes a specific AASX package from the server

Why though Jentic?

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

Credential isolation

DotAAS Part 2 | HTTP/REST | AASX File Server Service Specification 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., 'stores the aasx package at the server') and Jentic returns the matching DotAAS Part 2 | HTTP/REST | AASX File Server Service Specification 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 | AASX File Server Service Specification 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 | AASX File Server Service Specification API through Jentic.

What authentication does the DotAAS Part 2 | HTTP/REST | AASX File Server Service Specification use?

The DotAAS Part 2 | HTTP/REST | AASX File Server Service Specification 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 stores the aasx package at the server with the DotAAS Part 2 | HTTP/REST | AASX File Server Service Specification?

Yes. Use the POST /packages 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 | AASX File Server Service Specification?

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 stores the aasx package at the server through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'stores the aasx package at the server'. Jentic returns the matching DotAAS Part 2 | HTTP/REST | AASX File Server Service Specification 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 | AASX File Server Service Specification have?

The DotAAS Part 2 | HTTP/REST | AASX File Server Service Specification exposes 6 endpoints covering description, packages operations.