ev.energy

ev.energy is a London- and Palo-Alto-based smart electric-vehicle charging platform. Its cloud software connects EV drivers, vehicles, EVSEs (chargers), home batteries, solar inverters and utility programs so charging can be shifted to cheaper, greener periods and aggregated as grid flexibility. The company operates a consumer driver app across the UK, EU, US and Canada, a white-label platform for utilities and e-mobility businesses, an EV Flex virtual power plant product, and the Smart Charge API — a public OpenAPI 3.1 REST contract at api.ev.energy covering vehicles, EVSEs, charging sessions, schedules, tariffs, solar, home batteries, VPP dispatch, rebates and utility program enrollment.

ev.energy publishes 1 API on the APIs.io network: v2 API. Tagged areas include Company, Energy, Electric Vehicles, EV Charging, and Smart Charging.

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

ev.energy’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, and 15 more developer resources.

46.8/100 developing ▬ flat Agent 56/100 agent ready Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0
1 APIs 1 MCP Servers
CompanyEnergyElectric VehiclesEV ChargingSmart ChargingUtilitiesSustainabilityVirtual Power PlantDemand ResponseSolarHome EnergyInternet of Things

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 46.8/100 · developing
Contract Quality 13.5 / 21
Developer Ergonomics 9.6 / 17
Commercial Clarity 3.6 / 17
Operational Transparency 4.1 / 11
Governance 2.1 / 10
Discoverability 6.5 / 9
Regulatory Posture 7.5 / 15
Agent readiness — 56/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
MCP Server 12 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 7 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 6 / 6
Agent Skills 5 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 3 / 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/ev-energy: 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.

ev.energy v2 API

The official ev.energy v2 REST API. 210 operations across 180 paths covering users, vehicles, EVSEs, charging sessions, schedules, tariffs, regions, solar, solar forecasts, home...

MCP Servers 1

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

ev-energy-mcp.yml

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Ev Energy Rate Limits

1 limits

RATE LIMITS

Event Specifications 1

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

Security Posture 3

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

Ev Energy Authentication

oauth2 · 1 scheme

SECURITY

Ev Energy Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Ev Energy Vulnerability Disclosure

Hackerone · contact published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Ev Energy Scopes

35 scopes

35 scopes

SCOPES

Resources

Get Started 2

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

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 4

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: ev-energy
name: ev.energy
description: ev.energy is a London- and Palo-Alto-based smart electric-vehicle charging platform. Its cloud software connects
  EV drivers, vehicles, EVSEs (chargers), home batteries, solar inverters and utility programs so charging can be shifted
  to cheaper, greener periods and aggregated as grid flexibility. The company operates a consumer driver app across the UK,
  EU, US and Canada, a white-label platform for utilities and e-mobility businesses, an EV Flex virtual power plant product,
  and the Smart Charge API — a public OpenAPI 3.1 REST contract at api.ev.energy covering vehicles, EVSEs, charging sessions,
  schedules, tariffs, solar, home batteries, VPP dispatch, rebates and utility program enrollment.
image: https://cdn.prod.website-files.com/6278ea1f9c10c9550411fdd7/627a9ce3111e36661da5018c_ev-logo-256px.png
url: https://raw.githubusercontent.com/api-evangelist/ev-energy/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-08-12'
modified: '2026-08-12'
tags:
- Company
- Energy
- Electric Vehicles
- EV Charging
- Smart Charging
- Utilities
- Sustainability
- Virtual Power Plant
- Demand Response
- Solar
- Home Energy
- Internet of Things
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- aid: ev-energy-api-v2
  name: ev.energy v2 API
  description: The official ev.energy v2 REST API. 210 operations across 180 paths covering users, vehicles, EVSEs, charging
    sessions, schedules, tariffs, regions, solar, solar forecasts, home batteries, boundary meters, CT clamps, HEM systems,
    sites, carbon intensity, grid data, programs, rebates, subscriptions, notifications, support tickets and VPP dispatch.
    OAuth 2.0 (authorization code with PKCE, and client credentials) with 35 fine-grained scopes; RFC 9457 problem-details
    errors; RFC 5988 Link-header pagination; ULID-prefixed resource IDs.
  humanURL: https://developers.ev.energy/ev.energy-api-v2
  baseURL: https://api.ev.energy/v2
  tags:
  - EV Charging
  - Smart Charging
  - Energy
  - Vehicles
  - Solar
  - Virtual Power Plant
  properties:
  - type: OpenAPI
    url: openapi/ev-energy-api-v2-openapi.yaml
  - type: Overlay
    url: overlays/ev-energy-api-v2-overlay.yaml
  - type: Documentation
    url: https://developers.ev.energy/docs/intro
  - type: APIReference
    url: https://developers.ev.energy/ev.energy-api-v2
  - type: GettingStarted
    url: https://developers.ev.energy/docs/intro
  - type: Authentication
    url: authentication/ev-energy-authentication.yml
  - type: OAuthScopes
    url: scopes/ev-energy-scopes.yml
  - type: RateLimits
    url: rate-limits/ev-energy-rate-limits.yml
  - type: ErrorCatalog
    url: errors/ev-energy-problem-types.yml
  - type: Conventions
    url: conventions/ev-energy-conventions.yml
  - type: DataModel
    url: data-model/ev-energy-data-model.yml
  - type: Sandbox
    url: sandbox/ev-energy-sandbox.yml
  - type: Webhooks
    url: asyncapi/ev-energy-webhooks.yml
  - type: Lifecycle
    url: lifecycle/ev-energy-lifecycle.yml
  - type: Conformance
    url: conformance/ev-energy-conformance.yml
common:
- type: Website
  url: https://www.ev.energy/
- type: DeveloperPortal
  url: https://developers.ev.energy/
- type: Documentation
  url: https://developers.ev.energy/docs/intro
- type: APIReference
  url: https://developers.ev.energy/ev.energy-api-v2
- type: GettingStarted
  url: https://developers.ev.energy/docs/intro
- type: Support
  url: https://support.ev.energy/en/support/home
- type: Blog
  url: https://www.ev.energy/blog
- type: GitHubOrganization
  url: https://github.com/ev-energy
- type: TermsOfService
  url: https://www.ev.energy/terms
- type: PrivacyPolicy
  url: https://www.ev.energy/privacy
- type: Plans
  url: plans/ev-energy-plans-pricing.yml
- type: LLMsTxt
  url: llms/ev-energy-llms.txt
- type: MCPServer
  url: mcp/ev-energy-mcp.yml
- type: ToolCrosswalk
  url: mcp/ev-energy-tool-crosswalk.yml
- type: AgentSkill
  url: skills/_index.yml
- type: WellKnown
  url: well-known/ev-energy-well-known.yml
- type: SecurityTxt
  url: well-known/ev-energy-security.txt
- type: Security
  url: security/ev-energy-vulnerability-disclosure.yml
- type: VulnerabilityDisclosure
  url: security/ev-energy-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/ev-energy-domain-security.yml
x-enrichment:
  date: '2026-08-12'
  status: enriched
  artifacts_added: 28
  pass: local-v1
x-notes:
  contract_discovery: 'The API host api.ev.energy returns 403 text/plain for every unauthenticated path, including / and every
    /.well-known/* path, so host-root spec probing finds nothing there. The real OpenAPI 3.1.0 is served by the Redocly Realm
    developer portal at https://developers.ev.energy/_spec/ev.energy-API-v2.yaml — discovered from /page-data/ev.energy-api-v2/data.json,
    which names definitionId ev.energy-API-v2.yaml. Ownership is direct: developers.ev.energy, api.ev.energy and www.ev.energy
    share the registrable domain ev.energy, and the spec servers[] block names https://api.ev.energy/v2.'
  not_found: No A2A agent card on any host (canonical or legacy path). No AsyncAPI. No published idempotency contract. No
    status page, deprecation policy, changelog, CLI, embedded components, gRPC/protobuf, Postman collection, roadmap, trust
    centre, bug bounty, or first-party SDK on any public registry. No public API pricing and no self-service signup — credentials
    are provisioned by ev.energy during commercial onboarding.