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 publishes 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.

42.6/100 developing ▬ flat Agent 33/100 agent aware Full breakdown ↓
scored 2026-08-20 · rubric v0.12.0
AccessSelf serve
1 APIs 1 MCP Servers
MappingNavigationLocationSearchAutomotiveConnected CarsEV ChargingPoints of Interest

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-20 · rubric v0.12.0
Composite quality — 42.6/100 · developing
Contract Quality 9.6 / 21
Developer Ergonomics 12.1 / 17
Access Clarity 3.6 / 17
Operational Transparency 2.9 / 11
Contract Governance 0.5 / 10
Discoverability 5.7 / 9
Regulatory Posture 5.1 / 15
Agent readiness — 33/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
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.
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/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/telenav: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

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...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Telenav MCP Server

MCP SERVER

Event Specifications 1

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

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

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
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
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  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-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 Cars
- EV Charging
- Points of Interest
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: MCPServer
  url: mcp/telenav-mcp.yml
- type: LLMsTxt
  url: llms/telenav-llms.txt