Jsivori Aero Paquetes
Browse all Swaggerhub Jsivori APIsCommunity OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey8 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically búqueda de salidas con parámetros puntuales opcionales., búqueda puntual de una salida por identificador único.. Covers 8 operations with apiKey authentication.
Use for: I need to búqueda de salidas con parámetros puntuales opcionales., I want to búqueda puntual de una salida por identificador único., Search for consulta de disponibilidad de una salida., Find all alternativas a una salida puntual.
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Aero-Packs es la aplicacion donde Aero S.R.L ofrece todos sus servicios en un único servicio integral. Este documento debe utilizarse como referencia para utilizar la API de AeroPaquetes. Se necesitan credenciales de acceso para el uso de la misma. The API exposes 8 endpoints secured with apiKey authentication.
Install Jentic One Beta
Connect the Aero Paquetes to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Aero Paquetes, 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.
1
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%2Fswaggerhub.jsivori%2Faero-paquetes" | sh2
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%2Fswaggerhub.jsivori%2Faero-paquetes" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Aero Paquetes API.
Búqueda de salidas con parámetros puntuales opcionales.
Consulta de disponibilidad de una salida.
Alternativas a una salida puntual.
Preliquidacion de la salida puntual.
Genera una reserva.
Use Cases
Patterns agents use Aero Paquetes API for, with concrete tasks.
★ Developer Tools Operations
Use the Aero Paquetes to perform developer tools operations programmatically. The API provides 8 endpoints covering core functionality including búqueda de salidas con parámetros puntuales opcionales., búqueda puntual de una salida por identificador único., consulta de disponibilidad de una salida..
Call POST /api/packages/find_with_params to búqueda de salidas con parámetros puntuales opcionales.
Automated Packages Management
Automate packages operations by combining multiple Aero Paquetes endpoints. Agents can búqueda puntual de una salida por identificador único. and then consulta de disponibilidad de una salida. in a single workflow.
Call GET /api/packages/{id} to búqueda puntual de una salida por identificador único., then verify the result
AI Agent Integration via Jentic
AI agents discover and call Aero Paquetes 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 'búqueda de salidas con parámetros puntuales opcionales.', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
8 endpoints — aero-packs es la aplicacion donde aero s.
METHOD
PATH
DESCRIPTION
POST
/api/packages/find_with_params
Búqueda de salidas con parámetros puntuales opcionales.
GET
/api/packages/{id}
Búqueda puntual de una salida por identificador único.
GET
/api/packages/{id}/availability
Consulta de disponibilidad de una salida.
GET
/api/packages/{id}/other_bases
Alternativas a una salida puntual.
GET
/api/packages/{id}/other_options
Alternativas a una salida puntual.
GET
/api/packages/{id}/get_price_info
Preliquidacion de la salida puntual.
POST
/api/packages/{id}/reserve
Genera una reserva.
GET
/api/packages/reserve_to_cancel
Cancelar una reserva.
POST
/api/packages/find_with_params
Búqueda de salidas con parámetros puntuales opcionales.
GET
/api/packages/{id}
Búqueda puntual de una salida por identificador único.
GET
/api/packages/{id}/availability
Consulta de disponibilidad de una salida.
GET
/api/packages/{id}/other_bases
Alternativas a una salida puntual.
GET
/api/packages/{id}/other_options
Alternativas a una salida puntual.
GET
/api/packages/{id}/get_price_info
Preliquidacion de la salida puntual.
POST
/api/packages/{id}/reserve
Genera una reserva.
GET
/api/packages/reserve_to_cancel
Cancelar una reserva.
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Aero Paquetes by hand means passing its API key in the Authorization header, pointing at the staging host, and writing your own request and retry handling around the package search and reserve calls. Through Jentic you install once, import Aero Paquetes from the API Directory, store the API key once, and your agent calls it.
Permission scoping
This API puts the package id in the URL path (/api/packages/{id}, /api/packages/{id}/availability), so a rule can pin your agent to one package and the operations around it. You choose the operations it may call, so writes like reserving a package are not included unless you add them.
Credential isolation
Your Aero Paquetes API 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 'find travel packages by parameters' or 'check package availability', and Jentic returns the matching Aero Paquetes operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using Aero Paquetes API through Jentic.
What authentication does the Aero Paquetes use?
The Aero Paquetes uses an API key passed in the `Authorization` 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 búqueda de salidas con parámetros puntuales opcionales. with the Aero Paquetes?
Yes. Use the POST /api/packages/find_with_params endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Aero Paquetes?
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 búqueda de salidas con parámetros puntuales opcionales. through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'búqueda de salidas con parámetros puntuales opcionales.'. Jentic returns the matching Aero Paquetes operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Aero Paquetes have?
The Aero Paquetes exposes 8 endpoints covering packages operations.
Can I limit what my agent is allowed to do with the Aero Paquetes API?
Yes. Because you run Jentic One yourself, your own rules decide which Aero Paquetes operations the agent may call and which credentials it may use. Since the package id sits in the URL path, such as /api/packages/{id} and /api/packages/{id}/availability, you can pin the agent to a single package and the read operations around it. You control whether writes like POST /api/packages/{id}/reserve or the cancel call are included, so the agent cannot reserve or cancel unless you allow it.
GET STARTED