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

# Airvantage Team av_integration_mtc_api

This integration provides endpoints to check subscriber eligibility and to add advances for subscribers on the AV advance system</br>. The API exposes 2 endpoints.

## For AI agents

Programmatically this endpoint is used to check if a subscriber is eligible for an advance., this endpoint is used to register and process an advance for a subscriber.. Covers 2 operations.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- This endpoint is used to check if a subscriber is eligible for an advance.
- Manage developer tools data programmatically
- Integrate av_integration_mtc_api into automated workflows
- Query and filter av_integration_mtc_api records by parameters
- Monitor av_integration_mtc_api operational status and events

## Use cases

### Developer Tools Operations

Use the av_integration_mtc_api to perform developer tools operations programmatically. The API provides 2 endpoints covering core functionality including this endpoint is used to check if a subscriber is eligible for an advance., this endpoint is used to register and process an advance for a subscriber..

Example prompt: Call GET /canGetAdvance to this endpoint is used to check if a subscriber is eligible for an advance.

### Data Retrieval and Monitoring

Query av_integration_mtc_api resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary av_integration_mtc_api endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call av_integration_mtc_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.

Example prompt: Search Jentic for 'this endpoint is used to check if a subscriber is eligible for an advance.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /canGetAdvance | This endpoint is used to check if a subscriber is eligible for an advance. |
| GET | /processAdvance | This endpoint is used to register and process an advance for a subscriber. |

## Key resources

- **Endpoints** — Operations related to Endpoints

## Why Jentic

- **Setup:** Wiring av_integration_mtc_api by hand means calling its advance-eligibility and advance-processing operations against the hosted host yourself. Through Jentic you install once, import av_integration_mtc_api from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** av_integration_mtc_api exposes flat operation paths rather than per-resource URLs, so limit the agent to the operations it needs, such as checking eligibility with canGetAdvance. You choose the operations it may call, so processAdvance is not included unless you add it.
- **Credential handling:** Your av_integration_mtc_api 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 'check if a subscriber is eligible for an advance', and Jentic returns the matching av_integration_mtc_api operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the av_integration_mtc_api use?

The av_integration_mtc_api 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 check if a subscriber is eligible for an advance. with the av_integration_mtc_api?

Yes. Use the GET /canGetAdvance endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the av_integration_mtc_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 this endpoint is used to check if a subscriber is eligible for an advance. 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 check if a subscriber is eligible for an advance.'. Jentic returns the matching av_integration_mtc_api operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the av_integration_mtc_api have?

The av_integration_mtc_api exposes 2 endpoints covering endpoints operations.

### Can I limit what my agent is allowed to do with the AV Integration MTC API?

Yes. The AV Integration MTC API exposes flat operation paths, so in your self-hosted Jentic One instance you decide which operations the agent may call. You can allow only the eligibility check, canGetAdvance, and leave out processAdvance so the agent cannot register or process an advance unless you add that operation. Because Jentic One is self-hosted, your own rules govern which operations and stored credentials the agent is permitted to use.