DotAAS Part 2 | HTTP/REST | AASX File Server API

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

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputenone5 EndpointsREST

For Agents

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

Stores the AASX package at the server

Returns a list of available AASX packages at the server

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

Explore with Jentic

View OpenAPI Document

Use Cases

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

★ Cloud Infrastructure Operations

Use the DotAAS Part 2 | HTTP/REST | AASX File Server API to perform cloud infrastructure operations programmatically. The API provides 5 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 AASX File Server API Management

Automate aasx file server api operations by combining multiple DotAAS Part 2 | HTTP/REST | AASX File Server API 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 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 'stores the aasx package at the server', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

5 endpoints — the aasx file server api as part of details of the asset administration shell part 2.

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}

Updates the AASX package at the server

DELETE

/packages/{packageId}

Deletes a specific AASX package from the server

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}

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

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

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

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 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 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 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 | AASX File Server API have?

The DotAAS Part 2 | HTTP/REST | AASX File Server API exposes 5 endpoints covering aasx file server api operations.