# Electra

> Electra is a European operator of ultra-fast electric-vehicle charging, headquartered in Paris and led by co-founder and CEO Aurelien de Meaux. It designs, finances, installs and operates its own DC fast-charging stations — 770+ live with 68 more building, up to 400 kW — across France, Belgium, Spain, Italy, Germany, Austria, the Netherlands and Switzerland, with a stated target of 2,200 stations / 15,000 charge points in Europe by 2030. This file was GENERATED by API Evangelist from probed evidence; Electra does not publish an llms.txt (/llms.txt returns 404 on go-electra.com).

## What Electra publishes for machines

Electra has no developer portal, no API documentation, no OpenAPI, no GraphQL, no MCP server and no A2A agent card. All of these were probed on 2026-08-17 and all missed.

It does run one real machine-readable API: an Open Charge Point Interface (OCPI) implementation in the Charge Point Operator role. Its version-negotiation endpoints answer anonymously; every data module requires a bilateral OCPI credentials token issued under a commercial roaming agreement.

## APIs

- [Electra OCPI CPO API](https://ocpi.go-electra.com/ocpi/cpo/versions): OCPI 2.1.1 and 2.2.1 served concurrently. Base https://ocpi.go-electra.com/ocpi/cpo. Modules: cdrs (SENDER), commands (RECEIVER), credentials (SENDER+RECEIVER), locations (SENDER), sessions (SENDER), tariffs (SENDER), tokens (RECEIVER). Auth: `Authorization: Token <credential>`; unauthenticated module calls return HTTP 401 with `WWW-Authenticate: Token realm="Application"`.
- [OCPI version negotiation](https://ocpi.go-electra.com/ocpi/cpo/versions): HTTP 200, no credentials required.
- [OCPI 2.1.1 endpoint inventory](https://ocpi.go-electra.com/ocpi/cpo/2.1.1): HTTP 200, no credentials required.
- [OCPI 2.2.1 endpoint inventory](https://ocpi.go-electra.com/ocpi/cpo/2.2.1): HTTP 200, no credentials required.
- [OCPI specification](https://github.com/ocpi/ocpi): the standard Electra implements. Owned by the OCPI community, not by Electra.

## Specs

Electra publishes no specification document. The only machine-readable material is the verbatim OCPI discovery responses captured in this profile.

## Artifacts in this profile

- authentication/go-electra-authentication.yml — OCPI Token scheme, observed on the wire.
- conformance/go-electra-conformance.yml — what Electra does and does not conform to, with evidence per line.
- conventions/go-electra-conventions.yml — response envelope, versioning, tracing, caching; idempotency and pagination recorded as unknown because the modules are gated.
- errors/go-electra-problem-types.yml — the observed 401 and two distinct 404 shapes; not RFC 9457.
- lifecycle/go-electra-lifecycle.yml — two concurrent protocol versions; no status page, SLA, deprecation policy or changelog.
- rate-limits/go-electra-rate-limits.yml — limit_count 0; no rate-limit header of any kind on the wire.
- plans/go-electra-plans-pricing.yml — consumer and fleet charging pricing; no API pricing exists.
- packages/go-electra-packages.yml — package_count 0; no first-party SDK in any registry.
- security/go-electra-domain-security.yml — TLS 1.3 on both hosts; HSTS on the API host, absent on the marketing host; SPF and DMARC (quarantine) published, no DNSSEC, no CAA.
- security/go-electra-trust-center.yml — a real Vanta trust centre at https://trust.go-electra.com/, contents not readable anonymously, so no certification is claimed.
- well-known/go-electra-well-known.yml — a recorded absence: no /.well-known/ document on any host.
- mcp/go-electra-mcp.yml — a CANDIDATE tool design derived from the OCPI modules. Electra ships no MCP server.
- examples/ — the three OCPI discovery responses, verbatim.

## Docs

- [Website](https://www.go-electra.com/)
- [Pricing](https://www.go-electra.com/en/price/)
- [Help centre](https://intercom.help/go-electra/en/) — twelve collections, consumer and fleet oriented; no API content.
- [For professionals / fleets](https://www.go-electra.com/en/business/)
- [Fleet portal sign-up](https://business.go-electra.com/register)
- [Newsroom](https://www.go-electra.com/en/newsroom/all-categories/) — marketing blog, not a changelog.
- [Trust centre](https://trust.go-electra.com/)
- [Terms of service](https://www.go-electra.com/en/tos/)
- [Privacy policy](https://www.go-electra.com/en/privacy/)
- [Ethics and whistleblowing](https://www.go-electra.com/en/whistleblowing-and-grievance/) — ethics@go-electra.com; NOT a security disclosure channel.

## For agents

There is no way for an agent to use Electra today. There is no self-service credential, no sandbox, no documented endpoint and no rate-limit signal. The OCPI interface is real and correctly implemented, but it is reachable only after a human negotiates a roaming agreement. If you need Electra charging data, the practical route is one of the 180+ e-mobility service providers whose cards Electra accepts, not Electra directly.

## Provenance

Generated 2026-08-17 by the API Evangelist enrichment pipeline from anonymous public probes and Electra's own published pages. Not authored, reviewed or endorsed by Electra. Corrections: https://github.com/api-evangelist/go-electra