Open Vehicle Monitoring System (self-hosted)

Open Vehicle Monitoring System (OVMS) is an open‑source, self‑hosted telematics platform for electric and hybrid vehicles. It provides real‑time vehicle data, remote commands, and extensive support for many car models. Users can install the system on their own hardware, integrate with MQTT, and customize dashboards. The project is community‑driven, with documentation, source code, and hardware designs publicly available.

Open Vehicle Monitoring System (self-hosted) is listed with 2 APIs on the APIs.io network. Tagged areas include Company, Telematics, Electric Vehicles, Open Source, and IoT.

The Open Vehicle Monitoring System (self-hosted) catalog on APIs.io includes 1 Spectral governance ruleset.

Open Vehicle Monitoring System (self-hosted)’s developer surface includes documentation, support, pricing, and 12 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

26.1/100 emerging Agent 21/100 agent aware Full breakdown ↓
scored 2026-10-31 · rubric v0.25.0 · Show this score on your site →

2 APIs

Company Telematics Electric Vehicles Open Source IoT Automotive

Kin Score

Kin Score How this is scored →
scored 2026-10-31 · rubric v0.25.0

Composite quality — 26.1/100 · emerging

Contract Quality 2.1 / 21

Developer Ergonomics 5.1 / 17

Access Clarity 4.0 / 17

Operational Transparency 2.3 / 11

Contract Governance 2.2 / 10

Discoverability 5.6 / 9

Regulatory Posture 3.1 / 15

Agent readiness — 21/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 4 / 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

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) 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/ovms/"><img src="https://apis.io/badge/ovms/card.svg" alt="Open Vehicle Monitoring System (self-hosted) 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
Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey)
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
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes

10 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 9.9 — up to +22.5 composite points
Access Clarity scores 23.7 — up to +15.3 composite points
Developer Ergonomics scores 30.2 — up to +14.0 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/ovms/apis.yml: open an issue on github.com/api-evangelist/ovms 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 →

APIs 2

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

OVMS HTTP API

For some time now I’ve wanted to offer an HTTP API for OVMS. The existing car↔server and server↔app protocol is cool, but requires going through some hoops (perl, whatever) to h...

Open Vehicle Monitoring System (self-hosted) API

Open Vehicle Monitoring System (self-hosted) API as documented publicly: 7 operations. Contract generated from the documentation by API Evangelist (2026-10-28); not the provider...

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Open Vehicle Monitoring System (self-hosted) API Rules

9 rules · 7 errors 1 warnings 1 info

SPECTRAL

Security Posture 2

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

Ovms Authentication

0 schemes

SECURITY

Ovms Domain Security

TLSv1.3 · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Ovms Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 2

Portal, sign-up, and the first successful call

Login

DeveloperPortal

DeveloperPortal

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgentSkill

AgentSkill

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Spectral

Spectral

Vocabulary

Vocabulary

Conformance

Conformance

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

StatusPage

StatusPage

Support

Support

Commercial 1

Pricing, plans, and the legal terms of use

Pricing

Pricing

Company 1

The organization behind the API

Website

Website

Other 2

Properties that don't map to a standard resource type

Hosts

Hosts

Vendors

Vendors

Source (apis.yml)

aid: ovms
name: Open Vehicle Monitoring System (self-hosted)
description: Open Vehicle Monitoring System (OVMS) is an open‑source, self‑hosted telematics platform for electric and hybrid
  vehicles. It provides real‑time vehicle data, remote commands, and extensive support for many car models. Users can install
  the system on their own hardware, integrate with MQTT, and customize dashboards. The project is community‑driven, with documentation,
  source code, and hardware designs publicly available.
url: https://artifacts.apis.io/ovms/apis.yml
image: https://www.openvehicles.com/sites/default/files/OVMS_logo_57.png
x-type: company
x-source: harvest:new-submission
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-28 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-28'
modified: '2026-10-28'
tags:
- Company
- Telematics
- Electric Vehicles
- Open Source
- IoT
- Automotive
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Spectral
  url: rules/ovms-rules.yml
- type: Vocabulary
  url: vocabulary/ovms-vocabulary.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Conformance
  url: conformance/ovms-conformance.yml
- type: Hosts
  url: hosts/ovms-hosts.yml
- type: Vendors
  url: vendors/ovms-vendors.yml
- type: StatusPage
  url: https://status.openvehicles.com/
- type: Login
  url: https://www.openvehicles.com/user/login
- type: DeveloperPortal
  url: https://www.openvehicles.com/developers
- type: DomainSecurity
  url: security/ovms-domain-security.yml
- type: Website
  url: https://openvehicles.com/
- type: Documentation
  url: https://docs.openvehicles.com/
- type: Support
  url: https://www.openvehicles.com/forum
- type: Pricing
  url: https://www.openvehicles.com/buy
- type: GitHubOrganization
  url: https://github.com/openvehicles
apis:
- name: OVMS HTTP API
  description: For some time now I’ve wanted to offer an HTTP API for OVMS. The existing car↔server and server↔app protocol
    is cool, but requires going through some hoops (perl, whatever) to handle the encryption and protocol level stuff. An
    HTTP API would make this much easier to externally script.
  humanURL: https://docs.openvehicles.com/en/stable/protocol_httpapi/index.html
  baseURL: https://api.openvehicles.com
  aid: ovms:ovms-http-api
- aid: ovms:ovms-api
  name: Open Vehicle Monitoring System (self-hosted) API
  description: 'Open Vehicle Monitoring System (self-hosted) API as documented publicly: 7 operations. Contract generated
    from the documentation

    by API Evangelist (2026-10-28); not the provider''s own document.'
  humanURL: https://docs.openvehicles.com/en/stable/protocol_httpapi/index.html
  baseURL: http://api.openvehicles.com:6868
  properties:
  - type: OpenAPI
    url: openapi/_ae-authored/ovms-openapi-generated.yml
    x-provenance: generated
x-coverage:
  state: unreadable
  reason: no-machine-readable-spec
  detail: The OVMS HTTP API is documented in HTML pages but no OpenAPI or other machine‑readable spec is published.
  evidence:
  - url: https://api.openvehicles.com/openapi.json
    status: 404
  checked: '2026-10-28'
x-submission-probe: 301 https://www.openvehicles.com/, 2026-10-26
x-enrichment:
  date: '2026-10-28'
  status: enriched
  artifacts_added: 23
  pass: modular-v1
  engine: identity=oss,contract=oss,surfaces=oss,docs=oss,regulatory=oss

Open Vehicle Monitoring System (self-hosted) API — frequently asked questions

Does Open Vehicle Monitoring System (self-hosted) have an API?

Yes. APIs.io lists 2 APIs from Open Vehicle Monitoring System (self-hosted), including OVMS HTTP API and Open Vehicle Monitoring System (self-hosted) API.

Is there an OpenAPI specification for the Open Vehicle Monitoring System (self-hosted) API?

Yes. APIs.io indexes 1 OpenAPI specification for Open Vehicle Monitoring System (self-hosted), each linked for download from this page.

How do I authenticate with the Open Vehicle Monitoring System (self-hosted) API?

Open Vehicle Monitoring System (self-hosted) documents its authentication (0 schemes). The details are profiled on APIs.io as Ovms Authentication.

Is the Open Vehicle Monitoring System (self-hosted) API ready for AI agents?

Open Vehicle Monitoring System (self-hosted) has a Kin Score of 26.1 out of 100 (emerging) and an Agent Readiness score of 20.8 (agent-aware), scored by API Evangelist on 2026-10-31.

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/ovms"

All providers

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

Every operation they expose

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

How their score was established

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

Discovery needs no key. Ratings and market analysis are Pro.

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.