canonical: https://jentic.com/apis/swaggerhub.deepakcse2k5-2/swaggerhub-deepakcse2k5-2

# Deepakcse2k5 2 airline

This is the help center of Vogal Airline. Use the following conversation as a reference to reply to the user query going forward. \nUser- Hi. \nAssistant- Welcome to Vogal Airline, how may i help you. User- I would like to search_flight or book_flight Assistant- Sure, I can help you with that but first can you please provide your mobile number for validation so that i can check your registration s. The API exposes 8 endpoints.

## For AI agents

Programmatically check_registered, search_flight. Covers 8 operations.

## Scope

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

## Capabilities

- check_registered
- search_flight
- Book a flight
- Make a payment for a flight booking
- Get flight information
- Check in for a flight

## Use cases

### Communications Operations

Use the airline to perform communications operations programmatically. The API provides 8 endpoints covering core functionality including check_registered, search_flight, book a flight.

Example prompt: Call GET /CheckRegistered to check_registered

### Automated Bookflight Management

Automate bookflight operations by combining multiple airline endpoints. Agents can search_flight and then book a flight in a single workflow.

Example prompt: Call GET /SearchFlight to search_flight, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call airline 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 'check_registered', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /CheckRegistered | check_registered |
| GET | /SearchFlight | search_flight |
| POST | /BookFlight | Book a flight |
| POST | /MakePayment | Make a payment for a flight booking |
| GET | /FlightInformation | Get flight information |
| POST | /CheckInFlight | Check in for a flight |
| POST | /BookMeal | Book a meal for a flight |
| GET | /SearchPNR | Search for PNR status |

## Key resources

- **Bookflight** — Operations for BookFlight
- **Bookmeal** — Operations for BookMeal
- **Checkinflight** — Operations for CheckInFlight
- **Checkregistered** — Operations for CheckRegistered
- **Flightinformation** — Operations for FlightInformation

## Why Jentic

- **Setup:** Wiring the airline API by hand means resolving its SwaggerHub host, shaping the search, booking, check-in, and PNR calls, and handling retries yourself, even though it takes no auth. Through Jentic you install once, import the airline API from the API Directory, and your agent calls it with no credential to store.
- **Permission scoping:** This API uses flat action paths rather than per-resource ids, so scope by operation: limit the agent to what it needs, such as searching flights and looking up a PNR, and leave out booking a flight or making a payment unless you add them.
- **Credential handling:** This API needs no credentials, so there is nothing for the agent to hold. If a call ever required a secret, your own Jentic One instance would store it once, encrypted, and inject it at execution time so it never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'search for a flight' or 'look up a PNR', and Jentic returns the matching airline operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the airline use?

The airline 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 check_registered with the airline?

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

### What are the rate limits for the airline?

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 check_registered through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'check_registered'. Jentic returns the matching airline operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the airline have?

The airline exposes 8 endpoints covering bookflight, bookmeal, checkinflight operations.

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

Yes. Because you run Jentic One yourself and this API uses flat action paths rather than per-resource ids, you scope the agent by operation: your own rules decide which endpoints it may call. You can allow read-only actions such as searching flights and looking up a PNR while leaving out booking a flight, making a payment, or checking in unless you explicitly add them. The agent can only invoke the operations you have granted, so it cannot take a booking or payment action you did not authorize.