Geocode individual and batch addresses to coordinates, reverse geocode coordinate pairs to addresses, and append data fields like congressional districts, census tracts, school districts, timezones, and ACS demographics to results. The API supports single and batch requests (up to 10,000 addresses per batch), spreadsheet-based list processing with job management, a distance calculation feature for measuring driving or straight-line distance between geocoded results and destination points, and US/Canada-specific address parsing across 16 endpoints.
16 endpointsGeocodio is a US- and Canada-focused geocoding API that converts addresses to coordinates and back, with optional data appending for congressional districts, census blocks, school districts, timezones, and more. The spec covers single forward and reverse lookups, batch processing for large lists, spreadsheet uploads with managed list status, and a distance/route-matrix endpoint. It is widely used by US-centric civic-tech and analytics platforms because of its accuracy on US street data and its append fields for political geographies.
11 endpointsStep 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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.