Axeta 5BOX
Browse all Swaggerhub Axeta APIs★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlbearer7 EndpointsREST
For Agents
Programmatically авторизация, обновление токена. Covers 7 operations with bearer authentication.
Use for: I need to авторизация, I want to обновление токена, Search for выход, Find all получение пользователя
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Backend API для мобильного приложения сотрудников. The API exposes 7 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the 5BOX to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the 5BOX, 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.axeta%2F5box" | 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.axeta%2F5box" | 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 5BOX API.
Авторизация
Обновление токена
Выход
Получение пользователя
Контроллер принимает QR коды от входной двери
Use Cases
Patterns agents use 5BOX API for, with concrete tasks.
★ Developer Tools Operations
Use the 5BOX to perform developer tools operations programmatically. The API provides 7 endpoints covering core functionality including авторизация, обновление токена, выход.
Call POST /authorize to авторизация
Automated Авторизация Management
Automate авторизация operations by combining multiple 5BOX endpoints. Agents can обновление токена and then выход in a single workflow.
Call POST /token/refresh to обновление токена, then verify the result
AI Agent Integration via Jentic
AI agents discover and call 5BOX 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 bearer tokens manually.
Search Jentic for 'авторизация', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
7 endpoints — backend api для мобильного приложения сотрудников.
METHOD
PATH
DESCRIPTION
POST
/authorize
Авторизация
POST
/token/refresh
Обновление токена
POST
/logout
Выход
GET
/account/user
Получение пользователя
POST
/shops/scan
Контроллер принимает QR коды от входной двери
GET
/shops
Получение списка магазинов
GET
/tasks
Получение списка заданий пользователя
POST
/authorize
Авторизация
POST
/token/refresh
Обновление токена
POST
/logout
Выход
GET
/account/user
Получение пользователя
POST
/shops/scan
Контроллер принимает QR коды от входной двери
GET
/shops
Получение списка магазинов
GET
/tasks
Получение списка заданий пользователя
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
This 5BOX API uses bearer authentication with JWT tokens, so hand-wiring it means obtaining and refreshing the token, attaching the Authorization header to every call, and handling retries yourself. Through Jentic you install once, import 5BOX from the API Directory, store the token once, and your agent calls it.
Permission scoping
This API works through account, shop, and task operations whose targets travel in the request rather than a resource id in the URL path, so scope by operation: limit the agent to the operations it needs, such as reading the account user, listing shops, or listing tasks, and leave logout out unless you add it.
Credential isolation
Your 5BOX bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'authorize a session' or 'list shops', and Jentic returns the matching 5BOX 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.
Alternative
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using 5BOX API through Jentic.
What authentication does the 5BOX use?
The 5BOX uses a Bearer token in the Authorization header. 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 авторизация with the 5BOX?
Yes. Use the POST /authorize endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the 5BOX?
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 авторизация through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'авторизация'. Jentic returns the matching 5BOX operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the 5BOX have?
The 5BOX exposes 7 endpoints covering авторизация, аккаунт, задания operations.
Can I limit what my agent is allowed to do with the 5BOX API?
Yes. Because you run Jentic One yourself, you decide which 5BOX operations and credentials the agent may use, and it can call only the ones you allow. Since 5BOX passes account, shop, and task targets in the request body rather than as an id in the URL path, you scope by operation: grant just the endpoints the agent needs, such as reading the account user, listing shops, or listing tasks. Leave operations like logout out of the allowed set unless you explicitly add them.
GET STARTED