Eve Connect is one verb set reached through many surfaces
Module:
None(driver-facing, no workspace module required) | Role: EV driver | Licence: Free+ | Auth: ev.energy account login (Clerk OAuth)
Audience: anyone who wants the map of how Eve Connect is put together: drivers, partners, and the ev.energy team. The driver-facing overview is connect; the verb detail is connect/verbs.
Eve Connect is one set of verbs, over one backend, reached through several surfaces, reasoning about five kinds of information. The axes are independent: any surface can use any verb about any kind of information, and a fact reaches every surface the same way.
Rendering differs by surface, the facts do not
SURFACES chat · voice · your own AI client (MCP) · your own agent (A2A) · account page · the app
│
one shared assistant + one verb set
│
VERBS Read: my_account, discover Onboard: connect_device, join_program
Change: update_account, update_device History: my_transactions
Leave: remove_device, leave_program Share: refer_friend
│
INFORMATION Programme · Device · Location · Account · Why
│
FIELDS the details inside each record (see below)
Chat shows text and buttons, voice speaks and puts links on your screen, an AI client gets structured results. The content is identical, because it comes from the same verb reading the same source.
The verbs are shared by construction. The instructions are not, and that decides where a rule belongs. Chat gets Eve's full prompt plus a lifecycle overlay. Voice gets the prompt plus a transport delta. An MCP client is offered the prompt as server instructions and may ignore it. So anything that must be true on every surface has to live in the verb's result, not in prose. That is why confirmation gates, the one-programme-at-a-time switch, and the "search near this postcode" lookup are all properties of the verb rather than instructions to a model.
Every surface runs the same verbs against the same account
| Surface | Where | What it is |
|---|---|---|
| Hosted chat | eve.ev.energy/connect | Type to Eve in the browser |
| Voice | /connect/voice | Talk to Eve; links appear on your screen |
| Your AI client (MCP) | /connect/mcp | Use Eve's verbs inside Claude, ChatGPT, Cursor |
| Account page | /connect/account | Your referral QR, AI-client setup, and a summary of your cards (a charging card shows only its last four characters) with links to manage them |
| Card pages | /connect/rfid-cards, /connect/payment-cards | Activate and manage the charging cards you tap; add the payment cards you pay with |
| Notifications bell | beside your account chip on every signed-in page | What happened on your account, grouped Today / Yesterday / Earlier; a dot shows unread ones, opening it marks them read, and it updates as things happen |
| The ev.energy app | app stores | The visual companion: live state, charts, and actions Eve hands off |
You sign in once, with your ev.energy account. You reach the card pages from the account menu or from the Cards section of your account page. Eve manages the same cards through her four card verbs, and the pages and the verbs share one card layer, so they always agree on a card's status. Eve never takes a bank card number in conversation: adding a payment card always happens on the secure page. The organisation that issued a charging card can also pause or block it. Every other surface runs the same verbs against the same account, so what Eve knows does not depend on which one you use. How each surface takes a new driver from "stranger" to "signed in" is its own topic; see the internal channels design.
Fifteen verbs cover everything Eve does
They group by what you are trying to do. Full detail in connect/verbs.
| Group | Verbs | For |
|---|---|---|
| Read | my_account, discover | See your account; browse programmes, tariffs, devices |
| Onboard | connect_device, join_program | Add a car; join an earnings programme |
| Change | update_account, update_device | Set your location, tariff, charge limit (payout method is set in the app) |
| History | my_transactions | Your account over time: earned, spent, saved, energy and pending, with the items behind them |
| Leave | remove_device, leave_program | Disconnect a device; leave a programme |
| Share | refer_friend | Your referral link and QR |
| Cards | activate_charging_card, add_payment_card, update_card, remove_card | Activate a charging card you hold; add a payment card on the secure page; make a card the default or pause it; remove a card or report one lost |
| Notifications | my_notifications | What happened on your account (a charge, a declined card, a refund), in words written for you; showing them marks them read everywhere |
my_account runs first on every turn. It is the read that grounds Eve's answer in your real account.
Every driver question maps to one of five kinds of information
| Kind | The question | Answered with |
|---|---|---|
| Programme | What can I join? What am I in? How do I earn? | discover (programmes available / mine), join_program, leave_program |
| Device | Will my kit work? Is it connected? Change a setting? | connect_device (vehicles), discover (my devices), update_device |
| Location | Available where I live? Which tariff? | update_account, discover (tariffs / suppliers) |
| Account | Who am I? How am I paid? How am I doing? What happened? | my_account, my_transactions, update_account, refer_friend, my_notifications |
| Why | Why ev.energy? How much could I save? | Eve's answer, cited to the public ev.energy site |
You keep your tariff when you join a programme
Supplier, tariff and programme get confused, so Eve keeps them apart. You can have all three at once.
| Supplier | Tariff | Programme | |
|---|---|---|---|
| What it is | The company that sells you electricity | The named rate plan your supplier puts you on | An earnings or smart-charging scheme you join |
| Example | Octopus Energy, OVO, E.ON Next | Octopus Go, Intelligent Octopus Go, OVO Charge Anytime | Charge & Earn, ev.energy UK |
| How Eve handles it | Comes with your tariff | update_account (setting your tariff) | join_program / leave_program |
| How many | One | One | One at a time: joining a new one leaves the current |
Charge & Earn is a programme, not a tariff. You join it, and you keep whatever tariff you are on with your supplier. A tariff decides what you pay per unit; a programme decides how you earn from being flexible. They are independent axes, which is why the setup wizard asks for them as separate steps (Tariff, then Earnings). They touch in one place: some programmes exclude certain smart tariffs (Charge & Earn does not admit tariffs that already let your supplier control your charging), and that is stated in the programme's eligibility, not by making the tariff a programme.
A programme record carries the same fields on every surface
Each of these driver-facing fields reaches Eve identically everywhere:
name, description, benefits, eligibility_criteria, sponsor, country, sign-up link, FAQ link, support email, payment frequency / day, and the joining links.
Rich text (description, benefits, eligibility) is reduced to clean, readable text before Eve uses it, so it reads and speaks the same everywhere.
Savings and earnings are two different things
Eve keeps them apart:
| Savings | Earnings | |
|---|---|---|
| What it is | Your bill going down from smart charging | Cash a programme pays you for being flexible |
| Whose it is | Your account, and everyone who smart charges has them | Your programme, and only members of an earnings programme have them |
| Where the number comes from | my_transactions → saved, from your charging history, plus the headline estimate | my_transactions → earned: per-session charging incentives plus rebates paid to the account. What a programme advertises it pays is on the programme record |
Smart charging with ev.energy lowers your bill (savings). Joining an earnings programme, such as Charge & Earn, pays you on top (earnings). One is about your account and tariff; the other is about the programme you join. Your tariff is not a programme, and a programme is not a tariff, as the section above sets out.
That split is easy to get wrong, so the two stay distinct measures on one statement. The headline figure (£450 / $575 / €500 per EV per year) is a savings baseline, so quoting it as earnings crosses the axes. my_transactions returns both, side by side: saved is your bill going down, earned is what a programme paid you (per-session charging incentives plus rebates paid to the account). The one money number still missing is battery and solar earnings: v2 has their device state but no payout ledger, so it is not on my_transactions rather than shown as a guessed total, tracked internally as a core data request.
Every fact Eve states has a public home
One rule holds the whole architecture together:
Every fact Eve states about a programme, a device, a location or a number has a public home: the ev.energy API or a public web page. Eve never states a fact she cannot point you to.
If Eve cannot confirm something, she says so, rather than guessing. Numbers come from your account or a published figure with a source, never from memory. That is why what Eve tells you matches what you would find on the ev.energy site and in the app.