canonical: https://jentic.com/apis/swaggerhub.plattform-i40/dotaas-part-2-httprest-aasx-file-server-service-sp

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

The File Server Service Specification as part of the [Specification of the Asset Administration Shell: Part 2](https://industrialdigitaltwin.org/en/content-hub/aasspecifications). Copyright: Industrial Digital Twin Association (IDTA) 2025. The API exposes 6 endpoints.

## For AI agents

Programmatically stores the aasx package at the server, returns a list of available aasx packages at the server. Covers 6 operations.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- 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
- Monitor DotAAS Part 2 | HTTP/REST | AASX File Server Service Specification operational status and events

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'stores the aasx package at the server', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

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

## Key resources

- **Description** — Operations for description
- **Packages** — Operations for packages

## Why Jentic

- **Setup:** Wiring the AASX File Server Service Specification by hand means pointing at the admin-shell.io v3 host, matching each package path yourself, and parsing the upload, retrieval, and description responses. Through Jentic you install once, import the AASX File Server Service Specification from the API Directory, and since it takes no credential your agent calls it straight away.
- **Permission scoping:** The AASX File Server Service Specification puts the package id in the URL path (`/packages/{packageId}`), so a rule can pin your agent to one package and nothing else. You choose the operations it may call, so a destructive one like deleting a package is not included unless you add it.
- **Credential handling:** The AASX File Server Service Specification 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 'upload an AASX package' or 'read the server description', and Jentic returns the matching AASX File Server Service Specification 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 | 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

### Can I limit what my agent is allowed to do with the AASX File Server Service Specification?

Yes. Jentic One is self-hosted, so your own rules decide which operations the agent may call: you can grant read access through GET /packages and GET `/packages/{packageId}` while withholding a destructive call like DELETE `/packages/{packageId}` unless you explicitly add it. Because the package id sits in the URL path (`/packages/{packageId}`), a rule can pin the agent to a single package and nothing else. The agent only ever runs the operations you have allowed against the targets you have scoped.