# Radar > Radar is a location platform from Radar Labs with REST APIs for forward, reverse and IP geocoding, address autocomplete and validation, places search, distance, matrix, directions and route optimisation, plus geofencing, trip tracking and base maps. - Canonical: https://www.anchorterminal.com/tools/radar - Markdown: https://www.anchorterminal.com/tools/radar.md (~7,250 tokens) - Slim: https://www.anchorterminal.com/tools/radar.min.md (~1,530 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/radar.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-10 ## Overview **Grade D · 53.3/100 · rank #713 of 950 · #12 in Maps, geocoding & places · not agent-ready · confidence medium** ## Assessment Radar documents 36 REST operations in Markdown with a rate limit on each, and its status feed shows two short API incidents in 90 days. Access is sales-led. The pricing page says there is no free tier, every plan is an annual commitment, and no OpenAPI description or API changelog was found. ## Facts | Field | Value | | --- | --- | | Vendor | Radar Labs (https://radar.com) | | Kind | HTTP API | | Category | Maps, geocoding & places (https://www.anchorterminal.com/categories/maps) | | Transport | HTTP | | Endpoint | `https://api.radar.io/v1` | | Auth | API key · API key in the `Authorization` header, with no query-string option documented. Each project has four keys, test and live, publishable and secret. Publishable keys reach 16 of the 36 documented operations, including all geocoding, search and routing calls, and can be restricted by website domain or mobile app identifier. Secret keys reach the rest and can read or write any data. Keys come from the dashboard. Whether sign-up is self-serve was not established, because dashboard.radar.com's robots.txt closes every path. | | Pricing | Paid ($0.50 / 1k req) · Core Maps (forward, reverse and IP geocoding, autocomplete, static maps, distance, directions, matrix) starts at $0.50 per 1,000 API calls and Premium Maps (address validation, places search, route matching, route optimisation, satellite maps) at $2.00. Matrix bills per element. Every plan is an annual commitment with a monthly quota, at a rate Radar sets by quote. The pricing page says there is no free tier, and that teams can start with a technical validation period arranged with sales (https://radar.com/pricing). | | x402 | No · No x402, MPP or L402 in the API reference, the docs index or the pricing page (checked 2026-10-09). | | Licence | Proprietary service under Radar's Terms of Use. The web SDK in radarlabs/radar-sdk-js is Apache-2.0 | | Packages | npm: `radar-sdk-js` | | Source | https://github.com/radarlabs/radar-sdk-js | | Docs | https://docs.radar.com/api | | llms.txt | https://docs.radar.com/llms.txt | | Last release | 2026-09-14 | | Maps operations | Forward, reverse and IP geocoding, autocomplete, address validation, places search, distance, matrix (up to 625 routes), route matching, directions and route optimisation (up to 10 stops), all GET or POST under `https://api.radar.io/v1` | | Other operations | Track, users, trips, geofences, events, beacons and Places settings, most needing a secret key | | Rate limits | Per operation by default. 100 requests a second for geocoding and autocomplete, 50 for places search and distance, 25 for address validation, 20 for directions, 10 for matrix, route matching, route optimisation and the data operations | | Errors | JSON `meta` object with `code`, `param` and `message`. Documented codes include 402 (organisation disabled or usage exceeded), 429 and 451 (country blocklisted). Every response carries `X-Radar-Request-ID` | | Storage and attribution | Address and place results may be cached for up to 30 days. Maps must show the Radar logo and text attribution | | SDKs | Web (radar-sdk-js, v5.2.0 on 1 September 2026), iOS, Android, React Native, Flutter, Cordova, Capacitor and MAUI. No server-side client library was found in the docs | | Hosting | United States, on AWS, per the privacy notice and DPA | | Capabilities | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | | Tags | hosted, api-key, llms-txt, status-page, sales-led, annual-contract, soc2, closed-source | | JSON | https://www.anchorterminal.com/api/v1/tools/radar.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-09 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 70 | 14.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 50 | 8.1 | | Agent ergonomics | 13% | 16.2 | 65 | 10.6 | | Security & auth | 14% | 17.5 | 56 | 9.8 | | Payments & pricing | 10% | 12.5 | 10 | 1.2 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 77 | 6.7 | | Transparency & trust (editorial 51, provenance 58) | 7% | 8.8 | 55 | 4.8 | | Negative events | up to −15 | up to −15 | 9 October 2026. The Maps product page says the geocoding APIs come with 'the right to store, reuse, and export results freely' (https://radar.com/product/maps), while section 2(d) of the Terms of Use forbids storing address or point-of-interest data from the geocoding, autocomplete or place search APIs for more than 30 days (https://radar.com/terms) and the geocoding docs repeat the 30-day limit (https://docs.radar.com/maps/geocoding.md). 2 points for a claim the published terms contradict. A quoted enterprise agreement may differ and is not published. | -2 | | **Total** | | | | **53.3 → D** | ### Why each score - Reliability 70: Read with the hosted lines. status.radar.com is a Statuspage site with components for the Geocoding, Search, Routing and Maps APIs (20). Its history feed lists two incidents in the 90 days to 9 October 2026. Elevated API errors and latencies for 3 minutes on 14 July, and elevated API errors on 27 August from 19:31 to 20:34 EDT, with the share of failed requests not stated, so we read both as minor (20). Each operation states a default rate limit, 100 requests a second for geocoding down to 10 for matrix (15). 429 is documented with three meanings, with no Retry-After header or backoff guidance found, and PUT upserts keyed on `tag` and `externalId` make geofence writes repeatable (5). No SLA is published (0). The APIs carry no beta label (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 50: No OpenAPI description or other machine-readable contract was found in the docs index (0). docs.radar.com publishes llms.txt and a Markdown twin of each page, with the whole API reference in one 148 KB file (10). Descriptions say what an operation is for and sometimes when to use another, for example forward geocoding for complete addresses and autocomplete for partial ones (14). Parameters are listed with type, required or optional, ranges and allowed values, though coordinate lists travel as pipe-delimited strings and there is no schema to validate against (11). Every operation has a sample request and response, and there is one list of 12 response codes with one sample error (11). Paths carry `/v1`, and no API changelog was found (4). - Agent ergonomics 65: Read as an API. `limit` on search operations (1 to 100), `layers` and `country` filters on geocoding, and optional `geometry` on route optimisation size a response, with no field selection (14). List operations page with `limit` up to 1,000 and date cursors such as `updatedBefore` (16). Errors are JSON with `code`, `param` and `message`, and every response carries `X-Radar-Request-ID` (15). The maps operations only read. Geofence and beacon writes are PUT upserts by external ID, and no idempotency key was found for trip or user creation (10). Most maps calls need one parameter. Official SDKs cover web, iOS, Android and five cross-platform frameworks, all client-side, with no server library found (10). - Security & auth 56: Four keys a project, test and live, publishable and secret, sent in the `Authorization` header only. A secret key can read or write any data and no scopes were found. Key rotation was not read (20). Publishable keys reach only 16 client-safe operations and can be restricted by website domain or mobile app identifier, and dashboard accounts have read, write, admin and owner roles. No confirmation step for deletes (10). Results are addresses and place names from open and commercial datasets, with no prompt-injection guidance (6). Audit logs cover dashboard requests on enterprise plans, and each API response has a request ID (7). security.txt answers 404. The FAQ gives a disclosure address, and the DPA states SOC 2 Type II, a yearly third-party penetration test and a bug bounty, with the report on request. The trust centre is script-drawn and was not read (13). - Payments & pricing 10: No x402, MPP or L402 (0). The pricing page publishes starting prices without a login, $0.50 per 1,000 calls for Core Maps and $2.00 for Premium Maps, but every plan is an annual commitment at a rate set by quote (10). The pricing page says Radar has no free tier, and the technical validation period goes through sales (0). Keys come from a dashboard account, and the sign-up page was closed to us by robots.txt, so no programmatic route was found (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 77: No API changelog was found, so recency rests on Radar's own SDK. radarlabs/radar-sdk-js tagged autocomplete-v1.1.1 on 14 September 2026 and a 5.3.0 beta on 29 September, within 30 days (30). Stable tags in the last 90 days are v5.1.2 on 25 August, v5.1.3 on 31 August, v5.2.0 on 1 September and autocomplete-v1.1.1 (20). No public changelog for the API, support through a customer success manager and a feedback form, and GitHub issue replies were not read (5). Official SDKs for eight platforms are current (15). The web SDK repository carries Jest tests and CodeQL and npm publish workflows, whose results were not read (7). - Transparency & trust 55: Closed service with public Terms of Use, and an Apache-2.0 web SDK. The terms date from 24 May 2023, describe a free version the pricing page says does not exist, and paid plans run on a quoted agreement that is not published (12). The privacy notice of 13 May 2025, a public DPA and the FAQ agree on a default retention of 1 year, with 90 days for trips and 7 days for location updates in the FAQ. The privacy notice itself gives no period (22). No deprecation policy was found, and the terms let Radar change or stop the services without notice. One parameter is marked deprecated with no date (2). The DPA names AWS and MongoDB as sub-processors, and the privacy notice says hosting is in the United States (15). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (22 items): https://www.anchorterminal.com/fixes/radar.md (JSON https://www.anchorterminal.com/fixes/radar.json) ### What we couldn't check - unchecked: the trust centre at trust.radar.com, which is script-drawn - unchecked: whether sign-up at dashboard.radar.com is self-serve, and key rotation, because that host's robots.txt disallows every path - unchecked: the per-endpoint billing page the pricing FAQ links, the search, routing and maps docs pages, and the tutorials - unchecked: GitHub stars, npm downloads, issue response times and CI results for radar-sdk-js - unchecked: who registered radar.io, the domain the API answers on. Nothing was sent to the API host - Whether a quoted enterprise agreement lifts the 30-day storage limit in the public terms, as the Maps product page implies - Whether the free version the 2023 terms describe is still open to new accounts. The pricing page says there is no free tier - The share of requests that failed in the incident of 27 August 2026 is not stated on the status page - The terms forbid using the services to develop or test other geofencing, geocoding, autocomplete or place search APIs. This matters before any probe is run - The lead was right on the endpoints and key types. It did not say that the API host is api.radar.io or that access is sold by quote with no free tier ### Sources - API reference (Markdown twin): (seen 2026-10-09) - docs index for agents: (seen 2026-10-09) - FAQ, security and retention: (seen 2026-10-09) - geocoding docs, coverage and caching: (seen 2026-10-09) - web SDK docs: (seen 2026-10-09) - pricing: (seen 2026-10-09) - Terms of Use, last updated 24 May 2023: (seen 2026-10-09) - privacy notice, last updated 13 May 2025: (seen 2026-10-09) - Data Processing Addendum: (seen 2026-10-09) - Maps product page: (seen 2026-10-09) - status page: (seen 2026-10-09) - status history feed: (seen 2026-10-09) - web SDK repository, tags and licence (shallow clone): (seen 2026-10-09) - RDAP record for radar.com: (seen 2026-10-09) ## Who's behind it (provenance 58/100, checked 2026-10-09) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Radar Labs, Inc. | 20/20 | | Domain age | radar.com, registered 1994-12-16 (31 years) | 15/15 | | Endpoint on the vendor's domain | api.radar.io is not on radar.com | 0/15 | | Terms of service | read, states 4 of the 7 things a reader expects, and has 2 clauses that cost points | 3.4/10 | | Privacy policy | read, states 8 of the 8 things a reader expects | 10/10 | | Status page | status.radar.com | 10/10 | | Changelog | not found | 0/10 | | security.txt | not found | 0/10 | The privacy notice (last updated 13 May 2025) names Radar Labs, Inc., a Delaware corporation at 111 5th Ave, 12th Floor, New York, NY 10003. The Terms of Use (last updated 24 May 2023) cover the SDK and Radar's APIs and incorporate the DPA at radar.com/dpa. They describe a free version, which the pricing page says Radar does not have. Paid plans are by quote, and no enterprise agreement is published. The API answers at api.radar.io, a second domain. Nothing was sent to it, and its registrant was not checked. radar.com/.well-known/security.txt answers 404. The FAQ gives security@radar.com for reports. No API changelog was found in the docs index. The web SDK repository has dated release tags. RDAP gives 16 December 1994 as the registration date of radar.com. robots.txt answers on the day. radar.com 200 with a sitemap line only. docs.radar.com 200 with ai-input=yes. status.radar.com 200 disallowing /api/ and /embed/. dashboard.radar.com 200 disallowing every path. trust.radar.com answers the request with its page shell. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://radar.com/terms), read 2026-10-09, dated 2023-05-24, states 4 of the 7 things a reader expects. - To know. Restricts benchmarking or competitive use (costs points). "Licensee shall not (i) use the Services to develop or test other geofencing, geocoding, autocomplete, or place search APIs;" - To know. Says the terms or the service can change without notice (costs points). "Licensee acknowledges and agrees that Radar may change the form, features, components, or nature of the Services at any time in Radar's sole discretion without advance notice to Licensee, and that future versions of the Services may no longer be compatible with any given Licensee Property." - To know. Says access can be ended without notice or for any reason. "Licensee acknowledges and agrees that Radar may stop (permanently or temporarily) providing the Services (or any features within the Services) to Licensee at any time in Radar's sole discretion without prior notice or any compensation to Licensee." - To know. Requires arbitration or waives class actions. "("JAMS") then in effect, by one commercial arbitrator with substantial experience in resolving intellectual property and commercial contract disputes, who shall be selected from the appropriate list of JAMS arbitrators in accordance with such Rules." - To know. Has not been updated for three years or more. "Last updated: May 24, 2023" - Gives the date it was last updated. Last updated 2023-05-24. - Names the governing law or courts. The law of the State of New York. - Not found in the text. States a limit on its liability. - Not found in the text. Says how changes to the terms are announced. - Not found in the text. Refers to a service level or uptime commitment. - Also in the text (2026-10-08). Radar keeps a right to use and store SDK Information, the data collected from the customer's end users, to the maximum extent the law permits. "Notwithstanding anything to the contrary, Radar shall have the right to use and store the SDK Information to the maximum extent permitted by law and in accordance with Radar's Privacy Notice." - Also in the text (2026-10-08). Address and point of interest data from the geocoding, autocomplete and place search APIs may not be pre-fetched, cached, indexed or stored for more than 30 days. "pre-fetch, cache, index, or store any address or point of interest data from Radar's geocoding, autocomplete, or place search APIs for more than thirty (30) days;" - Also in the text (2026-10-08). Liability is capped at the greater of 100 US dollars or the amounts paid to Radar in the 12 months before the claim. "ANY AMOUNT, IN THE AGGREGATE, IN EXCESS OF THE GREATER OF (I) $100 OR (II) THE AMOUNTS PAID BY YOU TO RADAR IN CONNECTION WITH THE SERVICES IN THE TWELVE (12) MONTH PERIOD PRECEDING THIS APPLICABLE CLAIM" **Privacy policy** (https://radar.com/privacy), read 2026-10-09, dated 2025-05-13, states 8 of the 8 things a reader expects. - Gives the date it was last updated. Last updated 2025-05-13. - Says how long data is kept. For as long as needed, with no period named. - Gives a privacy contact. privacy@radar.com. - Says where data is transferred or stored. Relies on standard contractual clauses. ## Live (updated 2026-10-10 02:07 UTC) - Right now: up, HTTP 404, 120 ms, checked 2026-10-10 02:07 UTC (get on `https://api.radar.io/v1`) - Uptime 24h 100.0% (107 probes) · 30 days 100.0% (107 probes) · p50 124 ms · p95 233 ms - Vendor status page: none, All Systems Operational - github `radarlabs/radar-sdk-js` autocomplete-v1.1.1, released 2026-09-14 - npm `radar-sdk-js` 5.2.0 - Watching pricing - Watching privacy - Watching terms - Always current: https://www.anchorterminal.com/api/v1/live/radar.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Core Maps API calls, starting price | $0.50 | per 1,000 requests | Geocoding, autocomplete, static maps, distance, directions, matrix (per element). Annual commitment, rate set by quote | | Premium Maps API calls, starting price | $2 | per 1,000 requests | Address validation, places search, route matching, route optimisation, satellite maps. Annual commitment, rate set by quote | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - Each of the 36 documented operations states its key level and a default rate limit, from 10 to 100 requests a second - docs.radar.com publishes llms.txt and a Markdown twin of every page, including the whole API reference in one file - Statuspage history lists two API incidents in the 90 days to 9 October 2026, of 3 minutes and about an hour - Publishable keys are limited to 16 client-safe operations and can be restricted by website domain or mobile app identifier - The DPA names two sub-processors (AWS and MongoDB) and the FAQ states default retention periods ## Weaknesses - The pricing page says Radar has no free tier and every plan is an annual commitment set by quote - No OpenAPI description and no API changelog were found in the docs index - The terms cap storage of geocoding, autocomplete and place results at 30 days, while the Maps product page claims a right to store results freely - The terms of 24 May 2023 let Radar change or stop the services without notice, and still describe a free version - A secret key can read or write any project data, with no scopes found - The terms forbid using the services to develop or test other geocoding, autocomplete or place search APIs, which matters before any probe is run ## Before you call it (notes for agents) 1. Send the key in the `Authorization` header with no `Bearer` prefix, and call `https://api.radar.io/v1`, not radar.com 2. Use a publishable key for geocoding, search and routing. Keep the secret key for users, trips, geofences and beacons 3. Call `/v1/search/autocomplete` for partial addresses and place names. `/v1/geocode/forward` is documented as best for complete addresses 4. Set `units=metric` on routing calls. The default is imperial, with distances in feet 5. Treat 429 as one of three things (rate limit, no state change or selective throttling) and 402 as usage exceeded. No Retry-After header is documented 6. Do not keep geocoding, autocomplete or place results for more than 30 days ## Connect Install: ```bash npm install radar-sdk-js ``` First request: ```bash curl "https://api.radar.io/v1/geocode/forward?query=20+jay+st+brooklyn+ny" -H "Authorization: $RADAR_PUBLISHABLE_KEY" ``` Through letme (picks today, calling later): https://letme.dev/radar. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Mapbox APIs + MCP | BB | 75 | 57 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/mapbox.md | | Amazon Location Service | BB | 74.1 | 77 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/amazon-location.md | | Google Maps Platform + Grounding Lite MCP | B | 68.2 | 227 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/google-maps-platform.md | | Azure Maps | B | 67.9 | 236 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/azure-maps.md | | ArcGIS Location Platform | B | 65.4 | 320 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/arcgis.md | | Stadia Maps | B | 65.2 | 325 | geo.geocode, geo.reverse, geo.places, geo.routing, geo.tiles | no | https://www.anchorterminal.com/tools/stadia-maps.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The API reference documents 36 operations at `https://api.radar.io/v1`, 16 callable with a publishable key and 20 needing a secret key (source: ) - Pricing starts at $0.50 per 1,000 calls for Core Maps and $2.00 for Premium Maps, with annual commitments, quoted rates and no free tier (source: ) - The terms forbid storing address or point-of-interest data from the geocoding, autocomplete or place search APIs for more than 30 days, and forbid using the services to develop or test other such APIs (source: ) - Maps built on Radar must show the Radar logo and text attribution (source: ) - Default retention is 1 year for users and events, 90 days for trips and 7 days for location updates, adjustable per project (source: ) - The status history lists elevated API errors on 27 August 2026 from 19:31 to 20:34 EDT and for 3 minutes on 14 July 2026 (source: ) - #12 of 13 in Best maps, geocoding and places APIs for AI agents: https://www.anchorterminal.com/best/maps/index.md - All 78 maps comparisons: https://www.anchorterminal.com/compare/maps/index.md ## Compare - [Amazon Location Service vs Radar](https://www.anchorterminal.com/compare/amazon-location-vs-radar.md): BB 74.1 vs D 53.3 - [ArcGIS Location Platform vs Radar](https://www.anchorterminal.com/compare/arcgis-vs-radar.md): B 65.4 vs D 53.3 - [Azure Maps vs Radar](https://www.anchorterminal.com/compare/azure-maps-vs-radar.md): B 67.9 vs D 53.3 - [Geoapify Location Platform + MCP vs Radar](https://www.anchorterminal.com/compare/geoapify-vs-radar.md): C 55.3 vs D 53.3 - [Google Maps Platform + Grounding Lite MCP vs Radar](https://www.anchorterminal.com/compare/google-maps-platform-vs-radar.md): B 68.2 vs D 53.3 - [HERE Location Services vs Radar](https://www.anchorterminal.com/compare/here-location-services-vs-radar.md): C 58 vs D 53.3 - [LocationIQ vs Radar](https://www.anchorterminal.com/compare/locationiq-vs-radar.md): C 60.3 vs D 53.3 - [Mapbox APIs + MCP vs Radar](https://www.anchorterminal.com/compare/mapbox-vs-radar.md): BB 75 vs D 53.3 - [MapQuest vs Radar](https://www.anchorterminal.com/compare/mapquest-vs-radar.md): F 35.1 vs D 53.3 - [OpenCage Geocoding API vs Radar](https://www.anchorterminal.com/compare/opencage-vs-radar.md): B 69.2 vs D 53.3 - [Radar vs Stadia Maps](https://www.anchorterminal.com/compare/radar-vs-stadia-maps.md): D 53.3 vs B 65.2 - [Radar vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/radar-vs-tomtom.md): D 53.3 vs C 54.9 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on radar.com or one of its subdomains, or the README of github.com/radarlabs/radar-sdk-js. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "radar", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Radar on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Radar on Anchor Terminal](https://www.anchorterminal.com/badges/radar.svg)](https://www.anchorterminal.com/tools/radar) ``` Plain link: ```html Radar on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Radar is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/radar-dark.png - Light: https://www.anchorterminal.com/assets/share/radar-light.png