Pod Point
Pod Point — trading as Pod since its February 2026 rebrand, with pod-point.com now 301-redirecting to podenergy.com — is a British electric vehicle charging company founded in London in 2009 and wholly owned by EDF since its delisting from the London Stock Exchange in August 2025. It sells and installs home, workplace and fleet chargers, operates the third-largest public charging network in the United Kingdom across Tesco and Lidl car parks, and acquired depot-charging specialist EO Charging in May 2026. It sits on the demand side of the UK electricity value chain, between the driver and the electricity supplier, as a Charge Point Operator rather than a metering, network or settlement body. Its API posture is narrow but real and honestly split: there is no developer portal, no OpenAPI, no Swagger and no consumer data API, yet a live OCPI 2.2.1 Charge Point Operator service runs at ocpi.podenergy.com whose version negotiation answers anonymously and enumerates a full module set, while every data module — locations, tariffs, sessions, CDRs — returns 401 Unauthorized without a bilaterally exchanged OCPI credentials token. Britain's Public Charge Point Regulations 2023 name OCPI 2.2.1 as the vehicle for open charge point data; the plumbing that regulation names is verifiably in place at Pod, but the open part of it is not obtainable anonymously from outside, and the company publishes no open data page, no OCPI token policy and no developer onboarding of any kind.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Pod Point the way a machine reads it — 8 machine-readable artifacts across 1 API, 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 — Pod Point scores 28.6/100 (thin), with a separate agent-readiness read of 7/100 (agent aware). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Pod Point's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/pod-point/"
title="Pod Point on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/pod-point.svg"
alt="Pod Point Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/pod-point/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/pod-point/"
title="Pod Point on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/pod-point/card.svg"
alt="Pod Point Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Pod Point
Each block below is one kind of artifact we hold for Pod Point. 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 1
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.
Pod OCPI 2.2.1 CPO API
Pod's Open Charge Point Interface (OCPI) 2.2.1 service in the Charge Point Operator role, used for e-mobility roaming and as the technical vehicle named by the UK Public Charge ...
Examples 4
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 3
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.
Resources
Every other property we hold for Pod Point — 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.
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/pod-point · machine-readable index on apis.io
This is an independent, third-party profile of Pod Point, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.