Enapi

Enapi (ENAPI) operates a unified roaming and clearing platform for the electric vehicle charging industry, brokering transactions between Charge Point Operators (CPOs) and e-Mobility Service Providers (eMSPs). Rather than exposing a proprietary API, Enapi implements the open OCPI (Open Charge Point Interface) standard out-of-the-box across versions 2.1.1, 2.2.1, and 2.3.0, operating as an OCPI HUB that handles version interoperability, message routing, and endpoint fan-out on behalf of partners. Its three product lines are Roaming (peer-to-peer commercial connections while Enapi handles the technical integration), Technical (standardized OCPI onboarding with automated testing and a staging environment), and Financial CDR Clearing (real-time Charge Detail Record validation, dispute flagging, and settlement). As of early 2024 the platform connects over 700,000 charge points and works with most major eMSPs including partners such as TotalEnergies, ChargePoint, ubitricity, Plugsurfing, Monta, and Eneco.

Enapi is listed with 1 API on the APIs.io network. Tagged areas include Company, EV Charging, OCPI, Roaming, and E-Mobility.

Enapi’s developer surface includes documentation, API reference, getting-started guide, signup flow, support, authentication, sandbox, and 12 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

33.0/100 thin ▬ flat Agent 3/100 human only Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 API

Company EV Charging OCPI Roaming E-Mobility Charge Point OperatoreMSPElectric VehiclesCDR ClearingInteroperability Hub

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 33.0/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 10.5 / 17

Access Clarity 7.2 / 17

Operational Transparency 1.7 / 11

Contract Governance 1.9 / 10

Discoverability 6.2 / 9

Regulatory Posture 3.8 / 15

Agent readiness — 3/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Telecommunications 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/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/enapi/"><img src="https://apis.io/badge/enapi/card.svg" alt="Enapi on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0

12 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Access Clarity scores 42.1 — up to +11.6 composite points
Operational Transparency scores 15.8 — up to +10.9 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/enapi/apis.yml: open an issue on github.com/api-evangelist/enapi to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
EV Charging (charging, roaming, e-mobility)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OCPI

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Enapi OCPI Roaming API

Enapi's OCPI HUB endpoint for EV charging roaming. Implements the Open Charge Point Interface (OCPI) 2.1.1 / 2.2.1 / 2.3.0 across the Credentials, Locations, Tariffs, Tokens, Se...

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Enapi

SLA

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Enapi Authentication

ocpi-token · 1 scheme

SECURITY

Enapi Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 5

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Login

SignUp

SignUp

Sandbox

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Conventions

Conventions

Conformance

Conformance

Lifecycle

Lifecycle

Access & Security 3

Authentication, authorization, and security posture

Compliance

Compliance

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

Support

Support

StatusPage

StatusPage

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 1

The organization behind the API

Website

Website

Source (apis.yml)

aid: enapi
name: Enapi
description: Enapi (ENAPI) operates a unified roaming and clearing platform for the electric vehicle charging industry, brokering
  transactions between Charge Point Operators (CPOs) and e-Mobility Service Providers (eMSPs). Rather than exposing a proprietary
  API, Enapi implements the open OCPI (Open Charge Point Interface) standard out-of-the-box across versions 2.1.1, 2.2.1,
  and 2.3.0, operating as an OCPI HUB that handles version interoperability, message routing, and endpoint fan-out on behalf
  of partners. Its three product lines are Roaming (peer-to-peer commercial connections while Enapi handles the technical
  integration), Technical (standardized OCPI onboarding with automated testing and a staging environment), and Financial CDR
  Clearing (real-time Charge Detail Record validation, dispute flagging, and settlement). As of early 2024 the platform connects
  over 700,000 charge points and works with most major eMSPs including partners such as TotalEnergies, ChargePoint, ubitricity,
  Plugsurfing, Monta, and Eneco.
url: https://raw.githubusercontent.com/api-evangelist/enapi/refs/heads/main/apis.yml
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: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://enapi.com/media/pages/home/6908c67d54-1749641656/enapi_blue_inverse-web-1000x.png
x-type: company
x-source: vc-portfolio
x-backed-by:
- seedcamp
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
x-docs-platform: gitbook
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-03
tags:
- Company
- EV Charging
- OCPI
- Roaming
- E-Mobility
- Charge Point Operator
- eMSP
- Electric Vehicles
- CDR Clearing
- Interoperability
- Hub
tags_raw:
- Company
- EV Charging
- OCPI
- Roaming
- E-Mobility
- Charge Point Operator
- eMSP
- Electric Vehicle
- CDR Clearing
- Interoperability
- Hub
apis:
- name: Enapi OCPI Roaming API
  description: Enapi's OCPI HUB endpoint for EV charging roaming. Implements the Open Charge Point Interface (OCPI) 2.1.1
    / 2.2.1 / 2.3.0 across the Credentials, Locations, Tariffs, Tokens, Sessions, CDRs, Commands, HubClientInfo, and Payments
    modules. Authentication is via OCPI token exchange (handshake) with tokens carried in the Authorization header (Base64-encoded
    for 2.2.1+).
  humanURL: https://docs.enapi.com/technical-documentation
  baseURL: https://roaming.enapi.com
  properties:
  - type: Documentation
    url: https://docs.enapi.com
  - type: Authentication
    url: authentication/enapi-authentication.yml
  - type: Sandbox
    url: sandbox/enapi-sandbox.yml
common:
- type: Website
  url: https://enapi.com
- type: DeveloperPortal
  url: https://docs.enapi.com
- type: Documentation
  url: https://docs.enapi.com
- type: APIReference
  url: https://docs.enapi.com/technical-documentation
- type: GettingStarted
  url: https://docs.enapi.com/getting-started
- type: Login
  url: https://app.enapi.com/login
- type: SignUp
  url: https://calendly.com/enapi/let-s-talk
- type: Support
  url: https://docs.enapi.com/security-compliance-and-slas/incident-management
- type: StatusPage
  url: https://status.enapi.com/
- type: TermsOfService
  url: https://enapi.com/terms-of-use
- type: PrivacyPolicy
  url: https://enapi.com/privacy-policy
- type: Compliance
  url: https://docs.enapi.com/security-compliance-and-slas/compliance-and-data-residency
- type: LLMsTxt
  url: llms/enapi-llms.txt
- type: Authentication
  url: authentication/enapi-authentication.yml
- type: Conventions
  url: conventions/enapi-conventions.yml
- type: Conformance
  url: conformance/enapi-conformance.yml
- type: Lifecycle
  url: lifecycle/enapi-lifecycle.yml
- type: Sandbox
  url: sandbox/enapi-sandbox.yml
- type: DomainSecurity
  url: security/enapi-domain-security.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Enapi — frequently asked questions

Does Enapi have an API?

Yes. APIs.io lists 1 API from Enapi, including Enapi OCPI Roaming API.

How do I authenticate with the Enapi?

Enapi uses bearer-token authentication (ocpi-token · 1 scheme). The details are profiled on APIs.io as Enapi Authentication.

Is the Enapi ready for AI agents?

Enapi has a Kin Score of 33.0 out of 100 (thin) and an Agent Readiness score of 2.5 (human-only), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/enapi"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/enapi/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/enapi/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.