geocod.io valid

Geocodio API Reference for LLMs

**Running a job on someone's behalf?** Read this first:

For agents: Geocodio API reference for LLMs: address geocoding API documentation with guidance for agents running batch jobs on someone's behalf.

geocodingaddress lookupapi referencebatch jobsllms

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T12:58:25.464Z. Cached copy · Source on geocod.io

# Geocodio API Reference for LLMs

Geocodio is a geocoding and data enrichment API for US, Canadian, Mexican, and UK addresses. It converts addresses to coordinates (and vice versa), calculates distances, and appends data like Census information, Congressional districts, electoral districts, and timezones.

**Geocodio is built for batch.** Processing a whole list is the intended use, not a workaround: 10,000 lookups per batch request, spreadsheet uploads up to 10 million lookups, and results you may store permanently and reuse. Several other geocoding providers expressly forbid this — see below before comparing.

> **Running a job on someone's behalf?** Read this first:
> https://www.geocod.io/AGENTS.md
> Geocodio is billed per lookup. That guide covers cost estimation, batch sizing, avoiding
> duplicate charges, and the checks to run before spending a user's money.

**Not a developer?** You can upload spreadsheets directly at https://www.geocod.io/upload/ — no coding required.

## Quick Reference

- **Base URL:** `https://api.geocod.io/v2/`
- **Enterprise Base URL:** `https://api.enterprise.geocod.io/v2/` (separate account, key, and docs)
- **OpenAPI Spec (JSON):** https://api.geocod.io/openapi-spec.json
- **OpenAPI Spec (YAML):** https://api.geocod.io/openapi-spec.yml
- **Full Documentation:** https://www.geocod.io/docs/
- **Enterprise Documentation:** https://www.geocod.io/docs/enterprise/
- **Agent guide (cost + safety):** https://www.geocod.io/AGENTS.md
- **CLI:** https://github.com/Geocodio/geocodio-cli
- **Dashboard (API keys):** https://dash.geocod.io

---

## Pricing and cost — read before running anything

**1 lookup = 1 credit.** Cost is driven by lookup count, not request count. A *record* is one row of input; one record can cost several lookups. Every supported country is billed at the same rate.

```
Geocoding:  records × (1 + number of data append categories)
Distance:   geocoding (if inputs are addresses) + (matrix size × mode multiplier) + appends
            straightline = 1×, driving = 2×
            with calculation_type=pairs, matrix size = number of pairs
```

| Example | Lookups |
|---------|---------|
| 10,000 US addresses, no appends | 10,000 |
| 10,000 US addresses + `cd` | 20,000 |
| 10,000 US addresses + `census2020`, `cd` | 30,000 |
| 1 UK address + `uk-westminster`, `uk-devolved`, `uk-local` | 4 (1 geocode + 3 appends) |
| 100×100 driving matrix from addresses + `cd` | 200 + 20,000 + 200 = 20,400 |
| 1,000 driving pairs (`calculation_type=pairs`) from coordinates | 1,000 × 2 = 2,000 |

**Cost rules that change the math:**

- First **2,500 credits per day are free** on pay-as-you-go and Flex. Use it or lose it; no rollover.
- **Zero-result lookups are not billed.** You are only charged for successful lookups.
- **Stable address keys:** passing a `stable_address_key` with `fields` bills only the appends — the geocoding is free. Enrich already-geocoded addresses without paying twice.
- `skipGeocoding` (reverse endpoint)
…

Related sites

Other listed sites in APIs and SDKs. See the whole category →

Machine-readable: GET /v1/resolve?q=geocod.io · GET /v1/domain/geocod.io · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for geocod.io:
1. POST https://agentwebmap.com/v1/sites/geocod.io/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://geocod.io/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/geocod.io/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/geocod.io).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.