Location And Travel x402 offerings

Look up the visa requirement for a traveler with a given passport visiting a destination country. Pass passport and destination as ISO-3166 alpha-3, alpha-2, or country name (e.g. passport=USA destination=Japan). Returns the requirement category — 'visa free' (with visaFreeDays, the allowed days), 'visa on arrival', 'e-visa', 'eta' (electronic travel authorization), 'visa required' (must arrange in advance), or 'no admission' — plus a plain-language description and the resolved passport/destination names. Data from the community-maintained Passport Index dataset (MIT). Informational only — not official immigration advice; verify with the destination's embassy before travel.

Look up or search UN/LOCODE — the United Nations Code for Trade and Transport Locations (~116k locations, all countries). Pass `locode` for an exact code (e.g. USNYC or 'US NYC'). Or pass `query` to search location names, optionally filtered by `country` (ISO 3166 alpha-2) and `function` (port, rail, road, airport, postal, multimodal, fixed, border). Each result: locode, name, country, subdivision, transport functions, entry status, IATA code where it differs, and coordinates. UN/LOCODE is the standard location identifier in shipping schedules, EDI messages, and customs documents.

Resolve a postal/ZIP code to its place name(s), administrative divisions, and coordinates. Pass `postalCode` and a 2-letter `country` (default US). Returns each matching locality: place, admin1 (state/province name + code), admin2 (county/district), and lat/lon. International — covers major markets (US, GB, CA, DE, FR, AU, NL, ES, IT, CH, SE, MX). Use it to normalize and enrich addresses, derive the state/county for a ZIP, or geolocate a postal code in an ETL pipeline.

Geolocate a single IPv4 or IPv6 address. Returns country (name + ISO code), region (name + code), city, ZIP, lat/lon, timezone, ISP, organization, and AS number + name. For bulk lookups (up to 100 IPs in one call) use /api/ipinfo/bulk instead. Lat/lon precision is city-level, not GPS.

Resolve a coordinate to its IANA timezone and return the current UTC offset, local wall time, DST status, and short abbreviation. Query: lat (-90..90), lon (-180..180), at (optional ISO 8601 instant; defaults to now). Returns { tz, abbreviation, offsetMinutes, offsetHours, localTime, observesDst, isDst, januaryOffsetMinutes, julyOffsetMinutes, instant, source }. Polygon lookup against a CC0 timezone boundary index; offsets and DST come from the runtime tzdata so transition rules stay current. Use when scheduling for a coordinate, converting timestamps to local wall time, or checking whether a location is currently observing daylight saving.

UK street-level crime around a location from the Home Office data.police.uk service. Give a latitude/longitude (and optional month YYYY-MM, defaults to the latest available — UK data lags ~2 months) and get the total crime count, a breakdown by category (anti-social behaviour, burglary, violent crime, vehicle crime, etc.), and recent individual records (category, approximate street, lat/lon, and outcome status). Free, Open Government Licence (commercial use permitted). Location-risk signal an LLM cannot recall — for property, insurance, and safety agents. Locations are anonymised to nearby map points by the Home Office.

Look up an airport by 3-letter IATA (e.g. SFO) or 4-letter ICAO (e.g. KSFO) code. Query: code (3-5 chars, alphanumeric). Returns { airport: { id, ident, type, name, latitude, longitude, elevationFt, continent, isoCountry, isoRegion, municipality, scheduledService, icaoCode, iataCode, gpsCode, localCode, wikipediaLink } } or 404 NOT_FOUND.

Resolve a US street address to its congressional district (119th Congress), state, and county, via the US Census Bureau geocoder. Returns the matched/normalized address, latitude/longitude, state (name + 2-letter abbreviation), county, and the district number within the state (null for at-large or non-voting delegate districts). The point-in-polygon district lookup is something an agent can't do from a sandbox. Pair it with the gov/congress.* endpoints to find the representatives once you have the state + district. Public domain, keyless.

Live flight status and tracking. Pass ident as an airline flight designator (ICAO "UAL1" or IATA "UA1") or an aircraft tail number; returns recent and upcoming instances of that flight with origin/destination airports (ICAO/IATA/name/city/timezone), status, cancellation/diversion flags, scheduled vs estimated vs actual gate and runway times (out/off/on/in), departure and arrival delays, en-route progress percent, aircraft type and registration, and route distance. limit controls how many instances return (default 5, newest first by scheduled departure). Real-time operational data — answer "where is this flight, is it delayed, when does it land" with live values. For airport metadata see /api/airport/lookup.

Japanese address normalization (住所正規化): standardize a JP address into clean prefecture / city / town / chome-banchi components. Fixes fullwidth/halfwidth digits, old-form kanji, and chome-banchi nota…

Japanese address normalization (住所正規化): standardize a JP address into clean prefecture / city / town / chome-banchi components. Fixes fullwidth/halfwidth digits, old-form kanji, and chome-banchi notation variants, and resolves the 7-digit postal code. Returns a 0-1 confidence score so agents can flag low-quality input. Use for address validation, cleansing, deduplication, and canonicalization before storage or comparison.

Reverse-geocode WGS84 lat/lng coordinates within Japan to a normalized Japanese (JP) address with structured components. Use to label a GPS fix, a map pin, or a photo location with a human-readable a…

Geocode a Japanese (JP) address to WGS84 lat/lng coordinates, with a granularity level (prefecture → city → town → chome → banchi) and a 0-1 confidence score showing how precisely the input resolved. Japan-only. Use for mapping, distance calculation, or delivery routing.

Look up Japanese (JP) address candidates for a 7-digit postal code (郵便番号), backed by the official Japan Post KEN_ALL dataset. One postal code can map to several towns; all candidates are returned with kana readings. Use for address autofill and postal-code validation.

Batch-normalize or batch-geocode up to 100 Japanese (JP) addresses in a single call — same processing as POST /normalize and POST /geocode, with per-item success/error reporting. Dynamic pricing: a s…

Reverse-geocode WGS84 lat/lng coordinates within Japan to a normalized Japanese (JP) address with structured components. Use to label a GPS fix, a map pin, or a photo location with a human-readable address.

Geocode a Japanese (JP) address to WGS84 lat/lng coordinates, with a granularity level (prefecture → city → town → chome → banchi) and a 0-1 confidence score showing how precisely the input resolved.…

Pay-per-request access to FullEnrich, CompanyEnrich, LeadMagic, Exa, Firecrawl, Google Maps, Serper, and Whitepages APIs. No auth, no subscriptions.

Google Maps reviews API for AI agents: send a place_id or a Google Maps place URL and get up to 50 reviews as JSON: stars, text and its translation, date, likes, the owner's reply, plus the place's name, address and rating. Sort by newest, relevant, highest or lowest. Reviewer names, profiles and photos are not returned. A place with no reviews is not charged; reviews you paid for but did not get are refunded.

Google Maps places for a search term, optionally narrowed to an area: {"query":"coffee shops","location":"Prague","limit":5}. Up to 20 places per call. Each place comes back with title, categoryName, address, phone, website, totalScore (rating), reviewsCount, location (lat, lng), openingHours, price, placeId and its Maps url. Common uses are local lead lists, store and competitor mapping, and checking a business's hours or phone number.

Google Maps places for a search term, optionally narrowed to an area: {"query":"coffee shops","location":"Prague","limit":5}. Up to 20 places per call. Each place comes back with title, categoryName,…

Google Maps reviews API for AI agents: send a place_id or a Google Maps place URL and get up to 50 reviews as JSON: stars, text and its translation, date, likes, the owner's reply, plus the place's n…

NSW Development Applications: Find NSW development applications within 2 km of a street address or latitude/longitude, nearest first.

Deutschland auf Bundeslandebene inklusive der Gemeinde-Sonderfälle, Österreich auf Bundeslandebene, die Schweiz auf Kantonsebene. Bewegliche Feste werden aus dem Osterdatum gerechnet, nicht aus einer Tabelle gelesen.