# Connected Kerb

> Connected Kerb is a UK electric-vehicle charging company that designs, installs, owns and operates public on-street and destination charge points, with a particular focus on residential drivers who have no off-street parking. Founded in 2017 and headquartered in London, it delivers long-term charging concessions for local authorities, workplaces, retail destinations, car parks and residential developers, and by mid-2026 operated roughly 7,800 public chargers across about 1,780 UK locations.

This file was generated by API Evangelist from a public probe of Connected Kerb's own hosts on 2026-08-04. Connected Kerb does not publish an llms.txt, a developer portal, or a machine-readable API description of its own.

## APIs

- [Connected Kerb OCPI (CPO) Interface](https://cp.connectedkerb.com/ocpi/versions): Live Open Charge Point Interface endpoint. Versions 2.1.1, 2.2 and 2.2.1 all answer; token-gated per the OCPI credentials module. Used for e-mobility roaming and for the machine-readable charge point data named by the UK Public Charge Point Regulations 2023.
- [Connected Kerb Charge Point Platform API](https://cp.connectedkerb.com/public-api/): Server-to-server API for charge points, EVSEs, locations, sessions, users, tariffs, partners and roaming. Bearer API token, issued through the operator back office. The contract governing it is published by the platform vendor, not by Connected Kerb.

## Access

- Both API surfaces are gated. There is no self-service sign-up for API credentials.
- OCPI access requires a bilateral credentials exchange (commercial roaming agreement).
- Platform API access requires an API access token created in the operator back office.
- The OAuth 2.0 client-credentials grant described by the platform contract is not enabled on Connected Kerb's tenant.

## Artifacts

- [Authentication profile](authentication/connected-kerb-authentication.yml): every credential mechanism observed on Connected Kerb's hosts, with the HTTP status that evidences it.
- [API conventions](conventions/connected-kerb-conventions.yml): pagination, filtering, versioning, rate limits, tracing headers, error envelopes.
- [Error catalogue](errors/connected-kerb-problem-types.yml): observed error bodies plus the response catalogue of the governing contract.
- [Lifecycle](lifecycle/connected-kerb-lifecycle.yml): versioning, deprecation, status page and changelog posture.
- [Conformance](conformance/connected-kerb-conformance.yml): OCPI, OAuth, RFC 9457, RFC 9116, PCPR 2023.
- [Domain security](security/connected-kerb-domain-security.yml): TLS, HSTS, DNSSEC, CAA, SPF, DMARC probe results.
- [Well-known probe log](well-known/connected-kerb-well-known.yml): every /.well-known/ path probed, and the 404 each returned.

## Human pages

- [Website](https://www.connectedkerb.com/)
- [Our technology](https://www.connectedkerb.com/our-technology/)
- [Software platform](https://www.connectedkerb.com/our-technology/software/)
- [Charge point hardware](https://www.connectedkerb.com/our-technology/charging-points/)
- [Smart charging](https://www.connectedkerb.com/charge-your-car/smart-charging/)
- [Find a charging point](https://www.connectedkerb.com/charge-your-car/find-a-charging-point/)
- [Charging tariffs](https://www.connectedkerb.com/our-technology/charging-tariffs/)
- [Driver app](https://www.connectedkerb.com/our-technology/software/our-app/)
- [Customer portal](https://portal.connectedkerb.com/)
- [Customer support](https://www.connectedkerb.com/contact-us/customer-support/)
- [Stories, reports and events](https://www.connectedkerb.com/stories-reports-and-events/)
- [Technical information](https://www.connectedkerb.com/technical-information/)
- [Privacy policy](https://www.connectedkerb.com/privacy-policy/)
- [App terms and conditions](https://www.connectedkerb.com/our-technology/software/app-ts-cs/)

## What is missing

An agent or integrator looking at Connected Kerb today will find no developer portal, no API reference, no getting-started guide, no OpenAPI or AsyncAPI description, no SDKs, no CLI, no sandbox, no status page, no API changelog, no security.txt, no api-catalog and no agent card. The two APIs it operates are real and standards-based, but nothing on any Connected Kerb host tells a developer they exist.