The Mobility House website screenshot

The Mobility House

The Mobility House (TMH) is a Munich-headquartered electric-mobility and energy technology company, founded in 2009, with offices in Zurich, Montreal, Paris, Singapore and Belmont (USA). Its ChargePilot smart charging and energy management system pairs an on-site controller with a cloud dashboard to run dynamic load management across mixed-vendor AC and DC charging infrastructure, and its Vehicle-to-Grid (V2G) platform markets electric-vehicle battery capacity into energy and grid-balancing markets. ChargePilot integrates with third-party systems over open, standards-based interfaces rather than a public REST developer program: OCPP to charging stations, a VDV 463 WebSocket interface to depot and fleet management systems, a Modbus TCP/IP server for building and site energy management systems, and an outbound Charging Data Push-API that delivers completed charging sessions as JSON to a customer endpoint.

The Mobility House publishes 2 APIs on the APIs.io network. Tagged areas include Company, Energy, Electric Vehicles, EV Charging, and Smart Charging.

The The Mobility House catalog on APIs.io includes 1 event-driven AsyncAPI specification.

The Mobility House’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, signup flow, changelog, and 21 more developer resources.

43.6/100 developing ▬ flat Agent 32/100 agent ready Full breakdown ↓
scored 2026-09-02 · rubric v0.18.0
AccessSelf serve
2 APIs
CompanyEnergyElectric VehiclesEV ChargingSmart ChargingEnergy ManagementVehicle-to-GridLoad ManagementFleetOCPPVDV 463ModbusGermany

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-02 · rubric v0.18.0
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.
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/the-mobility-house: 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 →

APIs 2

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

ChargePilot VDV 463 Interface

Two-way WebSocket-Secure interface between ChargePilot (acting as the Charging Management System, CMS) and an upstream Depot Management, Fleet Management or ITCS system, impleme...

ChargePilot Charging Data Push-API

Outbound cloud-to-cloud push of billing-relevant charging session records. On completion of a charging session ChargePilot POSTs a JSON payload over HTTPS to a customer-supplied...

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

The Mobility House Rate Limits

0 limits

RATE LIMITS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Security Posture 2

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

The Mobility House Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Scroll for all 7

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 6

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: the-mobility-house
name: The Mobility House
description: 'The Mobility House (TMH) is a Munich-headquartered electric-mobility and energy technology company, founded
  in 2009, with offices in Zurich, Montreal, Paris, Singapore and Belmont (USA). Its ChargePilot smart charging and energy
  management system pairs an on-site controller with a cloud dashboard to run dynamic load management across mixed-vendor
  AC and DC charging infrastructure, and its Vehicle-to-Grid (V2G) platform markets electric-vehicle battery capacity into
  energy and grid-balancing markets. ChargePilot integrates with third-party systems over open, standards-based interfaces
  rather than a public REST developer program: OCPP to charging stations, a VDV 463 WebSocket interface to depot and fleet
  management systems, a Modbus TCP/IP server for building and site energy management systems, and an outbound Charging Data
  Push-API that delivers completed charging sessions as JSON to a customer endpoint.'
url: https://raw.githubusercontent.com/api-evangelist/the-mobility-house/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  - rate-limits
  - security
  generated: '2026-09-02'
  method: derived
specificationVersion: '0.20'
image: https://cdn-website.mobilityhouse.com/Open-Graph-Image_575018da3f191243c105ceb22aba34e4.png
created: '2026-08-30'
modified: '2026-08-30'
tags:
- Company
- Energy
- Electric Vehicles
- EV Charging
- Smart Charging
- Energy Management
- Vehicle-to-Grid
- Load Management
- Fleet
- OCPP
- VDV 463
- Modbus
- Germany
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- aid: the-mobility-house-chargepilot-vdv-463
  name: ChargePilot VDV 463 Interface
  description: Two-way WebSocket-Secure interface between ChargePilot (acting as the Charging Management System, CMS) and
    an upstream Depot Management, Fleet Management or ITCS system, implemented against the VDV 463 standard published by the
    Verband Deutscher Verkehrsunternehmen. ChargePilot pushes ProvideChargingInformation.req messages carrying a DepotInfoList
    (depot setup, charging station and charging point statuses, live charging processes, fault information) every 15 seconds;
    the upstream system may optionally push ProvideChargingRequests.req messages carrying per-vehicle charging schedules.
    The session opens with a WebSocket TLS handshake authenticated with HTTP Basic credentials issued by The Mobility House,
    followed by a BootNotification.req/.conf exchange.
  humanURL: https://vdv-docs.tmh.energy/
  baseURL: ''
  x-baseurl-note: Deliberately empty, not a gap in the pass. The VDV 463 WebSocket-Secure endpoint is provisioned per customer
    site by The Mobility House at the time the site is enabled, and is delivered privately with the credentials; no base URL
    is stated anywhere in the public technical guideline. api.tmh.energy resolves and is a Mobility House host, but it answers
    HTTP 503 from nginx on every path probed (/, /openapi.json, /docs, /v1/openapi.json, /swagger.json, /api-docs, /redoc,
    2026-08-30) and is named in no document, so it is not asserted as the base.
  tags:
  - VDV 463
  - WebSocket
  - Depot Management
  - Charging Schedules
  - Smart Charging
  properties:
  - type: Documentation
    url: https://vdv-docs.tmh.energy/
  - type: GettingStarted
    url: https://vdv-docs.tmh.energy/initial-connection/initial-connection/
  - type: Authentication
    url: authentication/the-mobility-house-authentication.yml
  - type: ErrorCatalog
    url: errors/the-mobility-house-problem-types.yml
  - type: DataModel
    url: data-model/the-mobility-house-data-model.yml
  - type: Conformance
    url: conformance/the-mobility-house-conformance.yml
- aid: the-mobility-house-chargepilot-charging-data-push-api
  name: ChargePilot Charging Data Push-API
  description: Outbound cloud-to-cloud push of billing-relevant charging session records. On completion of a charging session
    ChargePilot POSTs a JSON payload over HTTPS to a customer-supplied endpoint, batched by default hourly, authenticating
    itself to the receiver with an Ocp-Apim-Subscription-Key header. Each record carries TransactionID, ChargerID (the OCPP
    station identifier), ConnectorID, StartAt and EndAt UTC timestamps, the RFID Id presented, EnergyDelivered in Wh, and
    InitialSoC / EndSoC where the charging point is DC. All current and future charging sites on the account are included
    automatically.
  humanURL: https://tmh-help.freshdesk.com/en/support/solutions/articles/203000046009-chargepilot-charging-data-push-api
  baseURL: ''
  x-baseurl-note: 'Deliberately empty. This is an outbound webhook: ChargePilot POSTs to a host the CUSTOMER operates, so
    the base URL belongs to the consumer, not to The Mobility House. The provider documents the destination only as a customer-supplied
    HTTPS URL.'
  tags:
  - Webhook
  - Charging Sessions
  - Billing
  - Data Export
  tags_raw:
  - Webhooks
  - Charging Sessions
  - Billing
  - Data Export
  properties:
  - type: Documentation
    url: https://tmh-help.freshdesk.com/en/support/solutions/articles/203000046009-chargepilot-charging-data-push-api
  - type: Webhooks
    url: asyncapi/the-mobility-house-webhooks.yml
common:
- type: Website
  url: https://www.mobilityhouse.com/int_en/
- type: Documentation
  url: https://tmh-help.freshdesk.com/en/support/solutions/203000060458
- type: APIReference
  url: https://vdv-docs.tmh.energy/
- type: GettingStarted
  url: https://vdv-docs.tmh.energy/initial-connection/initial-connection/
- type: Support
  url: https://tmh-help.freshdesk.com/en/support/home
- type: HelpCenter
  url: https://tmh-help.freshdesk.com/en/support/home
- type: Blog
  url: https://www.mobilityhouse.com/int_en/unser-unternehmen/newsroom
- type: GitHubOrganization
  url: https://github.com/mobilityhouse
- type: SignUp
  url: https://www.mobilityhouse.com/int_en/contact
- type: TermsOfService
  url: https://www.mobilityhouse.com/int_en/terms-conditions
- type: PrivacyPolicy
  url: https://www.mobilityhouse.com/int_en/privacy-policy
- type: StatusPage
  url: https://status.tmh.energy/
- type: ChangeLog
  url: https://www.mobilityhouse.com/int_en/chargepilot/product-updates
- type: LLMsTxt
  url: llms/the-mobility-house-llms.txt
- type: Packages
  url: packages/the-mobility-house-packages.yml
- type: SDKs
  url: packages/the-mobility-house-packages.yml
- type: Webhooks
  url: asyncapi/the-mobility-house-webhooks.yml
- type: Authentication
  url: authentication/the-mobility-house-authentication.yml
- type: ErrorCatalog
  url: errors/the-mobility-house-problem-types.yml
- type: Conventions
  url: conventions/the-mobility-house-conventions.yml
- type: Idempotency
  url: conventions/the-mobility-house-conventions.yml
- type: Conformance
  url: conformance/the-mobility-house-conformance.yml
- type: Lifecycle
  url: lifecycle/the-mobility-house-lifecycle.yml
- type: DataModel
  url: data-model/the-mobility-house-data-model.yml
- type: ChangeLog
  url: changelog/the-mobility-house-changelog.yml
- type: Plans
  url: plans/the-mobility-house-plans-pricing.yml
- type: RateLimits
  url: rate-limits/the-mobility-house-rate-limits.yml
- type: DomainSecurity
  url: security/the-mobility-house-domain-security.yml
x-enrichment:
  date: '2026-08-30'
  status: enriched
  artifacts_added: 15
  pass: local-v1
x-coverage:
  state: covered
  reason: null
  detail: ChargePilot ships a public, machine-reachable, standards-based integration surface — a VDV 463 WebSocket interface
    with a seven-section technical guideline at vdv-docs.tmh.energy, a documented outbound Charging Data Push-API, and a published
    Modbus TCP register map — plus a served llms.txt and a first-party OCPP library on PyPI. What it does not publish is any
    OpenAPI, AsyncAPI, MCP server or agent card.
  evidence:
  - url: https://vdv-docs.tmh.energy/
    status: 200
  - url: https://www.mobilityhouse.com/llms.txt
    status: 200
  - url: https://status.tmh.energy/
    status: 200
  checked: '2026-08-30'

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/the-mobility-house"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/the-mobility-house/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/the-mobility-house/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

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