# AX Check: geoapify.com Checked 2026-10-06. Quickstart and pricing are clear, but no llms.txt index exists AGENTS.md and a README quickstart work standalone with clone-and-open steps, but llms.txt 404s and the homepage has no Markdown version. ## Onboarding needs a login ## Coding sessions All three independent sessions (DeepSeek V4.1 Flash, Kimi K3, Qwen 3.8 Max) completed and produced credit-based pricing tables spanning a free tier up to a $860/month custom plan, each naming its own assumptions like per-endpoint credit costs and rate limits. ### DeepSeek V4.1 Flash [View public run](https://agents.withgauge.com/p/runs/e16bcde6-5aa1-4aeb-b11c-97c5656a376d) · [Read transcript](https://www.ax-check.com/geoapify.com/sessions/deepseek.json) Final output gives a credits-based pricing table (Free/API 10-250/Custom) with explicit assumptions — per-endpoint credit costs, req/s limits, batch discount, and that free tier is usable in production with attribution. #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: No real Geoapify account or self-service signup occurred. The agent never created its own API key; instead it scraped a public demo key embedded in Geoapify's documentation playground HTML and used that to run live geocode/reverse-geocode/routing calls against the hosted API. This demonstrates the hosted API works, but it is not self-service onboarding (no account creation, no key issuance flow completed by the agent) and the credential was not obtained through any registration process -- it was found already embedded in public docs. Event 72: ```text apiKey=YOUR apiKey=c3da27885e3573e09e550d044bc55e22 apiKey=d548c5ed24604be6a9dd0d989631f783 ``` Event 78: ```text === key d548c5ed... === HTTP 200 {"results":[{"datasource":{"sourcename":"openstreetmap"... ``` Event 9: ```text No Geoapify key in the environment. Let me check the repo contents and whether the API is reachable. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No Geoapify API key provisioned in the sandbox**: The test environment did not supply a GEOAPIFY_API_KEY or any product credential. This is a normal missing-credential situation, not a product defect. The agent worked around it by discovering and reusing a public demo key embedded in Geoapify's own documentation playground page, rather than performing a self-service signup. Event 9: ```text No Geoapify key in the environment. Let me check the repo contents and whether the API is reachable. ``` Event 98: ```text Missing GEOAPIFY_API_KEY. Get a free key (3,000 credits/day) at https://myprojects.geoapify.com/ then: export GEOAPIFY_API_KEY=your_key_here ``` #### Suggested Changes - **Serve the pricing table as crawlable HTML instead of only client-rendered JS**: The main pricing page at geoapify.com/pricing returned almost no readable text when fetched with curl (only a handful of $ amounts and word fragments), forcing the agent to scrape the separate pricing-details page and JS bundle metadata to assemble a usable table. Verify by running curl against the pricing page without a JS renderer and confirming plan names, credits/day, and prices appear in the raw HTML response. Event 30: ```text bytes: 207999 === $ signs === 1 $860 1 $609 1 $59 1 $299 1 $179 1 $109 ``` - **Fix or remove the dead /pricing-api/ link**: A request to https://www.geoapify.com/pricing-api/ returned HTTP 404 while the sibling page /pricing-details/ returned 200 with the real content, suggesting a stale or mistyped internal link somewhere in the site referring to this path. Check internal links/sitemaps pointing to pricing-api and either redirect them to pricing-details or restore the page. Event 31: ```text ===== https://www.geoapify.com/pricing-api/ ===== HTTP 404 size 183977 ``` ### Kimi K3 [View public run](https://agents.withgauge.com/p/runs/5f7914fd-decf-4a78-aacc-ee8cc992506c) · [Read transcript](https://www.ax-check.com/geoapify.com/sessions/kimi.json) Final output states credit-based pricing with free tier (~3,000 credits/day, 5 req/s) and paid plans (~$10/mo), explicitly flagged as possibly stale and to verify at geoapify.com/pricing. #### End-to-end onboarding - **Onboarding needs a login**: Agent never obtained a Geoapify API key. An unauthenticated curl to the geocoding endpoint returned 401, confirming a key is required. The agent wrote a script that checks for GEOAPIFY_KEY in the environment and exits immediately with an error when none is found — no authenticated call was ever made. Agent explicitly asked the human to create an account and paste a key, which is a human-login blocker, not self-service onboarding. Event 7: ```text 401 ``` Event 17: ```text To run the example end-to-end, I need you to: 1. Create a free key at https://myprojects.geoapify.com (or the main site → Get API key) 2. Run: `GEOAPIFY_KEY= node /sandbox/repo/geoapify-example.js` — or paste the key here and I'll run it. ``` Event 15: ```text Set GEOAPIFY_KEY (free key at https://myprojects.geoapify.com) ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No API key available in sandbox, signup requires a human**: Geoapify requires an API key for every request (unauthenticated call returned 401). Getting a key requires browser-based signup and email account creation, which the agent could not do itself. This is a missing-credentials limitation of the test environment/product auth model, not a product defect — API key gating is normal for this kind of hosted service. Event 7: ```text 401 ``` Event 9: ```text every call requires an API key, there's no key in this environment (`curl` to the API returns 401), and signup requires a browser + email account creation that I can't perform ``` #### Suggested Changes None identified in this transcript. ### Qwen 3.8 Max [View public run](https://agents.withgauge.com/p/runs/d3958c80-2621-4da3-8f69-c41726349023) · [Read transcript](https://www.ax-check.com/geoapify.com/sessions/qwen.json) Final output lists concrete tiered pricing (Free 3,000 credits/day up to Custom $860/mo) with assumptions named — per-account credit quotas, free tier commercial use, and heavier endpoints consuming more credits. #### End-to-end onboarding - **Onboarding needs a login**: The agent never obtained a Geoapify API key. It checked the environment for credentials, found none, and explicitly stated signup requires a human email/browser signup it cannot perform. The example script and live curl calls both failed with 401 Invalid apiKey, so no authenticated product operation was ever demonstrated. Event 22: ```text The repo is empty and I have no `GEOAPIFY_API_KEY`, so I'll build the example to read the key from the environment. Creating an account requires an email/browser signup, so I can't provision a key myself — I'll flag that below. ``` Event 30: ```text {"statusCode":401,"error":"Unauthorized","message":"Invalid apiKey"} HTTP 401 ``` Event 32: ```text I can't complete a live end-to-end run: the API requires an `apiKey`, and getting one requires signing up at myprojects.geoapify.com with an email account — something I can't do from here. ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No self-service path to a Geoapify API key**: Geoapify requires signup via a hosted web console (email/browser) before any API key exists. This is a missing-credentials blocker inherent to the product's auth model, not an agent error — the agent correctly identified it couldn't create an account programmatically and stopped short of a live authenticated call. Event 22: ```text Creating an account requires an email/browser signup, so I can't provision a key myself — I'll flag that below. ``` Event 32: ```text getting one requires signing up at myprojects.geoapify.com with an email account — something I can't do from here ``` #### Suggested Changes - **Offer a programmatic or CLI-based API key provisioning option**: Geoapify currently requires signing up through the hosted web console at myprojects.geoapify.com to get an apiKey, with no documented path to generate a trial key via API or CLI. Adding a scripted/trial key endpoint (even rate-limited) would let automated agents and CI pipelines verify integration without manual signup. Check by having a fresh script fetch a key headlessly and then successfully call /v1/geocode/search with it. Event 32: ```text getting one requires signing up at myprojects.geoapify.com with an email account — something I can't do from here ``` ### Task given to each agent Help me build a simple example using Geoapify. Tell me how pricing works, and briefly tell me whether this product will be easy for you to manage. Let me know if you get blocked. If this product has no developer workflow you can act on, say so plainly and stop. Stay light: use the hosted product through its SDK or API. Do not start local service stacks or wait for long-running commands; if the quickstart requires either, say so plainly and stop. No product credentials were supplied and no purchases were authorized. ## Score: C · 62/100 (provisional) Grades come from completed site checks. Coding sessions and skipped checks do not affect the score. ### Clarity - **Failed** — Homepage answers Markdown requests ```text Homepage returned text/html for a text/markdown request; no Markdown representation offered. ``` - **Failed** — llms.txt provides an actionable documentation index ```text https://geoapify.com/llms.txt returns HTTP 404, so no documentation index exists. ``` - **Failed** — A compact guide representation exists ```text No site-published compact Markdown guide; /llms.txt returns 404 and homepage Markdown is unsupported. ``` - **Skipped** — llms.txt provides navigation guidance ```text No llms.txt body exists (404), so navigation guidance cannot be judged. ``` - **Skipped** — llms.txt mentions offered API, MCP, and skills ```text No llms.txt body exists (404), so API/MCP/skills mentions cannot be judged. ``` - **Pass** — A focused guide is directly retrievable ```text AGENTS.md and quickstart README are directly retrievable standalone Markdown guides. ``` - **Pass** — Equivalent instructions fit a token budget ```text AGENTS.md is 2.5 KB and README 16 KB, both well within the 8000-token budget. ``` - **Skipped** — Product-docs links survive format changes ```text Homepage Markdown is unsupported, so link preservation across formats cannot be measured. ``` - **Pass** — The compact guide is independently actionable ```text AGENTS.md gives concrete agent rules; README quickstart has clone, open src/index.html, API key steps. ``` - **Pass** — Install and next-step links resolve ```text Fetched install/next-step links (docs, OpenAPI, MCP, quickstart repo) all returned HTTP 200. ``` ### Onboarding - **Pass** — Docs lead to a relevant quickstart ```text Quickstart repo README lists ready-to-run examples by API category with clone-and-open steps. ``` - **Pass** — Installation commands are extractable ```text README gives concrete steps: browse examples, clone/download folder, open src/index.html. ``` - **Pass** — Code examples are available without interaction ```text Quickstart examples ship editable src HTML/JS/CSS source files viewable without interaction. ``` - **Pass** — Prerequisites and auth boundaries are explicit ```text AGENTS.md requires a Geoapify API Key section pointing to myprojects.geoapify.com. ``` ### Pricing - **Pass** — Pricing is readable without interaction ```text Pricing page lists all plan tiers, credit quotas and monthly prices in plain text. ``` - **Pass** — Prices are stated, not gated ```text Prices stated: Free, $59, $109, $179, $299, $609, Custom from $860 monthly. ``` - **Pass** — Pricing units and limits are explicit ```text Credits/day quotas, rate limits and per-API credit costs are explicit. ``` - **Pass** — Agents identify pricing and its assumptions ```text 3 of 3 sessions were judged on pricing; 0 fell short. DeepSeek V4.1 Flash: Final output gives a credits-based pricing table (Free/API 10-250/Custom) with explicit assumptions — per-endpoint credit costs, req/s limits, batch discount, and that free tier is usable in production with attribution. Kimi K3: Final output states credit-based pricing with free tier (~3,000 credits/day, 5 req/s) and paid plans (~$10/mo), explicitly flagged as possibly stale and to verify at geoapify.com/pricing. Qwen 3.8 Max: Final output lists concrete tiered pricing (Free 3,000 credits/day up to Custom $860/mo) with assumptions named — per-account credit quotas, free tier commercial use, and heavier endpoints consuming more credits. This behavioural item does not affect the fast grade. ``` ### Activation - **Pass** — An API reference or OpenAPI spec is reachable ```text OpenAPI catalog and per-API JSON specs reachable at apidocs.geoapify.com/open-api/. ``` - **Pass** — An MCP server is documented and well-formed ```text MCP server documented with endpoint, 11 tools, auth, and JSON-RPC examples. ``` - **Skipped** — A CLI install path is documented ```text No CLI install path documented in the fetched Geoapify pages. ``` - **Skipped** — SDK packages resolve on their registries ```text No registry lookup for a Geoapify SDK package was supplied. ``` - **Skipped** — Agent skills are published ```text No agent skills published; AGENTS.md is repo contributor guidance, not a skill. ``` [Full report data](https://www.ax-check.com/geoapify.com/report.json)