# char.gy

> char.gy is a British public electric-vehicle charge point operator that puts the charger inside the lamp post, serving the roughly 40% of UK households with no off-street parking. It publishes a genuinely open, genuinely anonymous OCPI-shaped Locations and Tariffs feed because Part 4 regulation 10(5) of the Public Charge Point Regulations 2023 requires charge point reference and availability data to be published free of charge, machine readable, and without any requirement to agree to terms and conditions. There is no developer portal, no consumer API and no OAuth server; the commercial OCPI roaming interface is partner-only.

Generated by API Evangelist on 2026-07-27 from live probes and the catalog. char.gy publishes no llms.txt of its own (https://char.gy/llms.txt returns 404).

## APIs

- [char.gy Open Charge Point Data API](https://help.char.gy/support/solutions/articles/77000576948-public-charge-point-regulations-2023): Statutory open data feed at https://char.gy/open-ocpi — two read-only, unauthenticated OCPI modules. `GET /open-ocpi/locations` returned HTTP 200 anonymously with an x-total-count of 5,409 on 2026-07-27; `GET /open-ocpi/tariffs` returned 3 tariff objects. Pagination is limit/offset with x-total-count, x-limit and an RFC 5988 Link rel="next" header; date_from and date_to filter on last_updated and are verified working.
- [char.gy OCPI CPO Roaming API](https://char.gy/us/partners): Commercial Open Charge Point Interface implementation in the Charge Point Operator role at https://char.gy/ocpi/cpo. Undocumented and credential-gated — anonymous requests return HTTP 401 with `www-authenticate: Token realm="OCPI"`. OCPI 2.2.1 and 2.1.1 are supported; 2.2 is rejected with status_code 3002. Access requires a commercial roaming agreement and an OCPI credentials handshake.

## Specs

- [OpenAPI — Open Charge Point Data API](https://raw.githubusercontent.com/api-evangelist/chargy/refs/heads/main/openapi/chargy-open-charge-point-data-openapi.yml): OpenAPI 3.1.0 generated by API Evangelist from live anonymous probes. char.gy publishes no machine-readable specification.
- [OpenAPI Overlay](https://raw.githubusercontent.com/api-evangelist/chargy/refs/heads/main/overlays/chargy-open-charge-point-data-overlay.yaml): API Evangelist enhancements — provenance, regulatory basis, crawl guidance, standard-divergence notes.
- [OCPI specification](https://github.com/ocpi/ocpi): The upstream standard char.gy's payloads are shaped by.

## Artifacts

- [Authentication profile](https://raw.githubusercontent.com/api-evangelist/chargy/refs/heads/main/authentication/chargy-authentication.yml): Two postures on one host — no auth at all on the statutory feed, OCPI Token on the commercial surface. No OAuth, no OIDC, no API keys.
- [API conventions](https://raw.githubusercontent.com/api-evangelist/chargy/refs/heads/main/conventions/chargy-conventions.yml): Envelope, pagination, filtering, caching, tracing and rate-limit signalling as observed.
- [Error codes](https://raw.githubusercontent.com/api-evangelist/chargy/refs/heads/main/errors/chargy-error-codes.yml): OCPI status codes 1000 / 2001 / 3002 plus the HTTP 401 and 404 shapes. Note client errors are returned with HTTP 200.
- [Conformance](https://raw.githubusercontent.com/api-evangelist/chargy/refs/heads/main/conformance/chargy-conformance.yml): PCPR 2023 regulation 10 conformance verified live; OCPI 2.2.1 partial (EVSE status values diverge from the standard).
- [Lifecycle](https://raw.githubusercontent.com/api-evangelist/chargy/refs/heads/main/lifecycle/chargy-lifecycle.yml): No versioning on the open feed, no changelog, no SLA, no status page; version negotiation on the CPO surface.
- [Data model](https://raw.githubusercontent.com/api-evangelist/chargy/refs/heads/main/data-model/chargy-data-model.yml): Location → EVSE → Connector → Tariff, joined only by connector.tariff_ids.
- [Domain security](https://raw.githubusercontent.com/api-evangelist/chargy/refs/heads/main/security/chargy-domain-security.yml): TLS 1.3, HSTS 2 years, SPF and DMARC present, no DNSSEC, no CAA.
- [Well-known probe record](https://raw.githubusercontent.com/api-evangelist/chargy/refs/heads/main/well-known/chargy-well-known.yml): All five /.well-known/ discovery paths return 404.
- [MCP candidate](https://raw.githubusercontent.com/api-evangelist/chargy/refs/heads/main/mcp/chargy-mcp.yml): char.gy runs no MCP server; a two-tool candidate surface derived from the OpenAPI.
- [Agent skills](https://raw.githubusercontent.com/api-evangelist/chargy/refs/heads/main/skills/_index.yml): Finding charge points and prices; keeping a local mirror in sync.
- [Examples](https://raw.githubusercontent.com/api-evangelist/chargy/refs/heads/main/examples/chargy-locations-response.json): Verbatim captured responses from both endpoints.

## Docs

- [Public Charge Point Regulations 2023 compliance article](https://help.char.gy/support/solutions/articles/77000576948-public-charge-point-regulations-2023): The complete published documentation for the open API — host, two paths, and a support email.
- [Help centre](https://help.char.gy/)
- [Regulation 10, SI 2023/1168](https://www.legislation.gov.uk/uksi/2023/1168/regulation/10/made): The legal basis for the open feed.
- [Partners](https://char.gy/us/partners): The only route to the commercial roaming interface.
- [Pricing](https://char.gy/us/pricing)
- [Terms of use](https://char.gy/us/terms-of-use)
- [Privacy notice](https://char.gy/us/privacy-notice)
- [News](https://char.gy/us/news)

## Notes for agents

- Send no credential to https://char.gy/open-ocpi — it is anonymous by law.
- Check `status_code == 1000` on every response; client errors are delivered with HTTP 200.
- There is no spatial or status filter and no per-object read; geographic questions require crawling all 5,409 locations. Use `date_from` for incremental syncs.
- `evse.status` values `WORKING` and `FAULTED` are not OCPI 2.2.1 values — do not validate them against the OCPI enumeration.
- No rate limit is published or signalled. Keep concurrency low; there is no status page if you cause a problem.