canonical: https://jentic.com/apis/swaggerhub.airvantage-team/avmicroservicegatekeeper

# Airvantage Team av_microservice_gatekeeper

**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.

## For AI agents

Programmatically this endpoint is used to retrieve the current maintenace mode., this endpoint is used to set the maintenance mode.. Covers 9 operations.

## Scope

Does not handle payments, communications, or crm - use for cloud infrastructure only.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

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

## Key resources

- **Private** — Operations related to Private

## Why Jentic

- **Setup:** Wiring av_microservice_gatekeeper by hand means calling its access-control operations against the hosted host yourself: authorizing users, reading user info, and toggling maintenance mode on your own. Through Jentic you install once, import av_microservice_gatekeeper from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** av_microservice_gatekeeper exposes flat operation paths rather than per-resource URLs, so limit the agent to the operations it needs, such as getUserInfo or getMode. You choose the operations it may call, so ones that change access like addUser, modifyRole, or resetPassword are not included unless you add them.
- **Credential handling:** Your av_microservice_gatekeeper credential 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.
- **Discovery method:** Agents search Jentic by intent such as 'read the current maintenance mode' or 'list users', and Jentic returns the matching av_microservice_gatekeeper operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Amazonaws** — Alternative cloud infrastructure API
- **Azure** — Alternative cloud infrastructure API
- **Googleapis** — Complementary cloud infrastructure API
- **Digitalocean** — Complementary cloud infrastructure API

## FAQ

### What authentication does the av_microservice_gatekeeper use?

The av_microservice_gatekeeper uses no authentication. 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 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 through Jentic One, the self-hosted execution layer, 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.

### Can I limit what my agent is allowed to do with the av_microservice_gatekeeper?

Yes. Because you run Jentic One yourself, your own rules decide which av_microservice_gatekeeper operations and credentials the agent may use. Since the API exposes flat operation paths rather than per-resource URLs, you scope the agent to just the operations it needs, such as getMode or getUserInfo. Access-changing operations like addUser, modifyRole, and resetPassword stay off limits unless you explicitly grant them.