Install Jentic One Beta

Connect the Helipaddy Sites API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Helipaddy Sites API, 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%2Fhelipaddy.com%2Fhelipaddy" | 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%2Fhelipaddy.com%2Fhelipaddy" | 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 Helipaddy Sites API.

Authenticate and obtain a bearer token via POST /auth/login

Handle the OAuth callback for an interactive login via GET /auth/callback

List landing sites in the Helipaddy directory via GET /sites

Find the landing sites nearest to a given coordinate via GET /sites/nearest

Retrieve a single site's details by id via GET /sites/{id}

GET STARTED

Start building with Helipaddy Sites API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Helipaddy Sites API for, with concrete tasks.

★ Pilot Pre-Flight Site Lookup

A pilot's flight-planning app surfaces nearby landing sites along the planned route. The /sites/nearest endpoint accepts coordinates and returns the closest pads, while /sites/{id} provides full operational details such as contact info and surface type. The pilot does not need to maintain a landing-site database in-app.

Call GET /sites/nearest?lat=51.5&lon=-0.12 and return the five closest landing sites with their contact details

Charter Operator Quote Tooling

A helicopter charter operator builds quotes by selecting origin and destination landing sites. The app calls /sites with region filters to populate dropdowns, then /sites/{id} for the chosen pad to confirm operating hours and PPR (prior permission required) status.

List sites with GET /sites filtered to a region, then call GET /sites/{id} on the selected destination to confirm PPR and contact

Drone Operations Site Selection

A passenger-drone operator screens potential vertiport locations by checking nearby existing landing sites for clustering and accessibility. The /sites/nearest endpoint returns sites within a configurable radius so the operator can score candidate locations.

Call GET /sites/nearest?lat=...&lon=... for each candidate vertiport coordinate and tally the count of existing sites within 5 km

AI Agent Aviation Concierge

An aviation concierge agent answers 'find me the nearest helipad to Battersea with PPR contact details'. Through Jentic, the agent searches by intent, loads /sites/nearest and /sites/{id}, and chains them - without ever seeing the bearer token.

Search Jentic for 'find nearest helipad', load GET /sites/nearest, and chain to GET /sites/{id} on the top result to return PPR contact

Key Endpoints

6 endpoints — jentic publishes the only available openapi specification for helipaddy sites api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/auth/login

Authenticate and receive a bearer token

GET

/sites

List landing sites in the directory

GET

/sites/nearest

Find the landing sites nearest to a coordinate

GET

/sites/{id}

Retrieve a single site's details

GET

/usage

Get API usage statistics for the client

POST

/auth/login

Authenticate and receive a bearer token

GET

/sites

List landing sites in the directory

GET

/sites/nearest

Find the landing sites nearest to a coordinate

GET

/sites/{id}

Retrieve a single site's details

GET

/usage

Get API usage statistics for the client

Why Jentic?

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

Setup

Wiring Helipaddy by hand means posting to /auth/login to obtain a bearer token, then attaching the Authorization header on every directory lookup. Through Jentic you install once, import the Helipaddy Sites API from the API Directory, store the login credentials once, and your agent calls it.

Permission scoping

Helipaddy puts the site id in the URL path (/sites/{id}) alongside read-only lookups like /sites and /sites/nearest, so a rule can pin your agent to reading one site or nearby sites and nothing else. The API is read-only, and you choose the operations it may call, so anything beyond those lookups is not included unless you add it.

Credential isolation

Your Helipaddy login credentials and the issued bearer token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'find the nearest helipad' or 'look up a landing site by id', and Jentic returns the matching Helipaddy operation with its input schema, including the lat/lon and id parameters, so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Helipaddy Sites API through Jentic.

Why is there no official OpenAPI spec for Helipaddy Sites API?

Helipaddy documents the API on helipaddy.com/api but does not distribute a maintained OpenAPI file. Jentic generates and maintains this spec so AI agents and developers can call Helipaddy via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Helipaddy Sites API use?

Helipaddy uses bearer-token auth. POST /auth/login exchanges credentials for a bearer token sent on subsequent /sites and /usage requests. Through Jentic, the credentials and token live in the encrypted vault.

Can I find the nearest helipad to a given coordinate?

Yes. GET /sites/nearest accepts lat and lon parameters and returns the closest landing sites, ordered by distance, so an agent can power a 'nearest helipad' lookup with a single call.

What are the rate limits for the Helipaddy Sites API?

The OpenAPI spec does not publish hard rate limits; Helipaddy applies plan-level fair use. GET /usage returns the current period's usage, so agents can check headroom before running a bulk job.

How do I look up a specific landing site through Jentic?

Run pip install jentic, have the agent search for 'find a helicopter landing site', load GET /sites/{id}, and execute it with the site id returned by /sites or /sites/nearest.

Does Helipaddy include passenger-drone vertiports as well as traditional helipads?

Yes. The Helipaddy directory covers helicopter sites and passenger-drone landing sites in a single catalog, so /sites and /sites/nearest queries return both site types where the data exists.

Can I limit what my agent is allowed to do with the Helipaddy Sites API?

Yes. Because you run Jentic One yourself, your own rules decide which Helipaddy operations and credentials the agent may use. The Helipaddy Sites API is read-only, so you can pin the agent to lookups such as GET /sites, GET /sites/nearest, and GET /sites/{id} by site id, and leave out anything you have not allowed. Since the site id sits in the URL path, you can scope the agent to reading one site or nearby sites and nothing else.

Helipaddy Sites API

Name: Helipaddy Sites API
Brand: Helipaddy Sites API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticMaps GeolocationPlaces Searchbearer6 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Find helicopter and passenger-drone landing sites by location or proximity across 6 endpoints, with bearer-token auth.

Use for: Get a Helipaddy bearer token using my credentials, List all helicopter landing sites in a region, Find the closest landing pads to a given lat/lon, Retrieve full details for a specific Helipaddy site

Not supported: Does not handle flight planning, weather, NOTAMs, slot booking, or air traffic control - use for landing-site directory lookups and proximity searches only.

Jentic publishes the only available OpenAPI specification for Helipaddy Sites API, keeping it validated and agent-ready. Helipaddy maintains a directory of helicopter and passenger-drone landing sites with location, contact, and operational details. The Sites API lets pilots, operators, and aviation apps look up sites by id, list sites in a region, and find the nearest landing pads to a given coordinate. Authentication is by bearer token issued via the auth/login endpoint, with usage statistics available on /usage.

Jentic One on Github View OpenAPI Document