OpenCage through Squiid

What OpenCage is

OpenCage does one thing: it converts between addresses and coordinates. It aggregates OpenStreetMap and other open and government datasets behind a single API, returns results with confidence scores, bounding boxes, timezone and currency information, and supports many query formats including partial addresses and plus codes. Licensing is deliberately permissive, with no requirement to display the results on a specific map. The API is intentionally small: one endpoint, one key and a documented response shape that does not change between releases.

That licensing is the practical reason AI-coded projects use it. Several major providers restrict storing geocoding results or require them to be shown on their own map, which is a problem when you want to geocode a table of addresses once and keep the coordinates in your database. OpenCage is also the sensible choice for batch jobs where you need coverage and clear terms rather than places data. Batch geocoding a customer list is the canonical case, and it is usually run once as a background job rather than on every request.

Why connect it through Squiid

OpenCage is on the Squiid roadmap. When it lands, requests will go to https://api.squiid.io/v1/opencage/... with Authorization: Bearer $SQUIID_API_KEY, with clients working by base URL swap (gateway convention), and requests will meter against prepaid credits at OpenCage's listed price on one Squiid invoice. For a service that is often called in a loop over a spreadsheet, prepaid metering with a visible daily count is a more comfortable arrangement than a card and a rate limit. Results are also returned with the licence of the underlying source, which makes attribution straightforward when it is required.

• One account, one key, one bill, one dashboard. OpenCage sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the OpenCage credentials. Your code carries SQUIID_API_KEY, so OPENCAGE_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 OpenCage 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

• Forward and reverse geocoding worldwide
• Open data sources with permissive terms
• Confidence scores, timezones and bounding boxes
• Results you can store in your own database
• OpenCage list pricing, no markup

How to connect OpenCage

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 OPENCAGE_API_KEY
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

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

Pricing through Squiid

OpenCage charges a monthly fee by daily request allowance, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of OpenCage usage, with no markup and no per-request margin.

OpenCage 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 OpenCage 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: OpenCage is usage-metered, so leaving means creating your own OpenCage key and pointing the client at it. Squiid never owns your code, your schema or your domain, and the gateway speaks OpenCage'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

OpenCage 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 OpenCage 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.