Geocodio
by Dotsquare LLC HTTP API in Maps, geocoding & places
Agent-ready
Dotsquare LLC · geocod.io since 2013 · status page · who's behind it
Geocodio is a hosted geocoding API from Dotsquare LLC for addresses in the US, Canada, Mexico, the UK, Australia and New Zealand. It does forward, reverse and batch geocoding, distance matrices and census, district and timezone data appends.
Best for Batch geocoding and district or census enrichment of addresses in the US, Canada, Mexico, the UK, Australia and New Zealand, where results must be stored.
Viewed under 500 times in the last 30 days · Claim it, free, to see who finds it
Is this your product? Claim it to see how agents find it: lookups through the API, MCP and letme, the comparisons it's in, and what people search for in Maps. Free, and it never changes the grade. Or verify it, or log in if it's already claimed.
Assessment. Geocodio publishes llms.txt, an AGENTS.md on cost and retries, an OpenAPI spec and a dated changelog, and its results may be stored permanently. Coverage stops at six countries, there's no MCP server or published SLA for self-serve plans, and the docs still put the key in the query string by default.
Facts
Access how an agent reaches and pays for it
- Transport
- HTTP
- Auth
- API key
- Pricing
- Freemium · $1 / 1k req
- x402
- No
- Licence
- not stated
- Capabilities
- geo.geocode geo.reverse geo.routing
Where it lives packages, source, docs and releases
- Packages
pypigeocodio-library-pythonnpmgeocodio-library-node- llms.txt
- published
- Last release
- npm / week
- 21k
- PyPI / week
- 921
From our research 10 facts checked against the vendor's pages
- Surface listed
- The REST API at api.geocod.io/v2.1, read from www.geocod.io/docs, llms.txt, AGENTS.md, the OpenAPI spec, the pricing, terms, privacy and security pages, status.geocod.io and the Geocodio GitHub repositories on 6 November 2026. No account was made and no key was used
- Coverage
- Forward and reverse geocoding and distance for the US, Canada, Mexico, the UK, Australia and New Zealand. No other countries
- Endpoints
- /geocode and /reverse (single GET or batch POST up to 10,000 lookups), /parse, /distance, /distance-matrix (10,000 calculations), /distance-jobs (50,000), /lists for spreadsheets up to 10 million lookups, and a Google Maps compatible /maps/api/geocode/json
- Data appends
- Congressional and state legislative districts with legislators, census geographies and ACS data, school districts, ZIP+4, FFIEC, Canadian ridings, UK constituencies and census, Australian census and electorates, and timezone, each billed as one more lookup
- Rate limits
- 1,000 requests a minute on single GET /geocode and /reverse on pay-as-you-go and Flex, 100 a minute on Enterprise Flex. Batch and lists aren't limited by these numbers. 429 with X-RateLimit headers
- Errors
- 403 bad key, missing permission or daily limit reached, 422 bad input, 429 rate limited, 500 server error, with a retry rule for each in llms.txt
- Data retention
- API and spreadsheet input and results deleted within 45 days, Lists API data after 72 hours, error logs 90 days. The privacy policy says customer data isn't used to train AI models
- Hosting
- Self-serve is hosted in Europe. Enterprise runs on separate infrastructure with SOC 2 Type II, HIPAA, SAML SSO, US hosting and on-premises options
- SDKs
- Python 1.6.0 (12 October 2026), Node 2.3.0 (12 October 2026), PHP 3.4.1 (4 November 2026) and a Ruby gem, plus a Go CLI, all MIT
- Legal entity
- Dotsquare LLC, dba Geocodio, Norfolk, Virginia, under Virginia law
Facts verified 6 November 2026 from vendor docs, repositories and package registries. JSON · Markdown
Strengths
- llms.txt and AGENTS.md cover billing arithmetic, retry rules, idempotency on the client and when not to use the API
- 2,500 free lookups a day with no card, then $1 per 1,000, and zero-result lookups aren't billed
- Results may be stored and reused permanently, except UK reverse geocoding addresses
- Dated API changelog with versioned paths, and replaced versions kept for at least 12 months
- Official Python, Node, PHP and Ruby libraries and a CLI with an agent output mode, all MIT
Weaknesses
- Covers only the US, Canada, Mexico, the UK, Australia and New Zealand, and UK needs a Flex or Unlimited plan
- The docs lead with the api_key query parameter, and the OpenAPI spec defines only that scheme
- No idempotency key on batch or list creation, so a retried upload is billed again
- No MCP server, and no published SLA on self-serve plans
- SOC 2 Type II and penetration tests apply to the separate Enterprise platform only
Before you call it notes for agents
- Always set
country, because an address with none falls back to the US and is billed even when it's wrong - Send the key as
Authorization: Bearer, not in the query string, so it stays out of logs - Use batch POST /geocode (up to 10,000 lookups) or the Lists API rather than looping single requests
- Treat accuracy_type place, county or state as not found, and check
_warningsfor appends that were billed but skipped - Don't retry 403 or 422. On 429 read X-RateLimit headers and back off, and never re-upload a list sitting in ENQUEUED
Who's behind it provenance 93/100
- Legal entity namedDotsquare LLC20/20
- Domain agegeocod.io, registered 2013-06-05 (13 years)15/15
- Endpoint on the vendor's domaingeocod.io15/15
- Terms of serviceread, states 6 of the 7 things a reader expects, and has 3 clauses that cost points3.1/10
- Privacy policyread, states 8 of the 8 things a reader expects10/10
- Status pagestatus.geocod.io10/10
- Changelogpublished10/10
- security.txtvalid10/10
- People named2 named with their role, none with a public profile7/10
- Support routea support address, help pages5/5
Terms and privacy, as read
Terms of service gives no date, states 6 of 7, 3 to know
TL;DR Gives no date. States 6 of the 7 things a reader expects. To know before relying on it, limits on automated access, limits on benchmarking and changes without notice.
Restricts automated accesscosts points
(v) engage in web scraping or data scraping on or related to the System, including without limitation collection of information through any software that simulates human activity or any bot or web crawler;
A rule against bots, scrapers or automated means can cover an agent, depending on how the vendor reads it.
Restricts benchmarking or competitive usecosts points
(iv) access the System in order to build a competitive product or service, to build a product using similar ideas, features, functions or graphics of the System, or to copy any ideas, features, functions or graphics of the System;
A clause against publishing test results or using the service to build something that competes.
Says the terms or the service can change without noticecosts points
Company reserves the right to update, change, and remove Plan features at any time with or without advance notice.
A customer may not hear about a change before it applies.
Gives the date it was last updated
Not found in the text.
Without a date nobody can tell which version they agreed to.
Names the governing law or courts The law of the Commonwealth of Virginia
This Agreement and any claims arising will be governed solely by the internal laws of the Commonwealth of Virginia, including without limitation applicable federal law, without reference to any conflicts of laws principles.
Says where a dispute would be heard and under whose law.
States a limit on its liability Capped at the fees paid in the 12 months before the claim
COMPANY’S CUMULATIVE LIABILITY FOR ALL CLAIMS ARISING OUT OF OR RELATED TO THIS AGREEMENT SHALL NOT EXCEED THE AGGREGATE AMOUNT OF FEES FOR SERVICES DELIVERED BY COMPANY ACTUALLY PAID BY CUSTOMER PURSUANT TO THIS AGREEMENT DURING THE TWELVE (12) MONTHS PRIOR TO THE ASSERTION OR INSTITUTION OF SUCH CLAIM.
Says the most the vendor would owe if the service causes a loss.
Says how the agreement or account can be ended
Either party may terminate this Agreement based on the other’s material breach by providing written notice specifying in detail the nature of the breach, and such termination shall be effective (a) after thirty (30) days unless the other party cures such breach, or (b) immediately in the event of non-payment or misuse…
Says when the vendor can cut off access and what notice it gives.
Says how changes to the terms are announced Says it gives notice of a change
Company may amend this Agreement under Section 12.1 (Amendments) and will notify the Covered Customer of the amendment, which takes effect as provided in that Section.
Says whether a customer hears about a change before it binds them.
Lists what users may not do
Except as otherwise provided in this Agreement, Customer will not be entitled to any refund, credit, or reimbursement for: (i) partial use of the Services;
The acceptable-use rules an agent acting for a user has to stay inside.
Refers to a service level or uptime commitment
(c) any addenda, schedules, or exhibits to this Agreement (including the Plan Terms Schedule, SLA Addendum, Enterprise Addendum, Australia Addendum, New Zealand Addendum, Business Associate Agreement, Data Processing Agreement, and any UK Data Services Attachment), each solely with respect to its subject matter;
Says whether availability is promised and where the promise is written.
The document · read 2026-11-06 · 12,714 words
Privacy policy dated 2018-05-25, states 8 of 8, 2 to know
TL;DR Dated 2018-05-25. States all 8 things a reader expects. To know before relying on it, selling or sharing data for advertising and no update in three years.
Says it sells personal data or shares it for advertising
We also share our users’ email addresses, and no other personal information, with LinkedIn for advertising, and LinkedIn may store and process them in the United States and other countries.
Personal data is passed to advertising partners, or the document says its sharing may count as a sale under privacy law.
Has not been updated for three years or more
General Data Protection Regulation (GDPR) - European Union legislation effective May 25, 2018
The date the document gives for itself is more than three years ago.
Gives the date it was last updated Last updated 2018-05-25
General Data Protection Regulation (GDPR) - European Union legislation effective May 25, 2018
Without a date nobody can tell which version applied when data was collected.
Says what personal data is collected
Right to Know - Request information about what personal data we collect, use, and share
The basic statement a privacy policy exists to make.
Says how long data is kept Names a period of 45 days
Spreadsheet/API Data: Input data you send to us for processing (such as addresses and coordinates), whether through the API or a spreadsheet upload, and the results are deleted within 45 days.
Says when data sent to the service is deleted.
Says who else receives the data
Customers with a signed Data Processing Agreement: this list is the canonical sub-processor list referenced in our DPA.
Names the sub-processors or service providers the data is passed to, or where they are listed.
Says whether personal data is sold or shared for advertising Says it does not sell personal data
We do not sell your personal information, and we do not provide it to LinkedIn for any purpose other than showing and measuring Geocodio ads.
A plain statement either way.
Says what rights people have over their data
Right to Know - Request information about what personal data we collect, use, and share
Access, correction, deletion and objection, and how to use them.
Gives a privacy contact Names a data protection officer
Data Protection Officer: Available for EU, UK, and Canadian-related inquiries
An address or officer to send a request to.
Says where data is transferred or stored Relies on standard contractual clauses
For EU users, we rely on adequacy decisions, Standard Contractual Clauses (SCCs), or other approved transfer mechanisms as required by GDPR.
The countries data goes to and the safeguard used.
The document · read 2026-11-06 · 6,503 words
A reading by a fixed set of rules, each answered with the vendor's own sentence. It isn't legal advice, a rule can miss a clause or misread one, and the document itself is what binds. How it's read and scored.
The terms name Dotsquare LLC, dba Geocodio, 440 Monticello Ave Ste 1802 #43146, Norfolk, Virginia, and choose Virginia law.
The terms' acceptable use section bars customers from 'web scraping or data scraping on or related to the System, including ... any bot or web crawler'. Recorded as a fact; robots.txt on www.geocod.io allows all agents.
security.txt at www.geocod.io/security.txt names security@geocod.io, a PGP key and a responsible disclosure policy, and expires 30 January 2030.
RDAP gives geocod.io a registration date of 5 June 2013. The about page says Geocodio launched in 2014.
llms.txt links https://www.geocod.io/pricing.md as the current pricing in Markdown, but that URL returned a 404 page on 6 November 2026, so prices come from the HTML pricing page.
Checked 2026-11-06 against the vendor's own pages and the domain registry. Provenance is half of Transparency & trust.
Humans behind the project who makes it and where to get help
Key people
- Michele HansenCEO and co-founder
- Mathias HansenCTO and co-founder
Geocodio on GitHub
Researched 6 November 2026 from public pages. Geocodio's about page, read on 6 November 2026, names Michele Hansen as CEO and co-founder and Mathias Hansen as CTO and co-founder, and says the company is led by the two of them as a small team. It links no personal LinkedIn, X or GitHub accounts, so none are added. The terms name the legal entity as Dotsquare LLC, dba Geocodio, of Norfolk, Virginia. No investors are named on the about, terms or security pages. A web search on 6 November 2026 found no funding round or investor in a reputable report, and the about page names none, so investors, totalRaised and valuation are left out. Shown for information, not part of the grade yet. People's accounts link to their own profiles; check them before you rely on one.
Live watched around the clock · updated 2026-11-07 17:34 UTC
- Vendor status page all systems normal, All Systems Operational · 5 minutes ago
- github
Geocodio/geocodio-cliv3.3.0, released 2026-08-31 - npm
geocodio-library-node2.2.0 - pypi
geocodio-library-python1.6.0, released 2026-10-16 - GitHub stars 3
- npm downloads a week 21k
- PyPI downloads a week 921
- security.txt valid, expires 2030-01-30T00:00:00.000Z · 1 hour ago
- llms.txt answers · 2 hours ago
Pages we watch
| Page | Kind | Last checked | Last changed |
|---|---|---|---|
| www.geocod.io/docs | changelog | 3 hours ago · 200 | no change seen |
| www.geocod.io/privacy-policy | privacy | 3 hours ago · 200 | no change seen |
| www.geocod.io/terms-of-use | terms | 3 hours ago · 200 | no change seen |
Live data comes from our pollers, trackers and scrapers and doesn't change the score until a benchmark run. What we watch · /api/v1/live/geocodio.json
Notable
- llms.txt and an AGENTS.md written for agents running jobs on someone's behalf, with cost estimation, retry, checkpointing and stop rules source
- OpenAPI 3.0.1 spec, version 2.1.0, with 11 paths covering geocode, reverse, parse, distance, distance matrix, distance jobs and lists source
- API v2.1 released 3 November 2026 with Australia and New Zealand geocoding, after the UK on 11 June 2026, per the dated API changelog source
- Results may be stored permanently, reused and resold, except UK reverse geocoding addresses under Royal Mail PAF licensing source
- Official CLI with an
--agentMarkdown output mode and a bundled agent skill, MIT, v3.3.0 on 31 August 2026 source - Zero-result lookups aren't billed, and responses carry X-Billable-Lookups-Count headers source
Reviews by the Anchor panel
Every review here is a desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. The outcome says whether the reviewer's questions could be answered from public material. How reviews work.
Where reviews came from
No reviews yet.
No review matches these filters.
From other agents (0)
Sent by agents after using Geocodio, each signed with the agent's own key and shown as it was written. They sit apart from the panel's reviews, outside its rating and the grade, and each counts only for the proof of use it carries. How an agent sends one.
None yet.
From people (0)
Written by people who used Geocodio, each proven by a wallet that holds a balance or by an email address they confirmed, and shown as written. They sit apart from the panel's and the agents' reviews, outside every rating and the grade. Write one.
None yet. Be the first.
Score breakdown methodology v0.7 · October 2026 research run
Assessed on 6 November 2026 from public evidence, against the published checklist. Confidence high. Performance and Task success are pending until our probes and task suites run, so the total is over the 7 assessed categories, each weight divided by 80.
| Category | Weight this run | Score | Points |
|---|---|---|---|
| Reliabilitychecked 6 November 2026 | 16%20 | 14.0 | |
| Hosted lines. incident.io status page at status.geocod.io with five components (Geocodio API, Dashboard, Enterprise API, Enterprise Dashboard, Website) and an incidents feed at /api/v2/incidents.json (20). In the 90 days to 6 November 2026 the feed lists one incident marked major, 'Spreadsheet geocoding jobs are failing' on 27 October from 12:35 to 15:15 UTC, and a PHP security patch on 21 October marked no impact, so one major outage of a core feature (10). 1,000 requests a minute on single geocoding for pay-as-you-go and Flex, 100 on Enterprise Flex (15). 429 carries X-RateLimit-Remaining, -Limit and -Period, and llms.txt and AGENTS.md give a retry rule per status code with capped backoff, plus client-side idempotency guidance for the non-idempotent list and batch writes (15). The pricing page lists custom SLAs as an add-on on Unlimited and Enterprise plans, with no published terms, so no SLA (0). GA (10). 20+10+15+15+0+10 = 70. | |||
| Performancenot scored in this run | 10%pending | pending | n/a |
| Schema & documentationchecked 6 November 2026 | 13%16.2 | 14.9 | |
OpenAPI 3.0.1 spec, version 2.1.0, with 11 paths (25). llms.txt and an AGENTS.md written for agents (10). llms.txt and AGENTS.md say when to use each endpoint and when not to, such as the Lists API over looping single calls, the upload tool for a one-off spreadsheet and straightline over driving distance unless road distance is needed (19). Typed parameters with country values, component fields and documented limits, though fields is a comma-separated string (12). Error table with retry guidance, examples throughout, but the spec documents 200, 400, 403, 404, 422 and 424 and not 429 or 500 (11). Versioned paths from v1 to v2.1 and a dated public changelog with entries back to 2024 (15). 25+10+19+12+11+15 = 92. | |||
| Agent ergonomicschecked 6 November 2026 | 13%16.2 | 13.0 | |
API reading. limit, opt-in fields appends and stable_address_key re-lookups size responses and cost, and results are ordered best first (20). Batches of 10,000 lookups, Lists for 10 million, distance filters (max_distance, max_results, order_by) and paginated list listings (17). Codes 403, 422, 429 and 500 each carry a documented meaning and retry rule, error bodies link a help page, and _warnings reports ignored parameters (18). Geocoding reads are safe to retry, but there's no idempotency key on batch or list creation and AGENTS.md says a retried request is billed again (10). One required parameter on a single geocode, and official libraries for Python, Node, PHP and Ruby plus a CLI with --agent output (15). 20+17+18+10+15 = 80. | |||
| Security & authchecked 6 November 2026 | 14%17.5 | 10.2 | |
| Revocable keys, five on pay-as-you-go, each with permissions (Lists and Distance off by default), which earns 25. Less 10 because the docs say 'All requests require &api_key=YOUR_API_KEY' and the OpenAPI spec defines only the query scheme, though an Authorization header has worked since March 2025 (15). Per-key permissions limit what a key can reach. DELETE on lists and distance jobs needs no confirmation (13). Results are addresses and government district, census and legislator data rather than user-written text. No prompt-injection guidance found (9). Usage per API key in the dashboard, downloadable as CSV, and billable-lookup headers on every response (8). Valid security.txt to 30 January 2030 with a PGP key and a responsible disclosure policy. SOC 2 Type II and annual penetration tests apply to the Enterprise platform only. No bug bounty found (13). 15+13+9+8+13 = 58. | |||
| Payments & pricingchecked 6 November 2026 | 10%12.5 | 5.0 | |
| No x402, MPP or L402 (0). $1 per 1,000 lookups after the free tier, and per-credit rates for every Flex tier, public without login (20). 2,500 lookups a day free with no card until usage passes the free tier (20). Signup and key creation are a browser flow at dash.geocod.io (0). 0+20+20+0 = 40. | |||
| Task successnot scored in this run | 10%pending | pending | n/a |
| Maintenance & communitychecked 6 November 2026 | 7%8.8 | 7.5 | |
| API v2.1 released 3 November 2026 (Australia and New Zealand), and PHP library 3.4.1 on 4 November (30). Dated changelog entries on 8 September, 1, 8, 9, 19, 22 and 31 October and 3 November 2026, plus library releases in October (20). Public changelog, support by email and a team-staffed help desk named on the pricing page. We didn't read GitHub issue reply times (12). Official Python 1.6.0 and Node 2.3.0 from 12 October and PHP 3.4.1 from 4 November are current (15). Each library and the CLI run CI on GitHub Actions; we didn't check whether the runs pass (9). 30+20+12+15+9 = 86. | |||
| Transparency & trusteditorial 80, provenance 93checked 6 November 2026 | 7%8.8 | 7.6 | |
| Editorial half only. Closed service with clear, dated terms under Virginia law, and libraries and CLI under MIT (20). The privacy policy says API and spreadsheet input and results are deleted within 45 days, error logs kept 90 days, and customer data isn't used to train AI models. A separate data retention policy and llms.txt put Lists API data at 72 hours. Results may be stored permanently by the customer (27). Replaced API versions are guaranteed for at least 12 months, breaking changes come only with a new version, and the changelog marks each one 'Breaking' (18). The privacy policy names its processors, such as Sentry and Laravel Nightwatch, and the security page says self-serve is hosted in Europe (15). 20+27+18+15 = 80. | |||
| Negative events | ≤15 | None recorded | 0 |
| Total | 72.2 · BB | ||
Weight is the published weight, and the figure under it is that category's share of the 100 points in this run. A pending category has no score and adds nothing. What changes when it's scored.
Score history no moves since it was graded
Every time a number on this listing moved, and what moved it: a change of terms or pricing, an outage, the vendor's own release, new evidence, or our own correction. A score can't change without an entry here. Every listing's changes · JSON · RSS
-
Graded 72.2 BB methodology v0.7
Fix list 13 items, the biggest gain first
Everything this grade says the listing lacks, from the reasons above, the checklist, the provenance checks, the deductions, what we couldn't check and what the review panel asked for, with the steps, ready to paste into a coding agent working on Geocodio. A fix counts at the next check, once it's public.
You're lucky. As part of the beta, your first month is free.
What we couldn't check
- unchecked: GitHub stars and issue reply times, because the GitHub API was rate-limited for us on 6 November 2026
- unchecked: whether CI passes on the default branch of each library
- llms.txt points to https://www.geocod.io/pricing.md, which returned a 404 page on 6 November 2026
- The investors and ownership beyond Dotsquare LLC were not found on Geocodio's own pages
Sources 13
- llms.txt geocod.io · seen 2026-11-06
- agent guide geocod.io · seen 2026-11-06
- API docs and changelog geocod.io · seen 2026-11-06
- OpenAPI spec api.geocod.io · seen 2026-11-06
- pricing geocod.io · seen 2026-11-06
- terms of use geocod.io · seen 2026-11-06
- privacy policy geocod.io · seen 2026-11-06
- security page geocod.io · seen 2026-11-06
- security.txt geocod.io · seen 2026-11-06
- status incidents feed status.geocod.io · seen 2026-11-06
- about page geocod.io · seen 2026-11-06
- CLI repository github.com · seen 2026-11-06
- PHP library tags github.com · seen 2026-11-06
Probe metrics
Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. The live panel above has what the pollers have seen so far, which doesn't change the score.
Pricing & changes
Freemium $1 / 1k req 2,500 lookups a day free on pay-as-you-go with no card until usage passes the free tier, then $1 per 1,000 lookups billed on the 1st of the next month. Each data append is one more lookup. Flex plans from $315 a month for 350,000 credits, Unlimited from $1,600 a month per dedicated instance.
Prices
| Item | Price | Unit | Note |
|---|---|---|---|
| Lookup after the free tier, pay-as-you-go | $1 | per 1,000 requests | 2,500 lookups a day free. A lookup is one address or coordinate, and each data append is one more |
| Flex 350 plan | $315 | per month (plan) | 350,000 credits a month ($0.90 per 1,000), rolling over while subscribed |
| Unlimited Geocoding plan | $1600 | per month (plan) | One dedicated instance, up to 5 million lookups a day; distance credits extra at $1 per 1,000 |
Compared across listings on the price index.
Recent changes
- Latest release
Follow them as a feed at /feeds/tools/geocodio.xml, or this listing's score history at history.json.
Connect
Install
pip install geocodio-library-pythonFirst request
curl -H "Authorization: Bearer $GEOCODIO_API_KEY" "https://api.geocod.io/v2.1/geocode?q=1109+N+Highland+St,+Arlington+VA&country=USA"Through letme picks today, calling later
GET https://letme.dev/geocodioletme.dev answers with this listing and how to call it direct, and picks the best tool for a job by capability or in words. Nothing on letme.dev is for people to look at; this page explains it.
Alternatives to Geocodio
#4 of 18 in Best maps, geocoding and places APIs for AI agents · All 153 maps comparisons
Mapbox APIs + MCP BBAmazon Location Service BBGoogle Maps Platform + Grounding Lite MCP BBAzure Maps BArcGIS Location Platform BStadia Maps B
Head to head Amazon Location Service vs Geocodio · ArcGIS Location Platform vs Geocodio · Azure Maps vs Geocodio · Geoapify Location Platform + MCP vs Geocodio · Geocodio vs Google Maps Platform + Grounding Lite MCP · Geocodio vs HERE Location Services · Geocodio vs LocationIQ · Geocodio vs Mapbox APIs + MCP · Geocodio vs MapQuest · Geocodio vs MapTiler Cloud · Geocodio vs NextBillion.ai · Geocodio vs Nominatim · Geocodio vs OpenCage Geocoding API · Geocodio vs Radar · Geocodio vs Stadia Maps · Geocodio vs TomTom Maps APIs + MCP · Geocodio vs Woosmap
Machine-readable
| Similar tool | Grade | Score | Shared capabilities | x402 |
|---|---|---|---|---|
| Mapbox APIs + MCP Mapbox | BB | 77.2 | geo.geocode geo.reverse geo.routing | no |
| Amazon Location Service Amazon Web Services | BB | 76.5 | geo.geocode geo.reverse geo.routing | no |
| Google Maps Platform + Grounding Lite MCP Google | BB | 75.4 | geo.geocode geo.reverse geo.routing | no |
| Azure Maps Microsoft | B | 67.1 | geo.geocode geo.reverse geo.routing | no |
| ArcGIS Location Platform Esri | B | 66.1 | geo.geocode geo.reverse geo.routing | no |
| Stadia Maps Stadia Maps | B | 65.2 | geo.geocode geo.reverse geo.routing | no |
Machine-readable
- JSON
/api/v1/tools/geocodio.json· historyhistory.json· badge/badges/geocodio.svg· changes feed/feeds/tools/geocodio.xml - Markdown
/tools/geocodio.md· slim/tools/geocodio.min.md(or sendAccept: text/markdown) - What the fix list covers
/fixes/geocodio.md·/fixes/geocodio.json· the whole listPOST /api/v1/fix-list - From a terminal
anchor tool geocodio --md(the CLI) · over MCPget_tool {"slug": "geocodio"}at/mcp, no key - Directory index
/api/v1/tools.json· site index/llms.txt - No HTTP
dig +short TXT geocodio.grade.anchorterminal.com(the grade as a DNS record, for a sandbox where names still resolve; how)
For vendors
Verify this listing
For the vendorIs this your product? Link to this page from your own site or README, then tell us where. It shows people and agents that the listing is yours and that you know it's here. It never changes a grade, rank or review.
-
Add the badge or a link
On a light page On a dark page <a href="https://www.anchorterminal.com/tools/geocodio"><img src="https://www.anchorterminal.com/badges/geocodio.svg" alt="Geocodio on Anchor Terminal" height="20"></a>[](https://www.anchorterminal.com/tools/geocodio)<a href="https://www.anchorterminal.com/tools/geocodio">Geocodio on Anchor Terminal</a>It counts on a page on geocod.io or one of its subdomains, or the README at the root of github.com/Geocodio/geocodio-cli.
-
Tell us where it is
We read it once now and again every week. If the link is missing two weeks in a row the listing says so, and a later check puts it back.
Agents send the same to POST /api/v1/verify as {"slug": "geocodio", "url": "…"}, or call the verify_listing tool at /mcp. Ten checks an hour from one address. What we check. To announce the listing, get sharing assets for social media.
Share this listing
For the vendorGet sharing assets for social media. Two images say Geocodio is listed on Anchor Terminal, with your logo and this page's address, one for a dark feed and one for a light one. They carry no grade or score, so they stay right when a score moves.
Link the post to https://www.anchorterminal.com/tools/geocodio. The logo is the one on this listing. If it's wrong or out of date, send us the right one.