char.gy is a British public electric-vehicle charge point operator that specialises in on-street charging for the roughly forty percent of UK households with no off-street parking, and it is best known for putting the charger inside the lamp post. Founded by Richard Stobart out of the digital agency Unboxed, it installed its first public charger in Marlow, Buckinghamshire in 2018, is now led by CEO John Lewis from Floor 5, 55 King William St, London EC4R 9AD, and is backed with £100m by Zouk Capital through the UK Government-backed Charging Infrastructure Investment Fund. Its own about page claims over 5,000 charge points and 28.3 million kg of CO2 saved, and its live open data feed returned an x-total-count of 5,409 locations on 2026-07-27. In the UK energy value chain it sits at the very end of the wire: it is not a licensed supplier, not a network operator and not a metering agent, it operates charge points on street furniture owned by local authorities — Haringey, Southwark, Brent, Barnet, Harrow, Coventry, Brighton and Hove, Richmond and Wandsworth, Enfield and others — authorising drivers, metering the session and pricing it. Britain has no consumer data-portability mandate for energy equivalent to Australia's Consumer Data Right, so nothing compels char.gy to expose an individual driver's usage or billing data through an API, and it does not: there is no consumer API, no OAuth server, no OpenID Connect discovery document and no accredited-recipient scheme anywhere on the domain. What Britain DID mandate here is open infrastructure data. The Public Charge Point Regulations 2023 (SI 2023/1168), Part 4 regulation 10(5), require every charge point operator to make reference data and availability data available to the public free of charge, in a machine readable format, and — the crucial clause — "without any requirement to agree to terms and conditions regarding the use of that data". char.gy complies, and the compliance is real rather than claimed: it publishes an OCPI-shaped Locations feed and an OCPI-shaped Tariffs feed at https://char.gy/open-ocpi/locations and https://char.gy/open-ocpi/tariffs, both of which returned HTTP 200 with application/json to a completely anonymous GET on 2026-07-27, paginated with x-total-count, x-limit and RFC 5988 Link rel="next" headers, carrying real GB*CGY*E*NNNNN EVSE identifiers, IEC 62196 Type 2 connectors, per-connector tariff_ids and time-of-day restricted pence-per-kWh price components. The posture is therefore the clean split this sector keeps producing, but rotated: market and infrastructure data wide open and genuinely ungated because a regulation forbids gating it, consumer data entirely absent because no regulation asks for it, and the commercial OCPI CPO roaming interface at /ocpi/cpo/ closed behind OCPI Token authorization for partner e-mobility service providers. There is no developer portal — the entire public documentation for the open API is a single Freshdesk help-centre article.
char.gy publishes 2 APIs on the APIs.io network: Locations API and Tariffs API. Tagged areas include Energy, United Kingdom, EV Charging, Electricity, and Utilities.
char.gy’s developer surface includes authentication, documentation, pricing, engineering blog, support, signup flow, and 24 more developer resources.
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 does not apply to this provider. The published contracts declare
no write operations, and a read-only API cannot create-or-update. The facet is excluded from this provider's
denominator entirely — not scored zero. A reference or data API is not deficient for being unable to
upsert.
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/chargy: 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 →
char.gy's commercial Open Charge Point Interface implementation in the Charge Point Operator role, used so that another network's drivers can authorise, charge and be settled on...
aid: chargy
url: https://raw.githubusercontent.com/api-evangelist/chargy/refs/heads/main/apis.yml
name: char.gy
kind: company
description: 'char.gy is a British public electric-vehicle charge point operator that specialises in on-street charging for
the roughly forty percent of UK households with no off-street parking, and it is best known for putting the charger inside
the lamp post. Founded by Richard Stobart out of the digital agency Unboxed, it installed its first public charger in Marlow,
Buckinghamshire in 2018, is now led by CEO John Lewis from Floor 5, 55 King William St, London EC4R 9AD, and is backed with
£100m by Zouk Capital through the UK Government-backed Charging Infrastructure Investment Fund. Its own about page claims
over 5,000 charge points and 28.3 million kg of CO2 saved, and its live open data feed returned an x-total-count of 5,409
locations on 2026-07-27. In the UK energy value chain it sits at the very end of the wire: it is not a licensed supplier,
not a network operator and not a metering agent, it operates charge points on street furniture owned by local authorities
— Haringey, Southwark, Brent, Barnet, Harrow, Coventry, Brighton and Hove, Richmond and Wandsworth, Enfield and others —
authorising drivers, metering the session and pricing it. Britain has no consumer data-portability mandate for energy equivalent
to Australia''s Consumer Data Right, so nothing compels char.gy to expose an individual driver''s usage or billing data
through an API, and it does not: there is no consumer API, no OAuth server, no OpenID Connect discovery document and no
accredited-recipient scheme anywhere on the domain. What Britain DID mandate here is open infrastructure data. The Public
Charge Point Regulations 2023 (SI 2023/1168), Part 4 regulation 10(5), require every charge point operator to make reference
data and availability data available to the public free of charge, in a machine readable format, and — the crucial clause
— "without any requirement to agree to terms and conditions regarding the use of that data". char.gy complies, and the compliance
is real rather than claimed: it publishes an OCPI-shaped Locations feed and an OCPI-shaped Tariffs feed at https://char.gy/open-ocpi/locations
and https://char.gy/open-ocpi/tariffs, both of which returned HTTP 200 with application/json to a completely anonymous GET
on 2026-07-27, paginated with x-total-count, x-limit and RFC 5988 Link rel="next" headers, carrying real GB*CGY*E*NNNNN
EVSE identifiers, IEC 62196 Type 2 connectors, per-connector tariff_ids and time-of-day restricted pence-per-kWh price components.
The posture is therefore the clean split this sector keeps producing, but rotated: market and infrastructure data wide open
and genuinely ungated because a regulation forbids gating it, consumer data entirely absent because no regulation asks for
it, and the commercial OCPI CPO roaming interface at /ocpi/cpo/ closed behind OCPI Token authorization for partner e-mobility
service providers. There is no developer portal — the entire public documentation for the open API is a single Freshdesk
help-centre article.'
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: true
label: Hosted service · you call their endpoint
confidence: high
source:
- openapi
- 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://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/chargy.png
tags:
- Energy
- United Kingdom
- EV Charging
- Electricity
- Utilities
- OCPI
- Charge Point Operator
- Open Data
- Roaming
- Tariffs
- Mobility
- Electrification
created: '2026-07-27'
modified: '2026-07-27'
specificationVersion: '0.23'
apis:
- aid: chargy:chargy-ocpi-cpo-api
name: char.gy OCPI CPO Roaming API
description: 'char.gy''s commercial Open Charge Point Interface implementation in the Charge Point Operator role, used so
that another network''s drivers can authorise, charge and be settled on char.gy infrastructure. char.gy publishes no documentation
for it at all — its existence was established by two independent signals. First, https://char.gy/robots.txt explicitly
disallows /ocpi/, /api/, /webhooks/, /account/ and /users/. Second, anonymous probes on 2026-07-27 returned HTTP 401 with
the response header `www-authenticate: Token realm="OCPI"` and the body {"error":"HTTP Token: Access denied."} on GET
/ocpi/cpo/versions, /ocpi/cpo/2.1.1/locations, /ocpi/cpo/2.2.1/locations, /ocpi/cpo/2.2.1 /tariffs, /ocpi/cpo/2.2.1/sessions,
/ocpi/cpo/2.2.1/cdrs and /ocpi/cpo/2.2.1/credentials, while control paths /ocpi/, /ocpi/cpo/ nonsense-xyz and /ocpi/xyz/versions
returned 404 from the same host in the same sweep — so the 401s are real routes, not a blanket wall. Version support is
directly observable: /ocpi/cpo/2.2/credentials returned HTTP 200 with the OCPI error envelope {"status_code":3002,"status_message":
"Unsupported version"}, whereas the 2.2.1 and 2.1.1 paths returned 401, which means char.gy speaks OCPI 2.2.1 and 2.1.1
in the CPO role and explicitly rejects 2.2. No eMSP-role surface was found (/ocpi/emsp/versions → 404). Access is partner-only:
an OCPI credentials handshake following a commercial roaming agreement. There is no signup, no sandbox, no published price
and no developer registration — the only published contact route anywhere near the API surface is support@char.gy.'
humanURL: https://char.gy/us/partners
baseURL: https://char.gy/ocpi/cpo
tags:
- EV Charging
- OCPI
- Roaming
- Charge Point Operator
- Sessions
- CDRs
- United Kingdom
properties:
- type: Authentication
url: authentication/chargy-authentication.yml
- type: ErrorCatalog
url: errors/chargy-error-codes.yml
- type: Specification
url: https://github.com/ocpi/ocpi
- type: Partners
url: https://char.gy/us/partners
- type: Support
url: https://help.char.gy/
- type: TermsOfService
url: https://char.gy/us/terms-of-use
- aid: chargy:chargy-locations-api
name: char.gy Locations API
description: Reference and availability data for char.gy charge points.
humanURL: https://help.char.gy/support/solutions/articles/77000576948-public-charge-point-regulations-2023
baseURL: https://char.gy/open-ocpi
tags:
- Locations
properties:
- type: OpenAPI
url: openapi/chargy-locations-api-openapi.yml
- type: Documentation
url: https://help.char.gy/support/solutions/articles/77000576948-public-charge-point-regulations-2023
- type: Examples
url: examples/chargy-locations-response.json
- type: Examples
url: examples/chargy-tariffs-response.json
- type: Conventions
url: conventions/chargy-conventions.yml
- type: ErrorCatalog
url: errors/chargy-error-codes.yml
- type: DataModel
url: data-model/chargy-data-model.yml
- type: ToolCrosswalk
url: mcp/chargy-tool-crosswalk.yml
- type: Specification
url: https://github.com/ocpi/ocpi
- type: Legal
url: https://www.legislation.gov.uk/uksi/2023/1168/regulation/10/made
- type: TermsOfService
url: https://char.gy/us/terms-of-use
- type: Support
url: https://help.char.gy/
- aid: chargy:chargy-tariffs-api
name: char.gy Tariffs API
description: Published price components for char.gy charging sessions.
humanURL: https://help.char.gy/support/solutions/articles/77000576948-public-charge-point-regulations-2023
baseURL: https://char.gy/open-ocpi
tags:
- Tariffs
properties:
- type: OpenAPI
url: openapi/chargy-tariffs-api-openapi.yml
- type: Documentation
url: https://help.char.gy/support/solutions/articles/77000576948-public-charge-point-regulations-2023
- type: Examples
url: examples/chargy-locations-response.json
- type: Examples
url: examples/chargy-tariffs-response.json
- type: Conventions
url: conventions/chargy-conventions.yml
- type: ErrorCatalog
url: errors/chargy-error-codes.yml
- type: DataModel
url: data-model/chargy-data-model.yml
- type: ToolCrosswalk
url: mcp/chargy-tool-crosswalk.yml
- type: Specification
url: https://github.com/ocpi/ocpi
- type: Legal
url: https://www.legislation.gov.uk/uksi/2023/1168/regulation/10/made
- type: TermsOfService
url: https://char.gy/us/terms-of-use
- type: Support
url: https://help.char.gy/
common:
- type: Overlay
url: overlays/chargy-open-charge-point-data-overlay.yaml
- type: X-MCPServerCandidate
url: mcp/chargy-mcp.yml
note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: AgenticAccess
url: agentic-access/chargy-agentic-access.yml
- type: DomainSecurity
url: security/chargy-domain-security.yml
- type: Authentication
url: authentication/chargy-authentication.yml
- type: Conventions
url: conventions/chargy-conventions.yml
- type: Conformance
url: conformance/chargy-conformance.yml
- type: Compliance
url: https://help.char.gy/support/solutions/articles/77000576948-public-charge-point-regulations-2023
- type: Lifecycle
url: lifecycle/chargy-lifecycle.yml
- type: DataModel
url: data-model/chargy-data-model.yml
- type: LLMsTxt
url: llms/chargy-llms.txt
- type: AgentSkill
url: skills/_index.yml
- type: Website
url: https://char.gy/
- type: Documentation
url: https://help.char.gy/support/solutions/articles/77000576948-public-charge-point-regulations-2023
- type: About
url: https://char.gy/us/about
- type: Products
url: https://char.gy/us/our-products-ev-charging
- type: Partners
url: https://char.gy/us/partners
- type: Drivers
url: https://char.gy/us/drivers
- type: Pricing
url: https://char.gy/us/pricing
- type: Blog
url: https://char.gy/us/news
- type: Support
url: https://help.char.gy/
- type: Contact
url: https://char.gy/us/contact-us
- type: PrivacyPolicy
url: https://char.gy/us/privacy-notice
- type: TermsOfService
url: https://char.gy/us/terms-of-use
- type: SignUp
url: https://char.gy/users/payg_registrations/new
- type: Login
url: https://char.gy/users/sign_in
- type: GitHubOrganization
url: https://github.com/char-gy
- type: LinkedIn
url: https://www.linkedin.com/company/char.gy
- type: Application
url: https://apps.apple.com/app/1636840750
- type: Application
url: https://play.google.com/store/apps/details?id=com.chargy_limited.driverapp
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
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.