Radar API
✓ Official Vendor SpecAnalyticsWeb AnalyticsapiKey13 EndpointsREST
For Agents
Programmatically track a location update, forward geocode. Covers 13 operations with apiKey authentication.
Use for: I need to track a location update, I want to forward geocode, Search for reverse geocode, Find all ip geocode
Not supported: Does not handle payments, communications, or crm — use for analytics only.
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.
Install Jentic One Beta
Connect the Radar API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Radar API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Radar API.
Track a location update
Forward geocode
Reverse geocode
IP geocode
Autocomplete
Search users
Use Cases
Patterns agents use Radar API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'track a location update', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
13 endpoints — radar provides location infrastructure for mobile and web apps.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Radar API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'track a location update') and Jentic returns the matching Radar API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Radar API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Radar API through Jentic.
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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
GET STARTED