Radar through Squiid

What Radar is

Radar is a location platform aimed at product features rather than cartography. Its APIs cover forward and reverse geocoding, address autocomplete and validation, distance and routing, and place and chain lookup, while its mobile SDKs handle the harder part: running location tracking efficiently in the background and firing geofence entry and exit events to your server through webhooks. Server-side APIs are also usable without the SDK, so a web app can geocode and validate addresses before any mobile work starts.

That makes it the pick for AI-coded apps with a physical component. Curbside pickup that notifies staff when a customer arrives, delivery tracking with automatic status changes, attendance or site check-ins, and location-triggered notifications are all geofencing problems that are unpleasant to build directly against platform location APIs, especially with battery life and permission handling in the mix. Webhooks arrive with the user, the geofence and the event type, which is enough to drive a workflow without polling anything.

Why connect it through Squiid

Radar is on the Squiid roadmap. When it is connected, server calls will go to https://api.squiid.io/v1/radar/... with Authorization: Bearer $SQUIID_API_KEY, with SDKs working by base URL swap (gateway convention), and requests and tracked users will meter against prepaid credits at Radar's listed price on one Squiid invoice. The secret key stays with Squiid while mobile clients use a publishable key, which keeps the credential that can read every user's location history out of an app bundle. Tracked user counts are the metric to watch, since they scale with adoption rather than with request volume.

• One account, one key, one bill, one dashboard. Radar sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Radar credentials. Your code carries SQUIID_API_KEY, so RADAR_SECRET_KEY, RADAR_PUBLISHABLE_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 Radar 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, autocomplete and address validation
• Geofencing with entry and exit webhooks
• Background location tracking SDKs
• Trip tracking for delivery and pickup
• Radar list pricing, no markup

How to connect Radar

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 RADAR_SECRET_KEY, RADAR_PUBLISHABLE_KEY
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

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

Pricing through Squiid

Radar charges by API requests and tracked monthly active users on plan tiers, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Radar usage, with no markup and no per-request margin.

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

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