VaDa Genius

VaDa Genius helps people prepare and understand their home energy context before asking ChatGPT about solar panels, consumption, batteries, tariffs, and automation. The app guides users through their current situation — whether they already have solar panels or are considering installing them — and uses connected or declared energy data to provide clearer, more grounded context for the conversation. VaDa Genius does not replace a certified installer, electrical study, legal advice, or a guaranteed savings calculation. It helps users ask better questions and make better-informed energy decisions.

View in the ChatGPT registry

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Data & Analytics
Primary Subcategory: Utility & Energy Plan Comparison
Secondary Subcategories: None listed
Brand: VaDa SmartHouse
Access: Account required
First tracked: 2026-08-13
Tool count: 28
Geography: US

ChatGPT Plugin Discoverability Score

ChatGPT organic discovery is not live yet

VaDa Genius is tracked in the ChatGPT Plugin registry. Public organic-discovery measurement is not live for ChatGPT yet, so there is no score to publish today.

Get notified when your score goes live

Enter your work email and we’ll notify you when ChatGPT Plugin organic discovery scoring launches.

No spam. Unsubscribe any time.

Talk to our team

Primary Subcategory

Competing in ChatGPT Utility & Energy Plan Comparison

View Category

Listed in alphabetical order

Primary Subcategory

Energy OgreOrganic discovery is pendingGet the score at launch

Facile.it EnergiaOrganic discovery is pendingGet the score at launch

LeLynx.fr ÉnergieOrganic discovery is pendingGet the score at launch

Overstappen.nlOrganic discovery is pendingGet the score at launch

Texas Electricity PlansOrganic discovery is pendingGet the score at launch

VaDa GeniusOrganic discovery is pendingGet the score at launch

Score explained

How the Discoverability Score works

Organic discovery scoring for VaDa Genius on ChatGPT is not live yet. The score will use measured agent conversations when it launches.

InvisibleBuriedEmergingCompetitiveWinning

Organic discovery scoring is pending. Your Plugin score will appear on this scale when measurement goes live.

FoundDiagnostic

Whether Claude found your Plugin in connector search. It must be Found before it can reach the picker, but the score counts picker appearances—not search results.

PickedMain score

How often your Plugin appeared in the picker, or Claude invoked it directly, across contested conversations. This percentage is the Discoverability Score; the headline number is rounded.

PositionedDiagnostic

What position your Plugin appeared in when it was shown in the picker. This shows prominence, but it does not affect the score.

Read the full scoring methodology Recommended guideHow to get your Claude Connector organically discoveredFollow the practical steps agents use to find, shortlist, and choose your Connector.

Tools

28 tools agents can invoke

Use this for contracted-power questions: P1/P2, whether to lower or raise power, maximeter, ICP risk, grid-demand peaks, or savings. Use a wide historical range, ideally 12 months. The main basis is power demanded from the grid by tariff period, not total house consumption. house_max_kw is explanatory context only.
solarbrain_analyze_contracted_power_demand
Use this when the user asks whether an electric car makes sense with their current installation, how many electric kilometers exported surplus could cover, or what EV usage could fit historical surplus. If the profile is DataDis/grid_only, call it exportacion a red or excedente visible, not measured solar surplus.
solarbrain_assess_ev_readiness
Use this when the user asks whether it is worth adding solar panels, expanding PV, adding battery capacity, or reviewing whether the installation is well sized. Provide an explicit date range and return evidence, caveats, and next steps. For contracted-power questions use the contracted-power tool.
solarbrain_assess_pv_battery_upgrade
Use this when the user asks to compare historical SolarBrain groups inside a date range, such as weekday vs weekend, month vs month, weekday patterns, or seasons. date_from and date_to are inclusive local dates. Supported group_by values are day_type, weekday, month, and season. For weather groups like sunny vs rainy, explain that weather cohorts are not yet available and use calendar cohorts or range summaries instead.
solarbrain_compare_energy_cohorts
Use this when the user asks whether their tariff is good, expensive, worth changing, or wants better tariff alternatives using recent SolarBrain billing months. The backend compares each candidate as a continuous tariff over the whole period and includes rolling wallet balances for month-behind compensation.
solarbrain_compare_tariffs
Use this when the user asks for solar reference production, PVGIS/JRC, solar potential, expected PV generation, or a kWp scenario. It estimates European reference production for a date range and scenario. For measured-vs-reference comparisons, also use measured history tools.
solarbrain_estimate_solar_potential
Use this when the user asks why something happened in their energy data, such as unusual import, export, low solar, high consumption, battery behavior, or an unexpected time slot. Use target_date and optional local times when the question is about a specific window.
solarbrain_explain_energy_anomaly
Use this when the user asks about historical energy patterns over a date range: hourly profile, night use, weekend vs weekday behavior, solar-window alignment, peak hours/days, or load-shifting opportunities. This is read-only pattern analysis; use contracted-power tools for P1/P2 decisions.
solarbrain_get_consumption_patterns
Use this when the user asks what VaDa Genius knows about their connected energy profile: installation, license, data sources, measured coverage, billing context, contracted power P1/P2, and available capabilities. It is read-only and focuses on energy context, not civil identity.
solarbrain_get_genius_energy_profile
Use this when the user asks what VaDa Genius recommends next: solar, battery, EV, tariff, automation, or contracted-power opportunities. It returns read-only opportunity cards with evidence, assumptions, missing data, risks, and next actions for an explicit date range.
solarbrain_get_genius_opportunities
Use this for Smart/EV installations when the user asks 'que hay encendido ahora', what VaDa has switched on now, which flexible loads are active, how much controlled power is running, or asks for a list/table of active devices. Use user_summary_es and active_assets for user-facing wording, locations, power, and timing fields when available; avoid technical IDs and avoid saying 'activos controlados encendidos'.
solarbrain_get_active_control_state
Use this when the user asks to test Auth0, verify SSO, check which SolarBrain user is logged in, or confirm whether ChatGPT is sending an authenticated OAuth token to the MCP server. This tool requires OAuth when Auth0 is enabled.
solarbrain_get_authenticated_user
Use this when the user asks whether the battery will charge fully, expected state of charge, evening discharge risk, battery forecast for today, or battery evolution by hour. Prefer human, by-hour reasoning when the backend returns hourly battery data.
solarbrain_get_battery_forecast
Use this when the user asks for an electricity bill, invoice estimate, monthly estimation process, current month cost, last month bill, import cost, export compensation, solar savings, wallet, or bill without solar comparison. Prefer bill_story.amount_to_pay_eur as the main payable amount, and use bill_story.formula_es plus bill_story.optimization_es to explain wallet, excedentes, and the goal of zero grid import with minimal export.
solarbrain_get_billing_estimate
Use this when the user only wants to know the current SolarBrain billing company, billing settings, tariff access, or contracted power settings. For Spanish 2.0TD, use contracted_power_context and keep P1 punta/llano separate from P2 valle; if only a single kW is visible, say that backend/MCP still lacks the split. This returns data only and does not open the editor UI.
solarbrain_get_billing_settings
Use this when the user asks what VaDa devices are configured, how they are named, where they are, their trigger availability, priority rules, average power, start/stop delays, or whether they are available now. This is read-only configuration; do not use it to switch devices on or off. Use display_name and location in answers, never technical IDs.
solarbrain_get_configured_assets
Use this when the user asks what is happening right now with PV production, home load, grid import/export, battery state, or current energy balance, including questions such as 'como esta la bateria ahora'. This returns data only, without the house widget.
solarbrain_get_current_energy
Use this when the user asks how today is going: solar generated so far, solar now, remaining forecast, battery outlook, export/import risk, or a short daily energy briefing. This is energy-only for the authenticated installation; use device tools for configured or active VaDa automations.
solarbrain_get_daily_outlook
Use this when the user asks about yesterday, today so far, a daily historical recap, or 'como fue ayer': solar generated, house consumption, grid import/export, battery behavior, device activation availability, and estimated variable cost. Do not answer that yesterday is unavailable before calling this tool for date_preset=yesterday.
solarbrain_get_daily_operational_summary
Use this when the user asks for current electricity prices, today's/tomorrow's prices, the cheapest hours today, expensive slots today, or whether consumption should be moved to a cheaper period today. For yesterday, this month, custom date ranges, or averages by P1/P2/P3, use solarbrain_get_energy_price_range.
solarbrain_get_energy_prices
Use this when the user asks for electricity prices over explicit or inferable date ranges such as ayer, hoy y ayer, este mes, mes pasado, average by tariff period, P1/P2/P3, cheapest or most expensive hours in a range, or price comparisons across days. date_from and date_to are inclusive local dates. This reads the price catalog independently from telemetry, so prefer it for complete full-day/month price analysis.
solarbrain_get_energy_price_range
Use this for measured energy totals over a custom date range: year-to-date, a season, summer/winter windows, Semana Santa, or any from/to period. Provide inclusive YYYY-MM-DD dates and granularity. For cohort comparisons, use the cohort tool.
solarbrain_get_energy_range_summary
Use this for measured energy in a specific local time slot or hourly window: export, import, solar, house consumption, or battery behavior between two times on a target date. Infer today only when the user clearly asks about hoy.
solarbrain_get_energy_time_window
Use this when the user asks about this month, last month, monthly history, 'este mes', or 'el mes pasado'. This returns the backend semantic analytics summary: measured house consumption when DataDis import is valid as consumption, grid import/export, contract context, data-quality flags such as export_anomaly, and known missing dimensions. Prefer this over raw monthly telemetry for DataDis/grid_only installations.
solarbrain_get_period_operational_summary
Use this when the user asks about solar generation today, tomorrow, remaining solar energy, the best solar hour, or solar production windows.
solarbrain_get_solar_forecast
Use this when the user asks what to run today or tomorrow, in what order, or when to place flexible loads such as washing machine, dishwasher, dryer, oven, iron, pool, air conditioning, or a custom appliance. This is read-only advice and never switches devices. For SMART/EV installations, first separate loads already active/configured in VaDa from manual loads; do not tell the user to start something VaDa is already managing.
solarbrain_plan_flexible_loads
Use this when the user asks whether to run a manual load now or today, such as a washing machine, dishwasher, dryer, oven, iron, or custom appliance.
solarbrain_recommend_manual_load
Use this only when the user asks for the visual house dashboard or explicitly asks about 'la casa' as a whole, for example 'muestrame la casa', 'como va la casa', or 'estado de la casa'. For direct questions about battery, solar production, grid, or what is switched on now, use the data/list tools instead.
solarbrain_show_live_house_snapshot

VaDa Genius FAQ

How do I improve a ChatGPT Plugin's discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are VaDa Genius alternatives on ChatGPT?

As of 2026-08-14, VaDa Genius competes with Energy Ogre, Facile.it Energia, LeLynx.fr Énergie, Overstappen.nl, Texas Electricity Plans in ChatGPT Utility & Energy Plan Comparison, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.