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.

Pod Point publishes 1 API on the APIs.io network. Tagged areas include Energy, United Kingdom, EV Charging, Electric Vehicles, and Utilities.

Pod Point’s developer surface includes engineering blog, support, authentication, code examples, and 20 more developer resources.

🌐 Visit website 📡 Source on GitHub

28.6/100 thin ▬ flat Agent 7/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

1 APIs

Energy United Kingdom EV Charging Electric Vehicles Utilities Electricity OCPI Charge Point Operator Smart Charging Grid

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 28.6/100 · thin

Contract Quality 1.4 / 21

Developer Ergonomics 6.7 / 17

Access Clarity 3.6 / 17

Operational Transparency 1.5 / 11

Contract Governance 1.9 / 10

Discoverability 6.5 / 9

Regulatory Posture 6.3 / 15

Agent readiness — 7/100 · agent aware

Machine-Readable Contract 0 / 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 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 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

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

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.

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

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 github.com/api-evangelist/pod-point: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

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

Example request and response payloads for these APIs.

Pod Point Ocpi Health

4 fields

EXAMPLE

Pod Point Ocpi Unauthorized

3 fields

EXAMPLE

Pod Point Ocpi Version Detail

4 fields

EXAMPLE

Pod Point Ocpi Versions

4 fields

EXAMPLE

Security Posture 3

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

Pod Point Authentication

http · 3 schemes

SECURITY

Pod Point Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Pod Point Vulnerability Disclosure

Hackerone · security.txt · contact published

SECURITY

Resources

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

LLMsTxt

LLMsTxt

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conformance

Conventions

ErrorCatalog

Lifecycle

DataModel

Components

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Examples

Packages

SDKs

Access & Security 5

Authentication, authorization, and security posture

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

Security

SecurityTxt

Authentication

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 4

The organization behind the API

Website

Website

Blog

Blog

LinkedIn

Careers

Careers

Source (apis.yml)

aid: pod-point
url: https://raw.githubusercontent.com/api-evangelist/pod-point/refs/heads/main/apis.yml
name: Pod Point
kind: company
description: '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.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-09-03'
  method: derived
image: https://podenergy.com/themes/custom/podpoint/images/favicon-96x96.png
tags:
- Energy
- United Kingdom
- EV Charging
- Electric Vehicles
- Utilities
- Electricity
- OCPI
- Charge Point Operator
- Smart Charging
- Grid
created: '2026-07-27'
modified: '2026-07-27'
specificationVersion: '0.23'
apis:
- aid: pod-point:pod-point-ocpi-cpo-api
  name: Pod OCPI 2.2.1 CPO API
  description: '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 Point Regulations 2023 for charge point reference and
    availability data. Version discovery is anonymous: GET /ocpi/cpo/versions returned HTTP 200 on 2026-07-27 advertising
    version 2.2.1, and GET /ocpi/cpo/2.2.1 returned HTTP 200 enumerating cdrs, credentials, locations, sessions and tariffs
    in the SENDER role plus commands, credentials and tokens in the RECEIVER role. Every one of those data modules returns
    HTTP 401 with OCPI status_code 2000 Unauthorized to an anonymous caller; access requires an OCPI credentials token exchanged
    bilaterally with Pod. Pod publishes no human documentation, no OpenAPI and no onboarding path for this API — the module
    list the service returns about itself is the only contract.'
  humanURL: https://ocpi.podenergy.com/ocpi/cpo/versions
  baseURL: https://ocpi.podenergy.com/ocpi/cpo/2.2.1
  tags:
  - EV Charging
  - OCPI
  - Roaming
  - Charge Point Operator
  - Open Data
  - United Kingdom
  properties:
  - type: APIReference
    url: https://ocpi.podenergy.com/ocpi/cpo/versions
  - type: Documentation
    url: https://github.com/ocpi/ocpi
  - type: Specification
    url: https://evroaming.org/wp-content/uploads/2024/11/OCPI-2.2.1-d2.pdf
  - type: Regulation
    url: https://www.legislation.gov.uk/uksi/2023/1168/contents/made
common:
- type: VulnerabilityDisclosure
  url: security/pod-point-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/pod-point-domain-security.yml
- type: Website
  url: https://podenergy.com/
- type: Blog
  url: https://podenergy.com/news
- type: Support
  url: https://help.pod-point.com/
- type: GitHubOrganization
  url: https://github.com/Pod-Point
- type: LinkedIn
  url: https://www.linkedin.com/company/podpoint
- type: Careers
  url: https://careers.pod-point.com/
- type: Security
  url: https://podenergy.com/security
- type: SecurityTxt
  url: well-known/pod-point-security.txt
- type: WellKnown
  url: well-known/pod-point-well-known.yml
- type: Authentication
  url: authentication/pod-point-authentication.yml
- type: Conformance
  url: conformance/pod-point-conformance.yml
- type: Conventions
  url: conventions/pod-point-conventions.yml
- type: ErrorCatalog
  url: errors/pod-point-error-codes.yml
- type: Lifecycle
  url: lifecycle/pod-point-lifecycle.yml
- type: DataModel
  url: data-model/pod-point-data-model.yml
- type: Examples
  url: examples/pod-point-examples.yml
- type: Packages
  url: packages/pod-point-packages.yml
- type: SDKs
  url: packages/pod-point-packages.yml
- type: Components
  url: components/pod-point-components.yml
- type: LLMsTxt
  url: llms/pod-point-llms.txt
- type: TermsOfService
  url: https://podenergy.com/general-terms-and-conditions
- type: PrivacyPolicy
  url: https://podenergy.com/legal/privacy-notice
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

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/pod-point"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/pod-point/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.