Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Autostore Controller, 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.
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.apologistics-gmbh%2Fautostore-controller" | shStep 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.apologistics-gmbh%2Fautostore-controller" | 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.
What an agent can do with Autostore Controller API.
delivers a list of BINs with their content information which contains the reques
releases the requested BIN from the AutoStore via the transfer port
save a BIN to the Autostore which is delivered via the transfer port
Set or unset the compress mode of the AutoStore
returns whether CompressMode is enabled, if so including a list of affected port
GET STARTED
retrieves the content information for a specific BIN
Patterns agents use Autostore Controller API for, with concrete tasks.
★ E-Commerce Operations
Use the Autostore Controller to perform e commerce operations programmatically. The API provides 10 endpoints covering core functionality including delivers a list of bins with their content information which contains the reques, delivers a list of bins with their content information which contains the reques, releases the requested bin from the autostore via the transfer port.
Call GET /AutoStore/PZN/List/{pzn} to delivers a list of bins with their content information which contains the reques
Automated Autostore Management
Automate autostore operations by combining multiple Autostore Controller endpoints. Agents can delivers a list of bins with their content information which contains the reques and then releases the requested bin from the autostore via the transfer port in a single workflow.
Call GET /AutoStore/NTIN/List/{ntin} to delivers a list of bins with their content information which contains the reques, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Autostore Controller 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 basic tokens manually.
Search Jentic for 'delivers a list of bins with their content information which contains the reques', load the operation schema, and execute with Jentic-managed credentials
10 endpoints — autostore api für ein-/auslagerung/kommissionierung.
METHOD
PATH
DESCRIPTION
/AutoStore/PZN/List/{pzn}
delivers a list of BINs with their content information which contains the reques
/AutoStore/NTIN/List/{ntin}
delivers a list of BINs with their content information which contains the reques
/AutoStore/ReleaseAtTransferPort
releases the requested BIN from the AutoStore via the transfer port
/AutoStore/StoreAtTransferPort
save a BIN to the Autostore which is delivered via the transfer port
/AutoStore/SetCompressMode/{mode}
Set or unset the compress mode of the AutoStore
/AutoStore/CompressModeStatus
returns whether CompressMode is enabled, if so including a list of affected port
/Autostore/BinContent/{bin_id}
retrieves the content information for a specific BIN
/AutoStore/StoreAtCarouselPort
save a BIN to the Autostore which is delivered via the carousel port
/AutoStore/PZN/List/{pzn}
delivers a list of BINs with their content information which contains the reques
/AutoStore/NTIN/List/{ntin}
delivers a list of BINs with their content information which contains the reques
/AutoStore/ReleaseAtTransferPort
releases the requested BIN from the AutoStore via the transfer port
/AutoStore/StoreAtTransferPort
save a BIN to the Autostore which is delivered via the transfer port
/AutoStore/SetCompressMode/{mode}
Set or unset the compress mode of the AutoStore
/AutoStore/CompressModeStatus
returns whether CompressMode is enabled, if so including a list of affected port
/Autostore/BinContent/{bin_id}
retrieves the content information for a specific BIN
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Autostore Controller by hand means setting up its HTTP basic auth, tracking the bin and product-code paths, and sequencing the store and release port calls yourself. Through Jentic you install once, import the Autostore Controller from the API Directory, store the basic credentials once, and your agent calls it.
Permission scoping
This API puts the bin id in the URL path (/Autostore/BinContent/{bin_id}), so a rule can pin your agent to one bin's content and nothing else. You choose the operations it may call, so ones like releasing at a transfer port or changing compress mode are not included unless you add them.
Credential isolation
Your Autostore Controller basic credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get the contents of a bin' or 'release stock at a transfer port', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Stripe
Alternative e commerce API
Choose Stripe when you need a different approach to e commerce operations
Specific to using Autostore Controller API through Jentic.
What authentication does the Autostore Controller use?
The Autostore Controller uses HTTP Basic authentication with username and password. 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 delivers a list of bins with their content information which contains the reques with the Autostore Controller?
Yes. Use the GET /AutoStore/PZN/List/{pzn} endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Autostore Controller?
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 delivers a list of bins with their content information which contains the reques through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'delivers a list of bins with their content information which contains the reques'. Jentic returns the matching Autostore Controller operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Autostore Controller have?
The Autostore Controller exposes 10 endpoints covering autostore, autostore operations.
Can I limit what my agent is allowed to do with the Autostore Controller API?
Yes. Because you run Jentic One yourself, your own rules decide which Autostore Controller operations and credentials the agent may use. Since the bin id sits in the URL path at GET /Autostore/BinContent/{bin_id}, you can pin the agent to reading one bin's contents and nothing more, and you choose which operations it can call at all. Write actions such as POST /AutoStore/ReleaseAtTransferPort or PUT /AutoStore/SetCompressMode/{mode} stay off limits unless you explicitly add them.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically delivers a list of bins with their content information which contains the reques, delivers a list of bins with their content information which contains the reques. Covers 10 operations with basic authentication.
Use for: I need to delivers a list of bins with their content information which contains the reques, I want to delivers a list of bins with their content information which contains the reques, Search for releases the requested bin from the autostore via the transfer port, Find all save a bin to the autostore which is delivered via the transfer port
Not supported: Does not handle payments, communications, or crm - use for e-commerce only.
Autostore API für Ein-/Auslagerung/Kommissionierung. The API exposes 10 endpoints secured with basic authentication.
/AutoStore/StoreAtCarouselPort
save a BIN to the Autostore which is delivered via the carousel port