Skip to main content

Eve runs your devices so you save and earn

Module: None (driver-facing, no workspace module required) | Role: EV driver | Licence: Free+ | Auth: ev.energy account login (Clerk OAuth)

Private trial: Eve Connect is currently open to ev.energy staff only. Signing in with any other account is refused.

Audience: individual EV drivers (B2C). Reach Eve through hosted chat (/connect), voice (/connect/voice), your own AI client over MCP (/connect/mcp), or your account page (/connect/account). Same account, same verbs, same answers; only the rendering changes. The full map is in connect/ia.

Eve helps you save money on your bills and earn from the grid by running your devices (EV, charger, home battery, solar) when energy is cheap and the grid needs help most. Sign in once with your ev.energy account; Eve does the rest.

This page answers what Eve can do, how to reach her, what she sees about your account, and what's intentionally out of scope. If you're an ev.energy engineer or operator, the internal companion is at docs/internal/features/connect/.

Eve sets up five things, then runs your devices for you​

StepWhat it sets upExample
AccountYour ev.energy loginClick the sign-in button on the page. One round-trip to Clerk; you come back signed in.
DeviceConnect your car"Connect my Tesla" → Eve hands back the OEM auth link, you confirm, you're paired. Chargers, home batteries and solar inverters are paired in the ev.energy app today; once they are on your account Eve reads them, and can disconnect them, but she cannot do the initial pairing.
LocationThe postcode Eve schedules around"My postcode is RH1 1JS", and Eve writes this to your account so the right programmes appear.
TariffThe energy plan you're on"I'm on Octopus Go", so Eve can pick cheap charging windows correctly.
Earnings programmeThe one programme that pays you to flex"What can I join?", and Eve lists eligible programmes for your postcode and enrols you in the one you pick. You're in one earnings programme at a time; joining a new one automatically leaves the last.

Once those five are set, Eve runs your devices automatically against the cheap windows and the programme rules. You can then ask her anything in plain English:

  • "Is my car plugged in?" gives live state from the car, no app needed. (Chargers report no live plug state today.)
  • "How much have I saved this month?" gives your bill cuts from cheap-window scheduling, in your account currency.
  • "What tariff am I on?" gives the name and price details, including off-peak / peak windows.
  • "Boost charging now" is a manual override. Today Eve routes you to the ev.energy app for execution; reads pick up the result on the next turn. See "Eve hands you to the app for what she cannot do yet".
  • "Add another car" pairs a device without restarting the wizard.
  • "What programmes pay near me?" is local earnings discovery; Eve filters to ones you're eligible for. You can ask this before connecting anything: give Eve a postcode or ZIP and she searches near there without saving it to your account.
  • "Share my referral link" gives your permanent code, as a link and a QR.

Use Eve in your browser, or inside your own AI client​

1. Hosted chat runs in any browser at /connect​

Browser-based, mobile-friendly. Sign in, ask questions, get answers. The whole flow lives at https://eve.ev.energy/connect. No setup, no client install. Best if you don't already use Claude or another AI client. (The old /connect/chat link is gone: it now 404s. Everything lives at /connect.)

  • Mobile-first layout works on small screens, with safe-area-inset padding so iOS notches don't crop content.
  • The page is stateless by design: refresh and the chat resets. Nothing about a conversation is kept on your account; Eve only reads from the underlying ev.energy account state on each turn.
  • The chat reveals replies word-by-word for prose; structured content (lists, tables, headings) paints atomically so layout doesn't jump.
  • Tool calls show inline as a per-tool list with a green-disc tick on success or a red-disc X on failure, so you can see exactly what Eve did.
  • A mic in the composer lets you talk to Eve inline (the voice pill); the full voice page is at /connect/voice.

2. MCP puts Eve's verbs inside your own AI at /connect/mcp​

If you use Claude Code, Claude Desktop, Claude.ai, ChatGPT (with the MCP connector), Cursor, Gemini, or any other MCP-compatible AI client, point it at https://eve.ev.energy/connect/mcp:

{
"mcpServers": {
"ev-eve": {
"url": "https://eve.ev.energy/connect/mcp"
}
}
}

On first use the client opens a browser window for ev.energy sign-in, an ev.energy-branded page that never asks for your password. Sign in once; Eve's 15 enrollment verbs become available inside your AI client. Your conversation runs in your AI; Eve provides the tools, the data, and the underlying instructions (the SKILL prompt that teaches Eve how to talk about charging and earnings).

The same OAuth carries forward: once you've authorised an MCP client, repeated sessions use refresh tokens automatically. Tokens are scoped to the /connect surface so a workspace cookie from /eve can't grant MCP access, and vice versa.

Pick hosted chat if you have no AI client, MCP if you do​

Hosted chat is for drivers who don't already have an AI client they trust. MCP is for drivers who already live in Claude, ChatGPT or Cursor and want Eve's verbs available there. They share the same underlying ev.energy account state and the same enrollment verbs; the difference is where the conversation happens.

Eve reads your ev.energy account and nothing else​

  • Your ev.energy account is the only thing Eve reads: addresses on file, vehicles, chargers, charging history, the earnings programme you're in, savings figures.
  • Eve never asks for your password. Sign-in goes through ev.energy's OAuth (currently fronted by Clerk at clerk.ev.energy); Eve only ever sees the bearer token your browser passes through.
  • The token Eve sees is scoped to your account only. There is no admin, multi-account or "as another user" surface on /connect.
  • Conversations on /connect are stateless by design, with no permanent transcript on your account. What Eve knows on the next turn comes from the account, not from chat memory.
  • If you sign out, the session row in Eve's database is deleted and the browser cookie is cleared. Re-sign-in always starts a fresh session.

Eve hands you to the app for what she cannot do yet​

Real-time device control is coming soon. Acting on a device right now, whether that is triggering a boost, pausing a charge, locking the charger or dispatching the battery, is reserved for a future generalised control verb, waiting on a device-control action ev.energy is still building. Ask for one of these today and Eve routes you to the ev.energy app rather than fake a confirmation:

"I can't trigger that from chat yet. Open the ev.energy app to boost, lock, or dispatch."

No fake confirmations, no silent failures. Everything else is live. That covers reads (state, savings, your programme, tariff details, live charging) and writes: connect a car, remove any device, join or leave your earnings programme, and update your home address, tariff and payout method all complete against your account without an app round-trip.

Three jobs still happen outside chat, and none of them is a failure:

  • Pairing a charger, home battery or solar inverter happens in the ev.energy app. Eve reads them once they're on your account and can disconnect them; she just can't do the first pairing.
  • Programme earnings to date aren't readable here yet. Eve will tell you what a programme pays, and what you've saved on your bills. A running earnings total is coming with the API that exposes it.
  • Referral invites are a link you send, not an email Eve sends. Ask for your link or QR and share it however you like.

Eve talks in plain words and real numbers​

Friendly, direct, low-jargon. She won't say "VPP" or "DR event". She says "the grid asks for help". She talks about savings (cheaper bills from charging in cheap windows) and earnings (programme payments for flexing) as two different things, because they are: savings come from your tariff structure, earnings come from third-party programme payments.

She names real numbers from your account. She never invents figures. If something fails (an API hiccup, a permission gap), she says so plainly and points you to the app.

A handful of stylistic conventions she follows: one themed emoji per line at most (🚗🔌🏠⚡💰), single H3 headings, bold headline numbers, and a single > callout for the value-exchange punchline. Lists use proper bullets. Currency rendering matches your account locale.

Eve picks your currency and wording from your address​

Eve picks UK / US / EU silently from your account's address. Currency (£ / $ / €), word choice (tariff / rate plan), example tariffs (Octopus Go vs PG&E EV-2A), and headline savings figures (£450 / $575 / €500 per EV per year) all switch automatically. You don't have to tell her where you live; the address on your ev.energy account does that.

If your account is in a country without active programmes, Eve will tell you and surface a waitlist instead of pretending there's something to enrol in.

Your referral code is permanent, and every signup traces back to you​

Every driver has a permanent personal referral code, a short URL like https://eve.ev.energy/connect/r/<code> that you can share with a friend. Every signup through your link is tracked back to you.

What that's worth depends on where you are: the default is tracked-not-paid, and reward groups (postcode, ambassador, employer schemes) layer credits on top where they're running. So Eve will share your link happily and won't promise you a figure per friend. Ask her about your account's activity for anything concrete.

Ask Eve "share my referral link" or "what's my QR code?" and she'll surface a QR image you can show on screen or save to your phone. Eve never shares your link without you asking, and she can't email an invite on your behalf. The link is yours to send.

You can also ask for a link to a specific programme: whoever follows it is signed in, credited to you, and put on that programme in the same tap (unless they're already on a different one, in which case they're asked first rather than switched).

On Chrome for Android, the share page also lets you write your referral URL to a blank NFC tag. Hold the tag against the back of your phone and Eve writes the link to it. Friends can then tap that tag with their own phone (iPhone or Android) to open your referral page directly. Same code, same crediting, no app install needed. QR and link sharing still work everywhere else.

Talk to Eve at /connect/voice. Alexa is still on the roadmap​

Talk to Eve at /connect/voice. It is the same Eve, the same account and the same verbs as the chat. She just speaks, and puts links on your screen instead of reading them aloud. Anything that needs a tap (signing in, connecting your car, connecting a utility account) appears on screen as a link or a button at the moment Eve offers it.

The Alexa skill, voice-driven enrollment via "Alexa, ask Eve to connect my car", is still on the roadmap. Dictating into the hosted chat, or using your MCP client's own voice mode, works today too.

Short answers to the questions drivers ask most​

Does Eve store my chats? No. /connect is stateless: refresh resets the conversation, and the chat content is never written to a permanent transcript on your account. Your MCP client may store its own transcript; that's between you and your AI tool.

Can I use Eve without an ev.energy account? Not yet. Eve's data and verbs all flow through your ev.energy account; without one, there's nothing for her to read or write. You can sign up for ev.energy first, then come to /connect.

What if my AI client doesn't support MCP? Use the hosted chat at /connect. It runs in any modern browser.

How do I disconnect an AI client? Sign out of the MCP client (it'll forget the OAuth token), or use Eve to revoke the refresh token directly. The token-revocation flow goes through /connect/oauth/revoke per RFC 7009; your AI client will then need to re-OAuth on next use.

Is /connect the same as /eve? No. /eve is the workspace surface for utilities and fleet operators, with a different principal (workspace member, not driver), different module-gated tools and a different licence model. /connect is the B2C surface for individual drivers. They share the underlying tooling architecture but the sessions, OAuth, and stored state are completely separate (driver state lives in tables prefixed connect_*; workspace state lives in the shared tables).

What languages does Eve speak? English today (UK / US dialect by account locale). Additional languages follow the ev.energy app's roadmap.

Is there a mobile app? Not yet for /connect specifically; the hosted chat works fine on mobile browsers. A native iOS/Android wrapper is on the roadmap.

Start using Eve, or read about ev.energy itself​

  • /connect itself, the live driver surface: https://eve.ev.energy/connect
  • MCP setup snippets, copy-paste config for Claude Code, Claude Desktop, Claude.ai, ChatGPT, Cursor and the rest: on your account page at /connect/account
  • ev.energy proper, the company behind your account, devices, tariffs, and programmes: https://ev.energy