Airvantage Team av_microservice_gatekeeper
Browse all Swaggerhub Airvantage Team APIs★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputenone9 EndpointsREST
For Agents
Programmatically this endpoint is used to retrieve the current maintenace mode., this endpoint is used to set the maintenance mode.. Covers 9 operations.
Use for: I need to this endpoint is used to retrieve the current maintenace mode., I want to this endpoint is used to set the maintenance mode., Search for this endpoint is used to authorize a client/internal call and then send a json w, Find all this endpoint is used to add a user to the database who might need to use json w
Not supported: Does not handle payments, communications, or crm — use for cloud infrastructure only.
**Release Notes** |Version| Detail| |---|---| |5.0.21 |Logging issues fixed when logging all even though set to error. | |5.0.12 |Addition of UI endpoints. | |5.0.9 |Upgraded to Java 17. | |4.0.8 |Upgraded to Java 11 and containerised. Added /authorize endpoint. | **Introduction** This microservice acts as a central gatekeeper for calls coming in from a variety of channels. This microservice is us. The API exposes 9 endpoints.
Install Jentic One Beta
Connect the av_microservice_gatekeeper to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the av_microservice_gatekeeper, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: 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 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 av_microservice_gatekeeper API.
This endpoint is used to retrieve the current maintenace mode.
Manage cloud infrastructure data programmatically
Integrate av_microservice_gatekeeper into automated workflows
Query and filter av_microservice_gatekeeper records by parameters
Monitor av_microservice_gatekeeper operational status and events
Use Cases
Patterns agents use av_microservice_gatekeeper API for, with concrete tasks.
★ Cloud Infrastructure Operations
Use the av_microservice_gatekeeper to perform cloud infrastructure operations programmatically. The API provides 9 endpoints covering core functionality including this endpoint is used to retrieve the current maintenace mode., this endpoint is used to set the maintenance mode., this endpoint is used to authorize a client/internal call and then send a json w.
Call GET /getMode to this endpoint is used to retrieve the current maintenace mode.
Automated Private Management
Automate private operations by combining multiple av_microservice_gatekeeper endpoints. Agents can this endpoint is used to set the maintenance mode. and then this endpoint is used to authorize a client/internal call and then send a json w in a single workflow.
Call GET /setMode to this endpoint is used to set the maintenance mode., then verify the result
AI Agent Integration via Jentic
AI agents discover and call av_microservice_gatekeeper 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 'this endpoint is used to retrieve the current maintenace mode.', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
9 endpoints — **release notes** |version| detail| |---|---| |5.
METHOD
PATH
DESCRIPTION
GET
/getMode
This endpoint is used to retrieve the current maintenace mode.
GET
/setMode
This endpoint is used to set the maintenance mode.
POST
/authorize
This endpoint is used to authorize a client/internal call and then send a JSON w
POST
/addUser
This endpoint is used to add a user to the database who might need to use JSON W
GET
/getUserInfo
This endpoint is used to retrieve the role and other data for a user.
GET
/getUsers
This endpoint is used to retrieve the user(s) list.
POST
/modifyRole
This endpoint is used to modify the role of a user.
POST
/resetPassword
This endpoint is used to modify an existing user's password.
GET
/getMode
This endpoint is used to retrieve the current maintenace mode.
GET
/setMode
This endpoint is used to set the maintenance mode.
POST
/authorize
This endpoint is used to authorize a client/internal call and then send a JSON w
POST
/addUser
This endpoint is used to add a user to the database who might need to use JSON W
GET
/getUserInfo
This endpoint is used to retrieve the role and other data for a user.
GET
/getUsers
This endpoint is used to retrieve the user(s) list.
POST
/modifyRole
This endpoint is used to modify the role of a user.
POST
/resetPassword
This endpoint is used to modify an existing user's password.
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
av_microservice_gatekeeper 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., 'this endpoint is used to retrieve the current maintenace mode.') and Jentic returns the matching av_microservice_gatekeeper operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct av_microservice_gatekeeper 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.
FAQs
Specific to using av_microservice_gatekeeper API through Jentic.
What authentication does the av_microservice_gatekeeper use?
The av_microservice_gatekeeper 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 this endpoint is used to retrieve the current maintenace mode. with the av_microservice_gatekeeper?
Yes. Use the GET /getMode endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the av_microservice_gatekeeper?
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 this endpoint is used to retrieve the current maintenace mode. through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'this endpoint is used to retrieve the current maintenace mode.'. Jentic returns the matching av_microservice_gatekeeper operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the av_microservice_gatekeeper have?
The av_microservice_gatekeeper exposes 9 endpoints covering private operations.
GET STARTED