Plattform I40 DotAAS Part 2 | HTTP/REST | AASX File Server Service Specification
Browse all Swaggerhub Plattform I40 APIsCommunity OpenAPI document · agent-readyDeveloper ToolsSource Controlnone6 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically stores the aasx package at the server, returns a list of available aasx packages at the server. Covers 6 operations.
Use for: I need to stores the aasx package at the server, I want to returns a list of available aasx packages at the server, Search for returns a specific aasx package from the server, Find all creates or updates the aasx package at the server
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
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.
Install Jentic One Beta
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.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.plattform-i40%2Fdotaas-part-2-httprest-aasx-file-server-service-sp" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.plattform-i40%2Fdotaas-part-2-httprest-aasx-file-server-service-sp" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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
Monitor DotAAS Part 2 | HTTP/REST | AASX File Server Service Specification operational status and events
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
GET
/description
Returns the self-describing information of a network resource (ServiceDescriptio
Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
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 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.
GET STARTED