Geoapify through Squiid

What Geoapify is

Geoapify is a location platform built on OpenStreetMap and other open datasets. It covers forward and reverse geocoding and address autocomplete, routing with turn-by-turn directions, route matrices, map matching and multi-stop route planning, isochrones and isodistances, a Places API with categories and place details, postcode and administrative-boundary lookups, IP geolocation, and static map images. Everything is metered in credits: a geocode is one credit, a route matrix is sources times targets, a 15-minute isochrone is three, so the cost of a request is predictable before you send it.

It is the practical pick for AI-coded apps that need more than geocoding but do not want a Google-scale contract: delivery and field-service tools that compute matrices and plan multi-stop routes, store locators with reachability rings, dashboards that colour administrative areas, and any pipeline that geocodes a table once and keeps the coordinates. Geoapify's terms explicitly allow caching, storing and redistributing results, which is the restriction that trips up projects on the big-brand providers.

Why connect it through Squiid

Geoapify is coming soon on Squiid. Requests go to https://api.squiid.io/v1/geoapify/... with Authorization: Bearer $SQUIID_API_KEY, with clients working by base URL swap (gateway convention), and each request meters the same credits Geoapify counts, priced at the effective rate of Geoapify's plan on one Squiid invoice. Map tiles for interactive maps stay a direct, browser-side concern; the gateway serves the server-side APIs and static map images. OpenStreetMap attribution applies to what you display.

• One account, one key, one bill, one dashboard. Geoapify sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Geoapify credentials. Your code carries SQUIID_API_KEY, so GEOAPIFY_API_KEY never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Geoapify costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• Geocoding, reverse geocoding and address autocomplete
• Routing, route matrices, map matching and route planning
• Isochrones, places, boundaries and IP geolocation
• Results you may cache, store and redistribute
• Geoapify credit pricing at the plan's effective rate, no markup

How to connect Geoapify

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces GEOAPIFY_API_KEY
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/geoapify/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Geoapify charges a monthly fee by daily credit allowance; Squiid meters the same credits per request at the plan's effective rate. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Geoapify usage, with no markup and no per-request margin.

Geoapify has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Geoapify usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Nothing to move: Geoapify is usage-metered, so leaving means creating your own Geoapify key and pointing the client at it. Squiid never owns your code, your schema or your domain, and the gateway speaks Geoapify's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Geoapify through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Geoapify usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.