--- name: agentgate-x402.netlify.app description: agentgate-x402.netlify.app provides three static lookup utilities: two for aviation data (airport metadata and route distance/flight time between airports) and one for DNS record resolution. All three are single-shot, synchronous lookups with no real-time or streaming components. host: agentgate-x402.netlify.app --- # agentgate-x402.netlify.app This host serves agents that need structured reference data for airports or domain DNS configurations. The aviation skills cover a global database of 49,000+ airports, supporting code-to-metadata resolution and great-circle distance calculations between any two airports. The DNS skill resolves a domain's full record set including mail and SPF configuration. There is no overlap between the aviation and DNS capabilities; they are independent utilities bundled on the same host. ## When to use this host Use this host when an agent needs to resolve an IATA or ICAO airport code to structured metadata, calculate distance or estimated flight time between two airports, or inspect a domain's DNS records including SPF and mail configuration. Do not use it for real-time flight tracking, live departure or arrival status, fare pricing, or flight booking — use a dedicated flight status or GDS API instead. Do not use it for reverse DNS (PTR) lookups or continuous DNS monitoring. Do not use it to search airports by city name or partial name; a valid IATA or ICAO code is required as input. The DNS skill is unrelated to the aviation skills and should be selected independently based on the task at hand. ## Capabilities ### Airport Reference Data Resolves airport codes to full metadata including coordinates, elevation, country, region, and service flags, covering IATA and ICAO codes across 49,000+ airports worldwide. - **`lookup-airport-by-code`** — Returns structured airport metadata (name, coordinates, elevation, country, region, municipality, size class, scheduled-service flag) for a given IATA or ICAO code, covering 49,000+ airports worldwide. ### Airport Route Calculation Computes great-circle distance in km, nautical miles, and statute miles plus estimated block flight time between two airports identified by IATA or ICAO code. - **`fetch-airport-route-distance`** — Returns great-circle distance in km, nautical miles, and statute miles plus estimated block flight time between any two of 49,000+ airports identified by IATA or ICAO code. ### DNS Record Lookup Performs a single-shot DNS resolution for a domain, returning A, AAAA, CNAME, MX, NS, and TXT records with TTLs plus a structured summary of mail setup, SPF policy, and site-verification tokens. - **`fetch-dns-records`** — Resolves a domain name and returns its A, AAAA, CNAME, MX, NS, and TXT records with TTLs, plus a summary of resolution status, mail configuration, SPF policy, and site-verification tokens. ## Workflows ### Airport Code Validation Then Distance *Use when an agent needs to verify that both airport codes are valid and retrieve their metadata before computing the route distance between them.* 1. **`lookup-airport-by-code`** — Resolve the origin airport code to confirm it exists and retrieve its name and coordinates. 2. **`lookup-airport-by-code`** — Resolve the destination airport code to confirm it exists and retrieve its name and coordinates. 3. **`fetch-airport-route-distance`** — Compute the great-circle distance and estimated flight time between the two validated airport codes. ## Skill reference ### `lookup-airport-by-code` **Airport Lookup API** — Returns structured airport metadata (name, coordinates, elevation, country, region, municipality, size class, scheduled-service flag) for a given IATA or ICAO code, covering 49,000+ airports worldwide. *Use when:* Use when an agent needs to resolve an airport code (IATA or ICAO) to its full metadata including geographic coordinates, country, region, municipality, elevation, airport type, and whether scheduled commercial service operates there. *Not for:* Do not use for flight search, route planning, or real-time flight status — this is a static airport record lookup only. Not suitable for resolving city names or partial airport names; a code is required. **Inputs:** - `code` (string, required) — 3-letter IATA or 4-letter ICAO airport code. Must match pattern ^[A-Za-z0-9]{3,4}$. **Returns:** Returns a single JSON object with ICAO/IATA codes, full airport name, lat/lon, elevationFt, ISO country and region codes, municipality, size type, and scheduledService boolean. **Example:** `GET https://agentgate-x402.netlify.app/api/airport?code=DXB` --- ### `fetch-airport-route-distance` **Airport Route Distance & Flight Time** — Returns great-circle distance in km, nautical miles, and statute miles plus estimated block flight time between any two of 49,000+ airports identified by IATA or ICAO code. *Use when:* Use when an agent needs the distance or estimated flight duration between two airports given their IATA or ICAO codes, such as for itinerary planning, logistics routing, or aviation data lookups. *Not for:* Do not use for real-time flight tracking, live departure/arrival data, or fare pricing; use a flight status or booking API instead. **Inputs:** - `from` (string, required) — Origin airport IATA or ICAO code (3–4 alphanumeric characters). - `to` (string, required) — Destination airport IATA or ICAO code (3–4 alphanumeric characters). **Returns:** Returns origin and destination airport metadata objects, distance in km/nm/mi, and estimated flight time as decimal hours and a formatted string (e.g. 7h 06m). **Example:** `GET https://agentgate-x402.netlify.app/api/route?from=JFK&to=LHR` --- ### `fetch-dns-records` **DNS Lookup API** — Resolves a domain name and returns its A, AAAA, CNAME, MX, NS, and TXT records with TTLs, plus a summary of resolution status, mail configuration, SPF policy, and site-verification tokens. *Use when:* Use when an agent needs to inspect a domain's DNS configuration, verify mail server setup, retrieve SPF policy strings, or collect third-party site-verification tokens for a given domain name. *Not for:* Do not use for real-time DNS monitoring or streaming record changes; this is a single-shot lookup. Not suitable for reverse DNS (PTR) lookups. **Inputs:** - `domain` (string, required) — Domain name to inspect. Must be at least 4 characters. **Returns:** Returns the queried domain, a records object with A/AAAA/CNAME/MX/NS/TXT arrays (each entry has name, ttl, value), and a summary with resolves, hasMx, spf string, and verifications array. **Example:** `GET https://agentgate-x402.netlify.app/api/dns?domain=openai.com` ---