Contact

Developers & AI (MCP)

Build on connected batteries — or just ask your AI.

Connect Claude, Cursor, or any MCP-compatible AI assistant to inspect battery health, register fleet assets, and onboard customers in plain English — or integrate directly with our certified REST APIs.

Request API credentials

Zero-Tech AI Integration (MCP)

Connect your batteries to AI without writing code.

Our built-in Model Context Protocol (MCP) server translates technical BMS metrics (millivolt cell balance, pack current, and gateway freshness) into everyday language and lets you manage batteries by serial number or customer email.

Paste into claude_desktop_config.json
{
  "mcpServers": {
    "evolve-energy": {
      "command": "node",
      "args": [
        "/Applications/Tech/ManTech Studio/coding/evolve-energy/tools/evolve-mcp-server/index.mjs"
      ],
      "env": {
        "EVOLVE_MCP_URL": "https://us-central1-tms-evolvix-energy.cloudfunctions.net/api/v1/evolve/mcp",
        "EVOLVE_EMAIL": "you@example.com",
        "EVOLVE_PASSWORD": "<YOUR_EVOLVE_PASSWORD>"
      }
    }
  }
}

Ask your AI in plain English (Click any prompt to copy)

Certified API endpoints

The canonical Evolve API surface.

All operations are served via the canonical Cloud Function API. Requests require a verified Firebase ID token and are strictly evaluated against organization membership or asset access grants.

FamilyMethodEndpoint PathRequired Scope
AI & MCP ServerGET, POST/v1/evolve/mcpAuthenticated User (JSON-RPC 2.0)
Identity & ContextGET/v1/me/evolve/contextAuthenticated User
Customer BatteriesGET/v1/me/evolve/batteriesCustomer Grant
Customer TelemetryGET/v1/me/evolve/batteries/{batteryId}/telemetry/latestAsset Read
Organization BatteriesGET, POST/v1/evolve/batteriesevolve.battery.read / create
Fleet TelemetryGET/v1/evolve/batteries/{batteryId}/telemetry/latestevolve.telemetry.read
Gateway DevicesGET, POST/v1/evolve/devicesevolve.device.read / create
Vehicles & AssetsGET, POST/v1/evolve/vehiclesevolve.vehicle.read / create
Incidents & DiagnosticsGET/v1/evolve/incidentsevolve.incident.read
BLE Control GrantsPOST/v1/evolve/ble/grantsevolve.ble.grant

Standard Request Headers

GET https://us-central1-tms-evolvix-energy.cloudfunctions.net/api/v1/evolve/batteries/bat_demo_01/telemetry/latest
Authorization: Bearer <FIREBASE_ID_TOKEN>
x-business-id: biz_example_org

Verified Telemetry Payload (200 OK)

{
  "batteryId": "bat_demo_01",
  "connectionState": "LIVE",
  "receivedAt": "2026-09-29T16:45:00.000Z",
  "latest": {
    "stateOfChargePct": 88.5,
    "packVoltageV": 52.4,
    "packCurrentA": 8.2,
    "powerW": 429.68,
    "temperaturesC": [31.5, 32.0, 31.8],
    "cellVoltagesMv": [3282, 3284, 3281, 3285, 3283, 3279, 3284, 3282],
    "isBalancing": true,
    "activeFaults": []
  }
}

Standard Error Format (403 Forbidden)

{
  "error": {
    "code": "FORBIDDEN",
    "message": "Caller lacks evolve.battery.read permission for this asset.",
    "requestId": "req_8f92b7c4"
  }
}

Integration Principles

How partner integrations work.

  • Cryptographic device identity

    Hardware gateways authenticate using secure challenges and project-bound session secrets. No hardcoded device tokens.

  • Tenant & asset isolation

    Every organization's data is isolated. Cross-tenant access is strictly denied at both the API gateway and Firestore security rules.

  • Real-time & offline capable

    Telemetry operates live over cellular/Wi-Fi or synchronizes historical records locally via authorized P-256 signed BLE sessions.

Planning an integration?

Contact our engineering team to receive sandbox credentials, integration guides, and technical onboarding support.

Talk to Evolvix