Install Jentic One Beta

Connect the Airports API v2 to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Airports API v2, 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.

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%2Ftransavia.com%2Fairports-api-v2" | sh

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%2Ftransavia.com%2Fairports-api-v2" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Airports API v2 API.

All airports

Airport(s) by country code.

Nearest airport(s) by geo coordinates.

Airport by id.

Monitor Airports API v2 operational status and events

GET STARTED

Start building with Airports API v2 API

Explore with Jentic One

View OpenAPI Document

Automated countrycode Management

Automate countrycode operations by combining multiple Airports API v2 endpoints. Agents can airport(s) by country code. and then nearest airport(s) by geo coordinates. in a single workflow.

Call GET /countrycode/{countryCode} to airport(s) by country code., then verify the result

AI Agent Integration via Jentic

AI agents discover and call Airports API v2 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 apiKey tokens manually.

Search Jentic for 'all airports', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

5 endpoints — returns all airports.

METHOD

PATH

DESCRIPTION

GET

All airports

GET

/countrycode/{countryCode}

Airport(s) by country code.

GET

/nearest

Nearest airport(s) by geo coordinates.

GET

/nearest/{id}

Nearest airport(s) by airport id.

GET

/{id}

Airport by id.

GET

All airports

GET

/countrycode/{countryCode}

Airport(s) by country code.

GET

/nearest

Nearest airport(s) by geo coordinates.

GET

/nearest/{id}

Nearest airport(s) by airport id.

GET

/{id}

Airport by id.

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Airports API v2 by hand means passing its apikey header or subscription-key query parameter on every call to api.transavia.com and handling errors yourself. Through Jentic you install once, import the Airports API v2 from the API Directory, store the API key once, and your agent calls it.

Permission scoping

The Airports API v2 is read-only, so scope the agent to the operations it needs, such as listing airports, looking up by country code, or finding the nearest airport, and leave out anything the workflow does not require. Every operation you allow is one you have chosen.

Credential isolation

Your Airports API v2 key 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 'list all airports' or 'find the nearest airport', and Jentic returns the matching Airports API v2 operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Airports API v2 API through Jentic.

What authentication does the Airports API v2 use?

The Airports API v2 uses an API key passed in the `apikey` 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 all airports with the Airports API v2?

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

What are the rate limits for the Airports API v2?

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 all airports through Jentic?

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

How many endpoints does the Airports API v2 have?

The Airports API v2 exposes 5 endpoints covering countrycode, default, nearest operations.

Can I limit what my agent is allowed to do with the Airports API v2?

Yes. Because you run Jentic One self-hosted, your own rules decide which Airports API v2 operations and which stored API key the agent may use. The API is read-only, so you can allow just the calls a workflow needs, such as listing all airports or looking up airports by country code, while withholding nearest-airport lookups by coordinates or by id. Every operation the agent can reach is one you have explicitly permitted.

Transavia Airports API v2

Name: Airports API v2 API
Brand: Airports API v2
Availability: InStock

Browse all Transavia APIs

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey5 EndpointsREST

For Agents

Programmatically all airports, airport(s) by country code.. Covers 5 operations with apiKey authentication.

Use for: I need to all airports, I want to airport(s) by country code., Search for nearest airport(s) by geo coordinates., Find all nearest airport(s) by airport id.

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

Returns all airports. The API exposes 5 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Connect the Airports API v2 to your agent

Capabilities

Start building with Airports API v2 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Transavia Airports API v2