Telenav

Telenav is a connected-car and location-based services company that powers in-vehicle navigation (VIVID NAV), infotainment (VIVID IVI), and in-car commerce (VIVID COMMERCE) for automotive partners including Daimler, Ford, GM, Toyota, and Xpeng. Its developer surface centers on the Entity Service REST API for location-aware semantic search, auto-suggest predictions, entity detail lookup, and discovery including EV charge-station search, alongside partner-distributed navigation and driver-intelligence SDKs documented at docs.telenav.com and open-source Java tooling on Maven Central.

Telenav is listed with 1 API on the APIs.io network. Tagged areas include Mapping, Navigation, Location, Search, and Automotive.

The Telenav catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Telenav’s developer surface includes documentation, API reference, getting-started guide, engineering blog, support, authentication, changelog, and 17 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

39.7/100 developing ▬ flat Agent 23/100 agent aware Front door AI 1/6 silent Heartbeat 0/100 dormant saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 API

Mapping Navigation Location Search Automotive Connected Vehicles EV Charging Points of Interest

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 39.7/100 · developing

Contract Quality 8.3 / 21

Developer Ergonomics 12.1 / 17

Access Clarity 3.6 / 17

Operational Transparency 2.9 / 11

Contract Governance 0.5 / 10

Discoverability 5.5 / 9

Regulatory Posture 3.1 / 15

Agent readiness — 23/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Energy & Utilities regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/telenav/"><img src="https://apis.io/badge/telenav/card.svg" alt="Telenav on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

9 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 21.1 — up to +15.8 composite points
Contract Quality scores 39.0 — up to +15.3 composite points
Contract Governance scores 4.5 — up to +11.5 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/telenav/apis.yml: open an issue on github.com/api-evangelist/telenav to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
EV Charging (charging, roaming, e-mobility)	builds-on	17.2 (thin)	-	-
Zoom App Marketplace and Partner Ecosystem (builders and partners on Zoom)	builds-on	17.2 (thin)	-	-
Overture Maps Foundation (members + data contributors)	builds-on	17.2 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Telenav Entity Service REST API

Location-based semantic search for the connected car - onebox search with category, brand, corridor, polygon, and bounding-box filters, reverse geocoding, EV charge-station sear...

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Telenav Webhooks

ASYNCAPI

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Telenav Authentication

apiKey/requestSignature · 3 schemes

SECURITY

Telenav Domain Security

HSTS · DMARC

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

Webhooks

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 2

Status, limits, changes, and where to get help

Support

Support

ChangeLog

ChangeLog

Commercial 2

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

TermsOfService

TermsOfService

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: telenav
name: Telenav
description: Telenav is a connected-car and location-based services company that powers in-vehicle navigation (VIVID NAV),
  infotainment (VIVID IVI), and in-car commerce (VIVID COMMERCE) for automotive partners including Daimler, Ford, GM, Toyota,
  and Xpeng. Its developer surface centers on the Entity Service REST API for location-aware semantic search, auto-suggest
  predictions, entity detail lookup, and discovery including EV charge-station search, alongside partner-distributed navigation
  and driver-intelligence SDKs documented at docs.telenav.com and open-source Java tooling on Maven Central.
url: https://raw.githubusercontent.com/api-evangelist/telenav/refs/heads/main/apis.yml
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://avatars.githubusercontent.com/u/3743554?v=4
x-type: company
x-source: vc-portfolio
x-backed-by:
- menlo-ventures
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
x-docs-platform: mkdocs
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-17
x-docs-hosting: aws-cloudfront
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 13
  pass: local-v1
created: '2026-07-17'
modified: '2026-07-21'
tags:
- Mapping
- Navigation
- Location
- Search
- Automotive
- Connected Vehicles
- EV Charging
- Points of Interest
tags_raw:
- Mapping
- Navigation
- Location
- Search
- Automotive
- Connected Cars
- EV Charging
- Points of Interest
- Connected Car
apis:
- name: Telenav Entity Service REST API
  description: Location-based semantic search for the connected car - onebox search with category, brand, corridor, polygon,
    and bounding-box filters, reverse geocoding, EV charge-station search, auto-suggest and word prediction, entity detail
    lookup (batch supported), and discovery of places, brands, and categories. JSON over REST, versioned under /v5/, authenticated
    with a Telenav-assigned API key plus per-request SHA-256 signature. API hosts are provisioned per automotive partner and
    are not published publicly (docs reference a {host} placeholder).
  humanURL: https://docs.telenav.com/overview/entity-rest.html
  properties:
  - type: Documentation
    url: https://docs.telenav.com/overview/entity-rest.html
  - type: Authentication
    url: https://docs.telenav.com/entity-rest/common.html
  tags:
  - Search
  - Location
  - Points of Interest
  - EV Charging
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.telenav.com
- type: DeveloperPortal
  url: https://docs.telenav.com
- type: Documentation
  url: https://docs.telenav.com
- type: APIReference
  url: https://docs.telenav.com/api-references/sdk/entity/current/index.html
- type: GettingStarted
  url: https://docs.telenav.com/entity-android/install-sdk.html
- type: Blog
  url: https://www.telenav.com/blog
- type: Support
  url: https://www.telenav.com/contact
- type: PrivacyPolicy
  url: https://www.telenav.com/legal/policies-privacy-policy
- type: TermsOfService
  url: https://www.telenav.com/legal
- type: GitHubOrganization
  url: https://github.com/Telenav
- type: DomainSecurity
  url: security/telenav-domain-security.yml
- type: Authentication
  url: authentication/telenav-authentication.yml
- type: Conventions
  url: conventions/telenav-conventions.yml
- type: ErrorCatalog
  url: errors/telenav-problem-types.yml
- type: Lifecycle
  url: lifecycle/telenav-lifecycle.yml
- type: ChangeLog
  url: changelog/telenav-changelog.yml
- type: Conformance
  url: conformance/telenav-conformance.yml
- type: Packages
  url: packages/telenav-packages.yml
- type: SDKs
  url: packages/telenav-packages.yml
- type: Sandbox
  url: sandbox/telenav-sandbox.yml
- type: Webhooks
  url: asyncapi/telenav-webhooks.yml
- type: WellKnown
  url: well-known/telenav-well-known.yml
- type: X-MCPServerCandidate
  url: mcp/telenav-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/telenav-llms.txt

Telenav API — frequently asked questions

Does Telenav have an API?

Yes. APIs.io lists 1 API from Telenav, including Telenav Entity Service REST API.

How do I authenticate with the Telenav API?

Telenav uses bearer-token authentication (apiKey/requestSignature · 3 schemes). The details are profiled on APIs.io as Telenav Authentication.

Is the Telenav API ready for AI agents?

Telenav has a Kin Score of 39.7 out of 100 (developing) and an Agent Readiness score of 22.7 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/telenav"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/telenav/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/telenav/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.