Swaggerhub Plattform I40 APIs
APIs7 in catalogue
Endpoints189 indexed
CategoriesCloud Infrastructure, Developer Tools
Categories
API Catalog(3 of 7)
DotAAS Part 2 | HTTP/REST | AASX File Server API
The AASX file server API as part of Details of the Asset Administration Shell Part 2. The API exposes 5 endpoints.
5 endpoints
DotAAS Part 2 | HTTP/REST | Asset Administration Shell Service Specification
The Full Profile of the [Specification of the Asset Administration Shell: Part 2](https://industrialdigitaltwin.org/en/content-hub/aasspecifications) for the use case of a standalone Asset Administration Shell, e.g., an Asset Administration Shell running in a Docker container. Copyright: Industrial Digital Twin Association (IDTA) 2025. The API exposes 50 endpoints.
50 endpoints
DotAAS Part 2 | HTTP/REST | Asset Adminstration Shell API
An exemplary API combination for the use case of a standalone Asset Administration Shell, e.g., an Asset Administration Shell running in a Docker container. The API exposes 20 endpoints.
20 endpoints
Connect Your Agent
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" | 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" | 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.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.