Install Jentic One Beta
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.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fradar.com%2Fradar" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fradar.com%2Fradar" | 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.
What an agent can do with Radar API.
Track a location update
Forward geocode
Reverse geocode
IP geocode
Autocomplete
GET STARTED
Search users
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
13 endpoints — radar provides location infrastructure for mobile and web apps.
METHOD
PATH
DESCRIPTION
/track
Track a location update
/geocode/forward
Forward geocode
/geocode/reverse
Reverse geocode
/geocode/ip
IP geocode
/search/autocomplete
Autocomplete
/search/users
Search users
/search/geofences
Search geofences
/search/places
Search places
/track
Track a location update
/geocode/forward
Forward geocode
/geocode/reverse
Reverse geocode
/geocode/ip
IP geocode
/search/autocomplete
Autocomplete
/search/users
Search users
/search/geofences
Search geofences
/search/places
Search places
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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.
Alternatives and complements available in the Jentic catalogue.
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 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.
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.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>