Electra is a European operator of ultra-fast electric-vehicle charging, headquartered at 104 rue de Richelieu in the 2nd arrondissement of Paris and led by co-founder and CEO Aurelien de Meaux. It designs, finances, installs and operates its own DC fast-charging stations rather than reselling someone else's hardware, advertising 770+ live stations with 68 more under construction, charge rates up to 400 kW, and a target of 2,200 stations / 15,000 charge points across Europe by 2030. Its own pricing and station pages cover France, Belgium, Spain, Italy, Germany, Austria, the Netherlands and Switzerland, with city hubs in Paris, Lyon, Marseille, Brussels, Antwerp, Liege, Milan, Bologna, Turin, Madrid, Barcelona and Zurich. The commercial surface is consumer- and fleet-facing: a mobile app, an Electra+ subscription that cuts up to 0.20 EUR/kWh, an RFID charging card, Autocharge and Plug&Charge, and a fleet dashboard at business.go-electra.com. It is a Serena portfolio company and has raised a 160 MEUR round, a 304 MEUR Series B and a 433 MEUR debt facility. Electra publishes NO developer portal, NO API documentation, NO OpenAPI, NO llms.txt, NO MCP server and NO A2A agent card — every one of those was probed and missed on 2026-08-17. What it does run, and what almost nobody looking at the marketing site would find, is a real machine-readable API: a live Open Charge Point Interface implementation in the Charge Point Operator role at https://ocpi.go-electra.com/ocpi/cpo, serving BOTH OCPI 2.1.1 and OCPI 2.2.1 concurrently. Its version-negotiation endpoints answer anonymously with HTTP 200 and enumerate the full module inventory — cdrs, commands, credentials, locations, sessions, tariffs and tokens, with SENDER/RECEIVER roles declared on the 2.2.1 surface — while every data module itself returns HTTP 401 with `WWW-Authenticate: Token realm="Application"`, OCPI's own bilateral token scheme. That is a documented open industry standard, fully implemented, discoverable without credentials and readable only with a roaming agreement; its production use is evidenced by the 180+ e-mobility service provider cards Electra's own help centre lists as accepted at its chargers.
Electra publishes 1 API on the APIs.io network. Tagged areas include Company, Climate Tech, EV Charging, Energy, and Mobility.
Electra’s developer surface includes pricing, signup flow, support, engineering blog, legal docs, authentication, code examples, and 22 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 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/go-electra: 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 →
Electra's Open Charge Point Interface implementation in the Charge Point Operator role — the roaming interface an e-mobility service provider calls to read Electra's locations a...
aid: go-electra
name: Electra
url: https://raw.githubusercontent.com/api-evangelist/go-electra/refs/heads/main/apis.yml
x-type: company
x-source: serena-portfolio
description: 'Electra is a European operator of ultra-fast electric-vehicle charging, headquartered at 104 rue de Richelieu
in the 2nd arrondissement of Paris and led by co-founder and CEO Aurelien de Meaux. It designs, finances, installs and operates
its own DC fast-charging stations rather than reselling someone else''s hardware, advertising 770+ live stations with 68
more under construction, charge rates up to 400 kW, and a target of 2,200 stations / 15,000 charge points across Europe
by 2030. Its own pricing and station pages cover France, Belgium, Spain, Italy, Germany, Austria, the Netherlands and Switzerland,
with city hubs in Paris, Lyon, Marseille, Brussels, Antwerp, Liege, Milan, Bologna, Turin, Madrid, Barcelona and Zurich.
The commercial surface is consumer- and fleet-facing: a mobile app, an Electra+ subscription that cuts up to 0.20 EUR/kWh,
an RFID charging card, Autocharge and Plug&Charge, and a fleet dashboard at business.go-electra.com. It is a Serena portfolio
company and has raised a 160 MEUR round, a 304 MEUR Series B and a 433 MEUR debt facility. Electra publishes NO developer
portal, NO API documentation, NO OpenAPI, NO llms.txt, NO MCP server and NO A2A agent card — every one of those was probed
and missed on 2026-08-17. What it does run, and what almost nobody looking at the marketing site would find, is a real machine-readable
API: a live Open Charge Point Interface implementation in the Charge Point Operator role at https://ocpi.go-electra.com/ocpi/cpo,
serving BOTH OCPI 2.1.1 and OCPI 2.2.1 concurrently. Its version-negotiation endpoints answer anonymously with HTTP 200
and enumerate the full module inventory — cdrs, commands, credentials, locations, sessions, tariffs and tokens, with SENDER/RECEIVER
roles declared on the 2.2.1 surface — while every data module itself returns HTTP 401 with `WWW-Authenticate: Token realm="Application"`,
OCPI''s own bilateral token scheme. That is a documented open industry standard, fully implemented, discoverable without
credentials and readable only with a roaming agreement; its production use is evidenced by the 180+ e-mobility service provider
cards Electra''s own help centre lists as accepted at its chargers.'
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: paid
onboarding: unknown
trial: false
try_now: false
public: false
label: Paid
confidence: high
source:
- plans
- authentication
- rate-limits
- security
generated: '2026-09-03'
method: derived
image: https://www.go-electra.com/favicons/apple-touch-icon-1024x1024.png
specificationVersion: '0.23'
created: '2026-08-17'
modified: '2026-08-17'
tags:
- Company
- Climate Tech
- EV Charging
- Energy
- Mobility
- OCPI
- Roaming
- Charge Point Operator
- Electric Vehicles
- Fast Charging
- Charging Sessions
- Tariffs
- Electrification
- France
- Europe
apis:
- aid: go-electra:go-electra-ocpi-cpo-api
name: Electra OCPI CPO API
description: 'Electra''s Open Charge Point Interface implementation in the Charge Point Operator role — the roaming interface
an e-mobility service provider calls to read Electra''s locations and tariffs, authorise its own drivers on Electra hardware,
receive session and charge-detail records, and send remote start/stop commands. Electra publishes no human documentation
and no specification document for it; the surface was established entirely by anonymous probe on 2026-08-17. GET https://ocpi.go-electra.com/ocpi/cpo/versions
returned HTTP 200 (application/json) advertising two concurrent protocol versions, 2.1.1 and 2.2.1. GET /ocpi/cpo/2.1.1
returned HTTP 200 enumerating seven module endpoints — cdrs, commands, credentials, locations, sessions, tariffs, tokens.
GET /ocpi/cpo/2.2.1 returned HTTP 200 enumerating the same modules plus explicit OCPI 2.2.1 roles: cdrs SENDER, commands
RECEIVER, credentials both SENDER and RECEIVER, locations SENDER, sessions SENDER, tariffs SENDER, tokens RECEIVER. Every
module endpoint itself is closed: GET /ocpi/cpo/2.2.1/locations, /ocpi/cpo/2.1.1/locations and /ocpi/cpo/2.2.1/tariffs
each returned HTTP 401 with the body `Token: Access denied.` and the header `WWW-Authenticate: Token realm="Application"`,
which is OCPI''s own bilateral Token authorization scheme rather than a blanket wall — sibling paths such as /ocpi/versions,
/ocpi/cpo/2.0.1 and /ocpi/cpo/2.2.1/credentials returned 404, proving the 401s are real routes. Access follows a commercial
roaming agreement and an OCPI credentials handshake; there is no signup, no sandbox and no self-service token. No anonymous
locations, tariff or availability feed of any kind is published, so Electra exposes zero open charging-network market
data.'
humanURL: https://ocpi.go-electra.com/ocpi/cpo/versions
baseURL: https://ocpi.go-electra.com/ocpi/cpo
tags:
- EV Charging
- OCPI
- Roaming
- Charge Point Operator
- Locations
- Tariffs
- Charging Sessions
- Europe
properties:
- type: Specification
url: https://github.com/ocpi/ocpi
- type: Authentication
url: authentication/go-electra-authentication.yml
- type: Conformance
url: conformance/go-electra-conformance.yml
- type: Conventions
url: conventions/go-electra-conventions.yml
- type: ErrorCatalog
url: errors/go-electra-problem-types.yml
- type: Examples
url: examples/_index.yml
- type: RateLimits
url: rate-limits/go-electra-rate-limits.yml
- type: Lifecycle
url: lifecycle/go-electra-lifecycle.yml
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
common:
- type: Website
url: https://www.go-electra.com/
- type: About
url: https://www.go-electra.com/en/about/
- type: Pricing
url: https://www.go-electra.com/en/price/
- type: SignUp
url: https://business.go-electra.com/register
- type: Login
url: https://business.go-electra.com/sign-in
- type: Support
url: https://intercom.help/go-electra/en/
- type: Contact
url: https://www.go-electra.com/en/contact/
- type: Blog
url: https://www.go-electra.com/en/newsroom/all-categories/
- type: TermsOfService
url: https://www.go-electra.com/en/tos/
- type: PrivacyPolicy
url: https://www.go-electra.com/en/privacy/
- type: Legal
url: https://www.go-electra.com/en/legal/
- type: TrustCenter
url: https://trust.go-electra.com/
- type: Ethics
url: https://www.go-electra.com/en/whistleblowing-and-grievance/
- type: Sustainability
url: https://www.go-electra.com/en/sustainability/
- type: Application
url: https://app.go-electra.com/
- type: LinkedIn
url: https://www.linkedin.com/company/electra-charge
- type: Careers
url: https://careers.go-electra.com/en
- type: Authentication
url: authentication/go-electra-authentication.yml
- type: Conformance
url: conformance/go-electra-conformance.yml
- type: Conventions
url: conventions/go-electra-conventions.yml
- type: ErrorCatalog
url: errors/go-electra-problem-types.yml
- type: Lifecycle
url: lifecycle/go-electra-lifecycle.yml
- type: Examples
url: examples/_index.yml
- type: DomainSecurity
url: security/go-electra-domain-security.yml
- type: Packages
url: packages/go-electra-packages.yml
- type: Plans
url: plans/go-electra-plans-pricing.yml
- type: RateLimits
url: rate-limits/go-electra-rate-limits.yml
- type: X-MCPServerCandidate
url: mcp/go-electra-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: LLMsTxt
url: llms/go-electra-llms.txt
x-enrichment:
date: '2026-08-17'
status: enriched
artifacts_added: 17
pass: local-v1
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.
Kin Score
How this is scored →