{ "data": { "a": { "slug": "geocodio", "name": "Geocodio", "vendor": "Dotsquare LLC", "vendorUrl": "https://www.geocod.io", "kind": "http-api", "category": "maps", "summary": "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.", "url": "https://www.anchorterminal.com/tools/geocodio", "markdownUrl": "https://www.anchorterminal.com/tools/geocodio.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/geocodio.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/geocodio.json", "dns": "geocodio.grade.anchorterminal.com", "repo": "https://github.com/Geocodio/geocodio-cli", "transports": [ "http" ], "packages": [ { "registry": "pypi", "name": "geocodio-library-python" }, { "registry": "npm", "name": "geocodio-library-node" } ], "auth": "api-key", "authNotes": "API key from the dashboard at dash.geocod.io after a browser signup, sent as `Authorization: Bearer` (since March 2025) or the `api_key` query parameter, which the docs and the OpenAPI spec still lead with. Five keys on pay-as-you-go. A new key reaches single and batch geocoding only; the Lists and Distance APIs must be enabled per key.", "pricing": "freemium", "pricingNotes": "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.", "priceSummary": "$1 / 1k req", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in llms.txt, AGENTS.md, the docs or the OpenAPI spec (checked 2026-11-06). Billing is by card on file, monthly in arrears on pay-as-you-go.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 20984, "pypiWeekly": 921, "asOf": "2026-11-06" }, "docsUrl": "https://www.geocod.io/docs/", "llmsTxt": "https://www.geocod.io/llms.txt", "openapi": "https://api.geocod.io/openapi-spec.json", "capabilities": [ "geo.geocode", "geo.reverse", "geo.routing" ], "tags": [ "hosted", "api-key", "freemium", "free-tier", "no-card", "llms-txt", "openapi", "official", "cli", "agent-skills", "python", "typescript", "php", "ruby", "batch", "async-jobs", "status-page", "security-txt", "enterprise", "soc2", "closed-source" ], "lastRelease": "2026-11-03", "graded": true, "anchor": { "graded": true, "score": 72.2, "grade": "BB", "agentReady": true, "rank": 138, "ranked": true, "rankOf": 1510, "categoryRank": 4, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 80, "maintenance": 86, "payments": 40, "reliability": 70, "schema": 92, "security": 58, "transparency": 87 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "high", "date": "2026-11-06" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "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" ], "agentNotes": [ "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 `_warnings` for 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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "high", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 72.2 } ], "editorialScores": { "ergonomics": 80, "maintenance": 86, "payments": 40, "reliability": 70, "schema": 92, "security": 58, "transparency": 80 }, "provenanceScore": 93, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install geocodio-library-python", "http": "curl -H \"Authorization: Bearer $GEOCODIO_API_KEY\" \"https://api.geocod.io/v2.1/geocode?q=1109+N+Highland+St,+Arlington+VA\u0026country=USA\"" }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/geocodio" }, "area": "everyday", "unitPrices": [ { "item": "Lookup after the free tier, pay-as-you-go", "unit": "1k-requests", "usd": 1, "note": "2,500 lookups a day free. A lookup is one address or coordinate, and each data append is one more" }, { "item": "Flex 350 plan", "unit": "month", "usd": 315, "note": "350,000 credits a month ($0.90 per 1,000), rolling over while subscribed" }, { "item": "Unlimited Geocoding plan", "unit": "month", "usd": 1600, "note": "One dedicated instance, up to 5 million lookups a day; distance credits extra at $1 per 1,000" } ], "provenance": { "legalEntity": "Dotsquare LLC", "domain": "geocod.io", "domainRegistered": "2013-06-05", "endpointOnVendorDomain": true, "terms": "https://www.geocod.io/terms-of-use", "privacy": "https://www.geocod.io/privacy-policy", "statusPage": "https://status.geocod.io", "changelog": "https://www.geocod.io/docs/#changelog", "securityTxt": "valid", "checked": "2026-11-06", "notes": [ "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." ], "score": 93 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/geocodio.json", "live": { "slug": "geocodio", "vendorStatus": { "page": "https://status.geocod.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T19:22:12.77760537Z" }, "versions": [ { "registry": "github", "name": "Geocodio/geocodio-cli", "version": "v3.3.0", "released": "2026-08-31", "seenAt": "2026-11-06T23:28:00.884456202Z" }, { "registry": "npm", "name": "geocodio-library-node", "version": "2.2.0", "seenAt": "2026-11-06T23:28:00.414999469Z" }, { "registry": "pypi", "name": "geocodio-library-python", "version": "1.6.0", "released": "2026-10-16", "seenAt": "2026-11-06T23:27:57.978816079Z" } ], "githubStars": 3, "npmWeekly": 20984, "pypiWeekly": 921, "securityTxt": { "url": "https://geocod.io/.well-known/security.txt", "state": "valid", "expires": "2030-01-30T00:00:00.000Z", "checkedAt": "2026-11-07T16:01:17.012285777Z" }, "llmsTxt": { "url": "https://www.geocod.io/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:35.723551581Z" }, "pages": [ { "url": "https://www.geocod.io/docs/", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:29:02.899876797Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9bcdba9ab6f4" }, { "url": "https://www.geocod.io/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:29:05.843886759Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "712b2145deac" }, { "url": "https://www.geocod.io/terms-of-use", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:29:07.288294893Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "ff5d2a37483d" } ], "updatedAt": "2026-11-07T19:22:12.77760537Z" } }, "answer": "Geocodio scores 72.2 (BB) on agent readiness against MapQuest's 35.4 (F), and leads in every scored category.", "b": { "slug": "mapquest", "name": "MapQuest", "vendor": "MapQuest (System1)", "vendorUrl": "https://developer.mapquest.com", "kind": "http-api", "category": "maps", "summary": "MapQuest's location APIs cover geocoding, directions, route matrices, place search, traffic and static maps. Agents call the REST API with a key or connect to a hosted MCP server over OAuth.", "url": "https://www.anchorterminal.com/tools/mapquest", "markdownUrl": "https://www.anchorterminal.com/tools/mapquest.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/mapquest.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/mapquest.json", "dns": "mapquest.grade.anchorterminal.com", "license": "Proprietary service. No API terms were found published without a login", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://www.mapquestapi.com", "packages": [], "auth": "mixed", "authNotes": "Self-serve. A person registers at developer.mapquest.com and creates an API key. REST calls send it in the `key` query parameter. The MCP server uses OAuth through login.mapquest.com with the single scope `mcp:tools`, then picks one of the account's keys. Further keys can be created with `POST /account/v1/keys`.", "pricing": "usage", "pricingNotes": "MapQuestGO is pay-as-you-go at $0.0045 a transaction with no monthly minimum, after 50,000 one-time free transactions that expire on 1 January 2027. Monthly plans run from Basic at $119 (30,000 transactions) to Business Plus at $949 (500,000). Enterprise is by quote. An agent can start on the free credits without a contract. Whether sign-up needs a card was not established (https://developer.mapquest.com/plans, checked 2026-10-08).", "priceSummary": "$4.50 / 1k req", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, the plans page, llms.txt or the MCP endpoint's 401 response (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://developer.mapquest.com/documentation/", "llmsTxt": "https://developer.mapquest.com/llms.txt", "capabilities": [ "geo.geocode", "geo.reverse", "geo.routing", "geo.places" ], "tags": [ "hosted", "mcp", "oauth", "api-key", "llms-txt", "free-credits", "usage-priced", "closed-source" ], "lastRelease": "2026-07-16", "graded": true, "anchor": { "graded": true, "score": 35.4, "grade": "F", "agentReady": false, "rank": 1395, "ranked": true, "rankOf": 1510, "categoryRank": 18, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 60, "maintenance": 23, "payments": 30, "reliability": 23, "schema": 47, "security": 28, "transparency": 31 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": 0, "verdict": "One account reaches geocoding, routing, place search and traffic through a REST API or a hosted MCP server with OAuth, at a published $0.0045 a transaction. No API terms, status page, changelog or product OpenAPI spec was found, and REST keys travel in the query string.", "bestFor": "An agent that needs US-centred geocoding, routing with truck profiles, traffic and place search behind one account, with an MCP server ready to connect.", "strengths": [ "Hosted MCP server at `https://www.mapquestapi.com/mcp` with OAuth and published protected-resource metadata", "Pay-as-you-go price of $0.0045 a transaction published without a login, with 50,000 one-time free transactions", "The Account API creates and lists keys and reports usage by key, service and hour", "`llms.txt` indexes every REST API, SDK and tool with a one-line purpose", "Async batch geocoding accepts up to 1 million rows, and batch calls take 100 locations" ], "weaknesses": [ "No API terms of service found. The legal link leads to System1's 2021 website terms, which allow personal, non-commercial use only", "No status page, changelog or published rate-limit numbers found", "REST keys are sent in the `key` query parameter, and no key scopes or restrictions are documented", "`openapi.json` describes the marketing site and has no paths, so the product APIs have no machine-readable contract", "Monthly plans forbid storing or caching geocodes. That needs an Enterprise account" ], "agentNotes": [ "Register an account and create an API key before connecting the MCP server. Every tool needs an active key, chosen by nickname on first use", "Send REST calls to `https://www.mapquestapi.com` with `key` in the query string, and redact it from logged URLs", "Read `info.statuscode` in geocoding and directions responses. 0 is success, and errors such as 610 (ambiguous location) arrive in the body", "Set `thumbMaps=false` and `maxResults` on geocoding, and `pageSize` (1 to 50) on place search, to keep responses small", "Do not store or cache geocodes on a monthly or pay-as-you-go plan" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 2.8, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "F", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 35.4 } ], "editorialScores": { "ergonomics": 60, "maintenance": 23, "payments": 30, "reliability": 23, "schema": 47, "security": 28, "transparency": 21 }, "provenanceScore": 41, "checked": { "categories": { "ergonomics": "2026-10-08", "maintenance": "2026-10-08", "payments": "2026-10-08", "reliability": "2026-10-08", "schema": "2026-10-08", "security": "2026-10-08", "transparency": "2026-10-08" }, "last": "2026-10-08", "lastMoved": "2026-10-28", "oldest": "2026-10-08", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl \"https://www.mapquestapi.com/geocoding/v1/address?key=$MAPQUEST_API_KEY\u0026location=Washington,DC\u0026maxResults=1\u0026thumbMaps=false\"", "claudeCode": "claude mcp add --transport http mapquest https://www.mapquestapi.com/mcp", "config": { "mcpServers": { "mapquest": { "url": "https://www.mapquestapi.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/geo.geocode", "tool": "https://letme.dev/mapquest" }, "area": "everyday", "unitPrices": [ { "item": "MapQuestGO pay-as-you-go", "unit": "1k-requests", "usd": 4.5, "note": "$0.0045 a transaction after 50,000 one-time free transactions" }, { "item": "Basic plan", "unit": "month", "usd": 119, "note": "30,000 transactions a month" }, { "item": "Plus plan", "unit": "month", "usd": 249, "note": "75,000 transactions a month" }, { "item": "Business plan", "unit": "month", "usd": 499, "note": "200,000 transactions a month" }, { "item": "Business Plus plan", "unit": "month", "usd": 949, "note": "500,000 transactions a month" } ], "provenance": { "legalEntity": "Mapquest Holdings LLC", "domain": "mapquest.com", "domainRegistered": "1996-01-10", "endpointOnVendorDomain": false, "terms": "", "privacy": "", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-10-08", "notes": [ "The developer site's footer reads '© 2026 Mapquest Holdings LLC, A System1 Company'.", "No terms link is given. The site's Terms of Use link, and developer.mapquest.com/legal, lead to https://system1.com/terms/terms-of-use, the parent's website terms (last updated 26 February 2021), which allow personal, non-commercial use only and do not mention the APIs. We found no API or platform terms published without a login.", "No privacy link is given. The only privacy document linked is the System1 OpCo, LLC group privacy policy at https://system1.com/terms/privacy-policy (last updated 5 July 2023), a parent company's notice.", "The REST API and the MCP server answer at www.mapquestapi.com, a second domain (registered 2008-09-08 per RDAP). MapQuest's own docs name that host. OAuth runs at login.mapquest.com.", "developer.mapquest.com/.well-known/security.txt redirects to the home page, www.mapquestapi.com/.well-known/security.txt returns 404, and www.mapquest.com returned an empty 202 to our reader.", "No status page is linked from the developer site, the docs or the plans page. No changelog was found. The blog carries two product announcements dated 16 July 2026.", "RDAP for mapquest.com gives a registration date of 1996-01-10." ], "score": 41 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/mapquest.json", "live": { "slug": "mapquest", "probe": { "target": "https://www.mapquestapi.com", "method": "get", "lastAt": "2026-11-07T19:22:18.221660176Z", "lastOk": true, "lastStatus": 404, "lastMs": 353, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 271, "p95ms24h": 353, "samples24h": 238, "samples30d": 7430, "days": [ { "date": "2026-10-08", "probes": 50, "ok": 50 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "securityTxt": { "url": "https://mapquest.com/.well-known/security.txt", "state": "unknown", "checkedAt": "2026-11-07T16:01:46.794353638Z" }, "llmsTxt": { "url": "https://developer.mapquest.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:57.161838807Z" }, "domain": { "domain": "mapquest.com", "registered": "1996-01-10", "source": "https://rdap.verisign.com/com/v1/domain/mapquest.com", "checkedAt": "2026-11-01T14:16:24.508888622Z" }, "mcpTools": { "url": "https://www.mapquestapi.com/mcp", "checkedAt": "2026-11-07T01:46:11.005976855Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:46:11.005976855Z" }, "updatedAt": "2026-11-07T19:22:18.221660176Z" } }, "edges": [ { "by": 63, "category": "maintenance", "leads": "geocodio", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "b": "The newest dated product changes are two blog announcements on 16 July 2026 (the Geolocation API and a 10,000 by 10,000 async route matrix), 84 days before the check (20). Two dated entries in 90 days. The MCP guide's version 1.2 is dated 7 July 2026, 93 days before (0). No changelog. Support is by email, untested (3). The MCP registry returns no server for 'mapquest', and the only current SDKs are browser libraries with no dated releases found (0). No package to judge (0)." }, "scores": { "a": 86, "b": 23 } }, { "by": 56, "category": "transparency", "leads": "geocodio", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "Closed service. The only terms linked are System1's website terms of 26 February 2021, which allow personal, non-commercial use and do not mention the APIs. The plans page states the storage rule (5). The System1 group privacy policy of 5 July 2023 gives no retention periods and describes sale and sharing of personal information, while the plans page says 'we don't collect or sell user data' (8). No deprecation policy. Dated notices exist from 2018 only (5). The policy names categories of service providers, with no list or locations. The geocoding docs name TomTom for international queries (3)." }, "scores": { "a": 87, "b": 31 } }, { "by": 47, "category": "reliability", "leads": "geocodio", "name": "Reliability", "reasons": { "a": "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.", "b": "Graded as a hosted service. No status page is linked from the developer site, the docs or the plans page (0). With no page there is no readable incident history (5). The reference marks endpoints 'Rate Limited Yes' and gives functional maximums (100 locations a batch, 50 a route, 25 a matrix) but no request-rate numbers (5). No 429, Retry-After or backoff guidance found (0). The Enterprise plan lists a service-level agreement, with no text published (3). The REST API is generally available and the MCP page calls the server production-ready (10)." }, "scores": { "a": 70, "b": 23 } }, { "by": 45, "category": "schema", "leads": "geocodio", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "`https://developer.mapquest.com/openapi.json` describes the marketing site and has an empty `paths` object, so the product APIs have no machine-readable contract. The MCP tool definitions sit behind OAuth and were not read (0). `llms.txt` indexes every API with a one-line purpose (10). The reference states each endpoint's purpose and each parameter's effect, without when-not-to-use guidance (12). Parameter tables give ranges and allowed values in prose (8). Example requests and responses on each page, and status-code pages per API (12). Versions in the path (v1, v2, v4, v5) but no changelog (5)." }, "scores": { "a": 92, "b": 47 } }, { "by": 30, "category": "security", "leads": "geocodio", "name": "Security \u0026 auth", "reasons": { "a": "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 \u0026api_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.", "b": "REST uses API keys, several per account, created in the dashboard or by API. The MCP server uses OAuth with one scope, `mcp:tools`. That earns 20, less 10 because the `key` query parameter is the documented way to send the secret (10). No key scopes, referrer or IP restrictions, or read-only mode found in the docs (3). Place and address text is returned with no prompt-injection guidance (7). The usage endpoint reports transactions by key, service and hour (8). No security.txt, disclosure policy, bug bounty or certification found (0)." }, "scores": { "a": 58, "b": 28 } }, { "by": 20, "category": "ergonomics", "leads": "geocodio", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "The MCP page names 13 tools. Their definitions were not read, so context cost is scored from the count and from REST controls such as `maxResults`, `thumbMaps=false` and `outFormat` (15). Place search pages with `pageSize` 1 to 50 and filters by category, circle, bounding box or corridor (16). Status codes are documented, with geocoding and directions errors carried in the response body and problem+json on the Account API (12). Most calls read and are safe to retry. Data Manager writes have no idempotency key, and MCP annotations were not read (10). Geocoding needs only `key` and `location`. The only current SDKs are browser libraries (7)." }, "scores": { "a": 80, "b": 60 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Dotsquare LLC", "b": "MapQuest (System1)", "name": "Vendor" }, { "a": "no (local only)", "b": "https://www.mapquestapi.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Pay per use", "name": "Pricing" }, { "a": "$1600 per month (plan)", "b": "not published", "name": "Price for geocoding" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "Proprietary service. No API terms were found published without a login", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "2026-11-03", "b": "2026-07-16", "name": "Last release" }, { "a": "no date given", "b": "no document linked", "name": "Terms last updated" }, { "a": "2018-05-25", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not read yet", "name": "Customer content may train models" }, { "a": "yes", "b": "not read yet", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not read yet", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not read yet", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not read yet", "name": "Arbitration or class-action waiver" }, { "a": "21k npm/wk, 921 PyPI/wk", "b": "none", "name": "Popularity" }, { "a": "none", "b": "2.8/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "Geocodio scores 72.2 (BB) on agent readiness against MapQuest's 35.4 (F), and leads in every scored category.", "question": "Which is better for AI agents, Geocodio or MapQuest?" }, { "answer": "Geocodio needs an API key. MapQuest takes an API key or an OAuth sign-in.", "question": "Do Geocodio and MapQuest need an API key?" }, { "answer": "No hosted endpoint is listed for Geocodio. MapQuest has a hosted endpoint at https://www.mapquestapi.com.", "question": "Can an agent call Geocodio and MapQuest without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 70 against 23", "Schema \u0026 documentation, 92 against 47", "Agent ergonomics, 80 against 60", "Security \u0026 auth, 58 against 28", "Payments \u0026 pricing, 40 against 30", "Maintenance \u0026 community, 86 against 23", "Transparency \u0026 trust, 87 against 31" ], "also": [ "Agent-ready, a grade of BB or better", "Free to start without a card" ], "goodFor": "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.", "slug": "geocodio", "watchFor": "Covers only the US, Canada, Mexico, the UK, Australia and New Zealand, and UK needs a Flex or Unlimited plan" }, { "aheadOn": null, "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "An agent that needs US-centred geocoding, routing with truck profiles, traffic and place search behind one account, with an MCP server ready to connect.", "slug": "mapquest", "watchFor": "No API terms of service found. The legal link leads to System1's 2021 website terms, which allow personal, non-commercial use only" } ], "history": { "geocodio": null, "mapquest": [ { "causes": [ "correction" ], "date": "2026-10-28", "delta": -0.1, "from": 35.5, "fromGrade": "F", "to": 35.4, "toGrade": "F" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.4, "from": 35.1, "fromGrade": "F", "to": 35.5, "toGrade": "F" } ] }, "job": { "capability": "geo.geocode", "name": "Geocoding" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-location-vs-geocodio.json", "title": "Amazon Location Service vs Geocodio", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-geocodio" }, { "json": "https://www.anchorterminal.com/compare/amazon-location-vs-mapquest.json", "title": "Amazon Location Service vs MapQuest", "url": "https://www.anchorterminal.com/compare/amazon-location-vs-mapquest" }, { "json": "https://www.anchorterminal.com/compare/arcgis-vs-geocodio.json", "title": "ArcGIS Location Platform vs Geocodio", "url": "https://www.anchorterminal.com/compare/arcgis-vs-geocodio" }, { "json": "https://www.anchorterminal.com/compare/arcgis-vs-mapquest.json", "title": "ArcGIS Location Platform vs MapQuest", "url": "https://www.anchorterminal.com/compare/arcgis-vs-mapquest" }, { "json": "https://www.anchorterminal.com/compare/azure-maps-vs-geocodio.json", "title": "Azure Maps vs Geocodio", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-geocodio" }, { "json": "https://www.anchorterminal.com/compare/azure-maps-vs-mapquest.json", "title": "Azure Maps vs MapQuest", "url": "https://www.anchorterminal.com/compare/azure-maps-vs-mapquest" }, { "json": "https://www.anchorterminal.com/compare/geoapify-vs-geocodio.json", "title": "Geoapify Location Platform + MCP vs Geocodio", "url": "https://www.anchorterminal.com/compare/geoapify-vs-geocodio" }, { "json": "https://www.anchorterminal.com/compare/geoapify-vs-mapquest.json", "title": "Geoapify Location Platform + MCP vs MapQuest", "url": "https://www.anchorterminal.com/compare/geoapify-vs-mapquest" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-google-maps-platform.json", "title": "Geocodio vs Google Maps Platform + Grounding Lite MCP", "url": "https://www.anchorterminal.com/compare/geocodio-vs-google-maps-platform" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-here-location-services.json", "title": "Geocodio vs HERE Location Services", "url": "https://www.anchorterminal.com/compare/geocodio-vs-here-location-services" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-locationiq.json", "title": "Geocodio vs LocationIQ", "url": "https://www.anchorterminal.com/compare/geocodio-vs-locationiq" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-mapbox.json", "title": "Geocodio vs Mapbox APIs + MCP", "url": "https://www.anchorterminal.com/compare/geocodio-vs-mapbox" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-maptiler.json", "title": "Geocodio vs MapTiler Cloud", "url": "https://www.anchorterminal.com/compare/geocodio-vs-maptiler" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-nextbillion.json", "title": "Geocodio vs NextBillion.ai", "url": "https://www.anchorterminal.com/compare/geocodio-vs-nextbillion" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-nominatim.json", "title": "Geocodio vs Nominatim", "url": "https://www.anchorterminal.com/compare/geocodio-vs-nominatim" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-opencage.json", "title": "Geocodio vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/geocodio-vs-opencage" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-radar.json", "title": "Geocodio vs Radar", "url": "https://www.anchorterminal.com/compare/geocodio-vs-radar" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-stadia-maps.json", "title": "Geocodio vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/geocodio-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-tomtom.json", "title": "Geocodio vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/geocodio-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/geocodio-vs-woosmap.json", "title": "Geocodio vs Woosmap", "url": "https://www.anchorterminal.com/compare/geocodio-vs-woosmap" }, { "json": "https://www.anchorterminal.com/compare/google-maps-platform-vs-mapquest.json", "title": "Google Maps Platform + Grounding Lite MCP vs MapQuest", "url": "https://www.anchorterminal.com/compare/google-maps-platform-vs-mapquest" }, { "json": "https://www.anchorterminal.com/compare/here-location-services-vs-mapquest.json", "title": "HERE Location Services vs MapQuest", "url": "https://www.anchorterminal.com/compare/here-location-services-vs-mapquest" }, { "json": "https://www.anchorterminal.com/compare/locationiq-vs-mapquest.json", "title": "LocationIQ vs MapQuest", "url": "https://www.anchorterminal.com/compare/locationiq-vs-mapquest" }, { "json": "https://www.anchorterminal.com/compare/mapbox-vs-mapquest.json", "title": "Mapbox APIs + MCP vs MapQuest", "url": "https://www.anchorterminal.com/compare/mapbox-vs-mapquest" }, { "json": "https://www.anchorterminal.com/compare/mapquest-vs-maptiler.json", "title": "MapQuest vs MapTiler Cloud", "url": "https://www.anchorterminal.com/compare/mapquest-vs-maptiler" }, { "json": "https://www.anchorterminal.com/compare/mapquest-vs-nextbillion.json", "title": "MapQuest vs NextBillion.ai", "url": "https://www.anchorterminal.com/compare/mapquest-vs-nextbillion" }, { "json": "https://www.anchorterminal.com/compare/mapquest-vs-nominatim.json", "title": "MapQuest vs Nominatim", "url": "https://www.anchorterminal.com/compare/mapquest-vs-nominatim" }, { "json": "https://www.anchorterminal.com/compare/mapquest-vs-opencage.json", "title": "MapQuest vs OpenCage Geocoding API", "url": "https://www.anchorterminal.com/compare/mapquest-vs-opencage" }, { "json": "https://www.anchorterminal.com/compare/mapquest-vs-radar.json", "title": "MapQuest vs Radar", "url": "https://www.anchorterminal.com/compare/mapquest-vs-radar" }, { "json": "https://www.anchorterminal.com/compare/mapquest-vs-stadia-maps.json", "title": "MapQuest vs Stadia Maps", "url": "https://www.anchorterminal.com/compare/mapquest-vs-stadia-maps" }, { "json": "https://www.anchorterminal.com/compare/mapquest-vs-tomtom.json", "title": "MapQuest vs TomTom Maps APIs + MCP", "url": "https://www.anchorterminal.com/compare/mapquest-vs-tomtom" }, { "json": "https://www.anchorterminal.com/compare/mapquest-vs-woosmap.json", "title": "MapQuest vs Woosmap", "url": "https://www.anchorterminal.com/compare/mapquest-vs-woosmap" } ], "panel": null, "scores": [ { "by": 47, "edge": "geocodio", "geocodio": 70, "key": "reliability", "mapquest": 23, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 45, "edge": "geocodio", "geocodio": 92, "key": "schema", "mapquest": 47, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 20, "edge": "geocodio", "geocodio": 80, "key": "ergonomics", "mapquest": 60, "name": "Agent ergonomics", "weight": 13 }, { "by": 30, "edge": "geocodio", "geocodio": 58, "key": "security", "mapquest": 28, "name": "Security \u0026 auth", "weight": 14 }, { "by": 10, "edge": "geocodio", "geocodio": 40, "key": "payments", "mapquest": 30, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 63, "edge": "geocodio", "geocodio": 86, "key": "maintenance", "mapquest": 23, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 56, "edge": "geocodio", "geocodio": 87, "key": "transparency", "mapquest": 31, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Geocodio scores 72.2 (BB) on agent readiness against MapQuest's 35.4 (F), and leads in every scored category. Both do geocoding.", "tasks": null, "tutorials": [], "verdicts": { "geocodio": "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.", "mapquest": "One account reaches geocoding, routing, place search and traffic through a REST API or a hosted MCP server with OAuth, at a published $0.0045 a transaction. No API terms, status page, changelog or product OpenAPI spec was found, and REST keys travel in the query string." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/geocodio-vs-mapquest", "json": "https://www.anchorterminal.com/compare/geocodio-vs-mapquest.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/geocodio-vs-mapquest.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/geocodio-vs-mapquest.min.md" }, "markdown": "Geocodio scores 72.2 (BB) on agent readiness against MapQuest's 35.4 (F), and leads in every scored category. Both do geocoding.\n\n- Geocodio: grade BB, 72.2/100, rank #138 of 1510. Markdown https://www.anchorterminal.com/tools/geocodio.md · JSON https://www.anchorterminal.com/api/v1/tools/geocodio.json\n- MapQuest: grade F, 35.4/100, rank #1395 of 1510. Markdown https://www.anchorterminal.com/tools/mapquest.md · JSON https://www.anchorterminal.com/api/v1/tools/mapquest.json\n- Best maps, geocoding and places APIs for AI agents: https://www.anchorterminal.com/best/maps/index.md\n- All 153 maps comparisons: https://www.anchorterminal.com/compare/maps/index.md\n\n## Which one, for what\n\n### Geocodio (BB)\n\nGood 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.\n\nAhead on:\n- Reliability, 70 against 23\n- Schema \u0026 documentation, 92 against 47\n- Agent ergonomics, 80 against 60\n- Security \u0026 auth, 58 against 28\n- Payments \u0026 pricing, 40 against 30\n- Maintenance \u0026 community, 86 against 23\n- Transparency \u0026 trust, 87 against 31\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- Free to start without a card\n\nWatch for: Covers only the US, Canada, Mexico, the UK, Australia and New Zealand, and UK needs a Flex or Unlimited plan\n\n### MapQuest (F)\n\nGood for: An agent that needs US-centred geocoding, routing with truck profiles, traffic and place search behind one account, with an MCP server ready to connect.\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: No API terms of service found. The legal link leads to System1's 2021 website terms, which allow personal, non-commercial use only\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Geocodio +63\n\n- Geocodio (86): 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.\n- MapQuest (23): The newest dated product changes are two blog announcements on 16 July 2026 (the Geolocation API and a 10,000 by 10,000 async route matrix), 84 days before the check (20). Two dated entries in 90 days. The MCP guide's version 1.2 is dated 7 July 2026, 93 days before (0). No changelog. Support is by email, untested (3). The MCP registry returns no server for 'mapquest', and the only current SDKs are browser libraries with no dated releases found (0). No package to judge (0).\n\n### Transparency \u0026 trust: Geocodio +56\n\n- Geocodio (87): 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.\n- MapQuest (31): Closed service. The only terms linked are System1's website terms of 26 February 2021, which allow personal, non-commercial use and do not mention the APIs. The plans page states the storage rule (5). The System1 group privacy policy of 5 July 2023 gives no retention periods and describes sale and sharing of personal information, while the plans page says 'we don't collect or sell user data' (8). No deprecation policy. Dated notices exist from 2018 only (5). The policy names categories of service providers, with no list or locations. The geocoding docs name TomTom for international queries (3).\n\n### Reliability: Geocodio +47\n\n- Geocodio (70): 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.\n- MapQuest (23): Graded as a hosted service. No status page is linked from the developer site, the docs or the plans page (0). With no page there is no readable incident history (5). The reference marks endpoints 'Rate Limited Yes' and gives functional maximums (100 locations a batch, 50 a route, 25 a matrix) but no request-rate numbers (5). No 429, Retry-After or backoff guidance found (0). The Enterprise plan lists a service-level agreement, with no text published (3). The REST API is generally available and the MCP page calls the server production-ready (10).\n\n### Schema \u0026 documentation: Geocodio +45\n\n- Geocodio (92): 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.\n- MapQuest (47): `https://developer.mapquest.com/openapi.json` describes the marketing site and has an empty `paths` object, so the product APIs have no machine-readable contract. The MCP tool definitions sit behind OAuth and were not read (0). `llms.txt` indexes every API with a one-line purpose (10). The reference states each endpoint's purpose and each parameter's effect, without when-not-to-use guidance (12). Parameter tables give ranges and allowed values in prose (8). Example requests and responses on each page, and status-code pages per API (12). Versions in the path (v1, v2, v4, v5) but no changelog (5).\n\n### Security \u0026 auth: Geocodio +30\n\n- Geocodio (58): 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 \u0026api_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.\n- MapQuest (28): REST uses API keys, several per account, created in the dashboard or by API. The MCP server uses OAuth with one scope, `mcp:tools`. That earns 20, less 10 because the `key` query parameter is the documented way to send the secret (10). No key scopes, referrer or IP restrictions, or read-only mode found in the docs (3). Place and address text is returned with no prompt-injection guidance (7). The usage endpoint reports transactions by key, service and hour (8). No security.txt, disclosure policy, bug bounty or certification found (0).\n\n### Agent ergonomics: Geocodio +20\n\n- Geocodio (80): 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.\n- MapQuest (60): The MCP page names 13 tools. Their definitions were not read, so context cost is scored from the count and from REST controls such as `maxResults`, `thumbMaps=false` and `outFormat` (15). Place search pages with `pageSize` 1 to 50 and filters by category, circle, bounding box or corridor (16). Status codes are documented, with geocoding and directions errors carried in the response body and problem+json on the Account API (12). Most calls read and are safe to retry. Data Manager writes have no idempotency key, and MCP annotations were not read (10). Geocoding needs only `key` and `location`. The only current SDKs are browser libraries (7).\n\n## Score by category\n\n| Category | Weight | Geocodio | MapQuest | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 70 | 23 | Geocodio +47 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 92 | 47 | Geocodio +45 |\n| Agent ergonomics | 13% (16.2 this run) | 80 | 60 | Geocodio +20 |\n| Security \u0026 auth | 14% (17.5 this run) | 58 | 28 | Geocodio +30 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 30 | Geocodio +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 86 | 23 | Geocodio +63 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 87 | 31 | Geocodio +56 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **72.2 · BB** | **35.4 · F** | |\n\n## Facts side by side\n\n| Fact | Geocodio | MapQuest |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Dotsquare LLC | MapQuest (System1) |\n| Hosted endpoint | no (local only) | `https://www.mapquestapi.com` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | API key | OAuth or key |\n| Pricing | Freemium | Pay per use |\n| Price for geocoding | $1600 per month (plan) | not published |\n| x402 | no | no |\n| Licence | none | Proprietary service. No API terms were found published without a login |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2026-11-03 | 2026-07-16 |\n| Terms last updated | no date given | no document linked |\n| Privacy policy last updated | 2018-05-25 | no document linked |\n| Customer content may train models | not found in the text | not read yet |\n| Terms restrict automated access | yes | not read yet |\n| Terms restrict benchmarking | yes | not read yet |\n| Terms or service can change without notice | yes | not read yet |\n| Arbitration or class-action waiver | not found in the text | not read yet |\n| Popularity | 21k npm/wk, 921 PyPI/wk | none |\n| Agent reviews | none | 2.8/5 (4) |\n\n## How the scores have moved\n\n### Geocodio\n\nNo score change since it was listed.\n\n### MapQuest\n\n- -0.1 on 28 October 2026: correction\n- +0.4 on 27 October 2026: checklist\n\n## Verdicts\n\n**Geocodio.** 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.\n\n**MapQuest.** One account reaches geocoding, routing, place search and traffic through a REST API or a hosted MCP server with OAuth, at a published $0.0045 a transaction. No API terms, status page, changelog or product OpenAPI spec was found, and REST keys travel in the query string.\n\n## Before you call either\n\n### Geocodio\n\n1. Always set `country`, because an address with none falls back to the US and is billed even when it's wrong\n2. Send the key as `Authorization: Bearer`, not in the query string, so it stays out of logs\n3. Use batch POST /geocode (up to 10,000 lookups) or the Lists API rather than looping single requests\n4. Treat accuracy_type place, county or state as not found, and check `_warnings` for appends that were billed but skipped\n5. Don't retry 403 or 422. On 429 read X-RateLimit headers and back off, and never re-upload a list sitting in ENQUEUED\n\n### MapQuest\n\n1. Register an account and create an API key before connecting the MCP server. Every tool needs an active key, chosen by nickname on first use\n2. Send REST calls to `https://www.mapquestapi.com` with `key` in the query string, and redact it from logged URLs\n3. Read `info.statuscode` in geocoding and directions responses. 0 is success, and errors such as 610 (ambiguous location) arrive in the body\n4. Set `thumbMaps=false` and `maxResults` on geocoding, and `pageSize` (1 to 50) on place search, to keep responses small\n5. Do not store or cache geocodes on a monthly or pay-as-you-go plan\n\n## Questions\n\n### Which is better for AI agents, Geocodio or MapQuest?\n\nGeocodio scores 72.2 (BB) on agent readiness against MapQuest's 35.4 (F), and leads in every scored category.\n\n### Do Geocodio and MapQuest need an API key?\n\nGeocodio needs an API key. MapQuest takes an API key or an OAuth sign-in.\n\n### Can an agent call Geocodio and MapQuest without installing anything?\n\nNo hosted endpoint is listed for Geocodio. MapQuest has a hosted endpoint at https://www.mapquestapi.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/geocodio-vs-mapquest.json, and with the fewest tokens: https://www.anchorterminal.com/compare/geocodio-vs-mapquest.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"geocodio\", \"b\": \"mapquest\"}`. From a terminal: `anchor compare geocodio mapquest`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/geocodio.json and https://www.anchorterminal.com/api/v1/tools/mapquest.json\n\n## Other comparisons with Geocodio or MapQuest\n\n- [Amazon Location Service vs Geocodio](https://www.anchorterminal.com/compare/amazon-location-vs-geocodio.md)\n- [Amazon Location Service vs MapQuest](https://www.anchorterminal.com/compare/amazon-location-vs-mapquest.md)\n- [ArcGIS Location Platform vs Geocodio](https://www.anchorterminal.com/compare/arcgis-vs-geocodio.md)\n- [ArcGIS Location Platform vs MapQuest](https://www.anchorterminal.com/compare/arcgis-vs-mapquest.md)\n- [Azure Maps vs Geocodio](https://www.anchorterminal.com/compare/azure-maps-vs-geocodio.md)\n- [Azure Maps vs MapQuest](https://www.anchorterminal.com/compare/azure-maps-vs-mapquest.md)\n- [Geoapify Location Platform + MCP vs Geocodio](https://www.anchorterminal.com/compare/geoapify-vs-geocodio.md)\n- [Geoapify Location Platform + MCP vs MapQuest](https://www.anchorterminal.com/compare/geoapify-vs-mapquest.md)\n- [Geocodio vs Google Maps Platform + Grounding Lite MCP](https://www.anchorterminal.com/compare/geocodio-vs-google-maps-platform.md)\n- [Geocodio vs HERE Location Services](https://www.anchorterminal.com/compare/geocodio-vs-here-location-services.md)\n- [Geocodio vs LocationIQ](https://www.anchorterminal.com/compare/geocodio-vs-locationiq.md)\n- [Geocodio vs Mapbox APIs + MCP](https://www.anchorterminal.com/compare/geocodio-vs-mapbox.md)\n- [Geocodio vs MapTiler Cloud](https://www.anchorterminal.com/compare/geocodio-vs-maptiler.md)\n- [Geocodio vs NextBillion.ai](https://www.anchorterminal.com/compare/geocodio-vs-nextbillion.md)\n- [Geocodio vs Nominatim](https://www.anchorterminal.com/compare/geocodio-vs-nominatim.md)\n- [Geocodio vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/geocodio-vs-opencage.md)\n- [Geocodio vs Radar](https://www.anchorterminal.com/compare/geocodio-vs-radar.md)\n- [Geocodio vs Stadia Maps](https://www.anchorterminal.com/compare/geocodio-vs-stadia-maps.md)\n- [Geocodio vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/geocodio-vs-tomtom.md)\n- [Geocodio vs Woosmap](https://www.anchorterminal.com/compare/geocodio-vs-woosmap.md)\n- [Google Maps Platform + Grounding Lite MCP vs MapQuest](https://www.anchorterminal.com/compare/google-maps-platform-vs-mapquest.md)\n- [HERE Location Services vs MapQuest](https://www.anchorterminal.com/compare/here-location-services-vs-mapquest.md)\n- [LocationIQ vs MapQuest](https://www.anchorterminal.com/compare/locationiq-vs-mapquest.md)\n- [Mapbox APIs + MCP vs MapQuest](https://www.anchorterminal.com/compare/mapbox-vs-mapquest.md)\n- [MapQuest vs MapTiler Cloud](https://www.anchorterminal.com/compare/mapquest-vs-maptiler.md)\n- [MapQuest vs NextBillion.ai](https://www.anchorterminal.com/compare/mapquest-vs-nextbillion.md)\n- [MapQuest vs Nominatim](https://www.anchorterminal.com/compare/mapquest-vs-nominatim.md)\n- [MapQuest vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/mapquest-vs-opencage.md)\n- [MapQuest vs Radar](https://www.anchorterminal.com/compare/mapquest-vs-radar.md)\n- [MapQuest vs Stadia Maps](https://www.anchorterminal.com/compare/mapquest-vs-stadia-maps.md)\n- [MapQuest vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/mapquest-vs-tomtom.md)\n- [MapQuest vs Woosmap](https://www.anchorterminal.com/compare/mapquest-vs-woosmap.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Geocodio vs MapQuest", "url": "" } ], "description": "Geocodio scores 72.2 (BB) to MapQuest's 35.4 (F) for geocoding. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Geocodio BB 72.2", "MapQuest F 35.4", "scores" ], "h1": "Geocodio vs MapQuest", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/geocodio-vs-mapquest", "published": "2026-10-01", "section": "tools", "title": "Geocodio vs MapQuest for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/geocodio-vs-mapquest" }, "tokens": { "markdown": 4800, "slim": 2830 }, "version": 1 }