Volteras
Volteras is the intelligence layer for OEM-grade connected vehicle data, providing a single Connect API that streams real-time telemetry, charging sessions, journeys, battery state of health, alerts, and asynchronous remote commands (charging, climate, locks) from 35+ global automakers across 340+ vehicle models, sourced directly from manufacturers rather than scrapers or hardware. Vehicles onboard via consent flow or bulk VIN upload, with a full-fidelity sandbox, Svix-powered webhooks, and OAuth 2.0 client-credentials security, serving fleet telematics, insurance, leasing, ride-hailing, and EV charging use cases across North America, Europe, and Australia. Backed by Union Square Ventures, Edenred, WEX, and Long Journey Ventures.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Volteras the way a machine reads it — 26 machine-readable artifacts across 19 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Volteras scores 52.8/100 (developing), with a separate agent-readiness read of 78/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Volteras
Each block below is one kind of artifact we hold for Volteras. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 19
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Volteras Accounts API
The Accounts API from Volteras — 4 operation(s) for accounts.
Volteras Authentication API
The Authentication API from Volteras — 2 operation(s) for authentication.
Volteras Rate Limit API
The Rate Limit API from Volteras — 1 operation(s) for rate limit.
Volteras Tags API
The Tags API from Volteras — 2 operation(s) for tags.
Volteras Vehicle Alerts API
The Vehicle Alerts API from Volteras — 1 operation(s) for vehicle alerts.
Volteras Vehicle Charging History API
The Vehicle Charging History API from Volteras — 2 operation(s) for vehicle charging history.
Volteras Vehicle Charging Schedule API
The Vehicle Charging Schedule API from Volteras — 2 operation(s) for vehicle charging schedule.
Volteras Vehicle Command Executions API
The Vehicle Command Executions API from Volteras — 15 operation(s) for vehicle command executions.
Volteras Vehicle Connection API
The Vehicle Connection API from Volteras — 4 operation(s) for vehicle connection.
Volteras Vehicle Eligibility API
The Vehicle Eligibility API from Volteras — 2 operation(s) for vehicle eligibility.
Volteras Vehicle Journeys API
The Vehicle Journeys API from Volteras — 1 operation(s) for vehicle journeys.
Volteras Vehicle Listening API
The Vehicle Listening API from Volteras — 2 operation(s) for vehicle listening.
Volteras Vehicle Manufacturer Alerts API
The Vehicle Manufacturer Alerts API from Volteras — 1 operation(s) for vehicle manufacturer alerts.
Volteras Vehicle Range API
The Vehicle Range API from Volteras — 1 operation(s) for vehicle range.
Volteras Vehicle Services API
The Vehicle Services API from Volteras — 1 operation(s) for vehicle services.
Volteras Vehicle State of Health API
The Vehicle State of Health API from Volteras — 1 operation(s) for vehicle state of health.
Volteras Vehicle Telemetry API
The Vehicle Telemetry API from Volteras — 1 operation(s) for vehicle telemetry.
Volteras Vehicle Tires API
The Vehicle Tires API from Volteras — 1 operation(s) for vehicle tires.
Volteras Vehicles API
The Vehicles API from Volteras — 5 operation(s) for vehicles.
Scroll within the panel for all 19 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
volteras-mcp.yml
MCP SERVERRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Volteras Rate Limits
RATE LIMITSEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Volteras Webhooks
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Volteras — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 3
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
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/volteras · machine-readable index on apis.io