canonical: https://jentic.com/apis/radar.com/radar

# Radar API

Radar provides location infrastructure for mobile and web apps. Use the Radar API for geofencing, geocoding, routing, tracking, and search. The API exposes 13 endpoints secured with apiKey authentication.

## For AI agents

Programmatically track a location update, forward geocode. Covers 13 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for analytics only.

## Capabilities

- Track a location update
- Forward geocode
- Reverse geocode
- IP geocode
- Autocomplete
- Search users

## Use cases

### Analytics Operations

Use the Radar API to perform analytics operations programmatically. The API provides 13 endpoints covering core functionality including track a location update, forward geocode, reverse geocode.

Example prompt: Call POST /track to track a location update

### Automated Tracking Management

Automate tracking operations by combining multiple Radar API endpoints. Agents can forward geocode and then reverse geocode in a single workflow.

Example prompt: Call GET `/geocode/forward` to forward geocode, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Radar API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'track a location update', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/track` | Track a location update |
| GET | `/geocode/forward` | Forward geocode |
| GET | `/geocode/reverse` | Reverse geocode |
| GET | `/geocode/ip` | IP geocode |
| GET | `/search/autocomplete` | Autocomplete |
| GET | `/search/users` | Search users |
| GET | `/search/geofences` | Search geofences |
| GET | `/search/places` | Search places |

## Key resources

- **Tracking** — Track user location updates
- **Geocoding** — Forward and reverse geocoding
- **Search** — Search for users, geofences, and places
- **Routing** — Distance, matrix, and directions routing
- **Address Validation** — Address validation and verification

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 57 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 48 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 44 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 72 / 100
- **View full report:** https://jentic.com/apis/radar.com/radar/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Radar API by hand means learning its Authorization header key auth, choosing between the publishable and secret keys, targeting the api.radar.io host, and handling retries across its geocoding and search operations yourself. Through Jentic you install once, import Radar from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Radar drives its geocoding and search through request parameters rather than a resource id in the path, so limit the agent to the operations it needs, such as forward geocoding or place search. You choose which operations are allowed, so a write like tracking a location is not included unless you add it.
- **Credential handling:** Your Radar key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'forward geocode an address' or 'reverse geocode coordinates', and Jentic returns the matching Radar operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

### What authentication does the Radar API use?

The Radar API uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I track a location update with the Radar API?

Yes. Use the POST /track endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Radar API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I track a location update through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'track a location update'. Jentic returns the matching Radar API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Radar API have?

The Radar API exposes 13 endpoints covering tracking, geocoding, search operations.

### Can I limit what my agent is allowed to do with the Radar API?

Yes. Because you run Jentic One yourself, your own rules decide which Radar operations the agent may call and which credentials it uses. Radar drives its geocoding and search through request parameters rather than a resource id in the path, so you can allow only the read operations an agent needs, such as forward geocode, reverse geocode, or place search, and leave out a write like POST /track that records a location update. The agent can call the Radar operations you permit and nothing else.