01 · APIs
Two API generations
The public Greenbyte API covers the Greenbyte and APM side, while the Drive API catalogue sits behind a sign-in portal. Which one you can use depends on your product history, and the blueprint settles it first.
For renewable IPPs running Power Factors Unity
A Power Factors MCP server that answers from Unity with read-only tools under your own permissions
A Power Factors MCP server gives Claude, ChatGPT or Copilot read-only tools for sites, active alerts, time series, downtime events and tasks in Unity. Power Factors documents the Greenbyte API in public, with API keys scoped per endpoint. Power Factors ships no MCP server as of 21 September 2026, so Pexon builds one against your tenant.
What we build
A first Power Factors Unity tool list, written as the manifest your IT team signs
Built on what Power Factors documents: sites and devices, data signals, time series (aggregated, real-time, high resolution), statuses and alerts, power curves, tasks with comments and files, downtime events, HSE incidents and worklog items. Backends named below are documented resources; "confirmed in blueprint" means the vendor documentation sits behind a login and the resource is checked against your release first.
# power-factors-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
list_sites: # -> sites with IDs and metadata
backend: GET /sites
mode: read
list_active_alerts: # device IDs or site -> active alerts
backend: GET /activealerts
mode: read
get_timeseries: # device IDs, data signal IDs, start, end, resolution -> aggregated values
backend: GET /data
mode: read
list_downtime_events: # site, period -> downtime events
backend: GET /downtime-events
mode: read
list_tasks: # site, status -> tasks with comments
backend: GET /tasks
mode: read
audit: every call logged with user, tool, arguments and the Power Factors Unity responseThe manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.
Checked 21 September 2026
Power Factors Unity at a glance: interfaces, access and what exists for AI
| What we found | |
|---|---|
| Interfaces | Greenbyte API 2.1 / 2.2-beta (REST/JSON, docs public): public OpenAPI at {customer}.greenbyte.cloud/api/2 for sites, devices, data signals, time series, statuses, alerts, tasks and downtime events; read endpoints only in the spec · Power Factors APIs (Drive) developer portal (REST/JSON, docs behind customer or partner login): Azure API Management portal; the API list is empty without sign-in, self sign-up exists |
| Authentication | The Greenbyte API takes an API key in the X-Api-Key header, scoped by per-endpoint permissions. Drive users sign in with Azure Active Directory SSO; how the Drive API authenticates is not visible without a portal login. |
| Vendor MCP server | No vendor server. No Power Factors MCP server found; the vendor's AI is REMI, embedded in Unity, with no external agent interface mentioned. |
| Vendor AI assistant | Unity REMI (Renewable Energy Management Intelligence) is an agentic engine that automates error-code investigation and signal correlation inside Unity, moving from recommendations towards autonomous actions. |
| Other connectors | None found. |
Power Factors (US). Large renewable IPPs, asset managers and O&M providers running wind, solar, storage and hybrid portfolios, such as Repsol, ENGIE, EDF Renewables and Lightsource BP; Power Factors states 310 GW across 18,000 sites and more than 600 customers in over 70 countries.
Why Power Factors Unity is hard for agents
Where a Power Factors Unity connection needs engineering, not configuration
02 · Naming
Drive and Greenbyte became Unity
The product names moved from Drive and Greenbyte to Unity, and customer tenants may run different stacks. Documentation, tenant URL and API key all have to match what you actually run.
03 · Lookup
Signal and device IDs come first
Signal and device IDs are tenant-specific. The connector looks them up through /devices and /datasignals before any /data query, otherwise the model asks for signals that do not exist.
04 · Overlap
REMI already covers work inside Unity
Power Factors' own REMI agent targets the same investigations inside Unity. An external connector has to earn its place outside Unity, for example by joining alerts with ERP, contracts or e-mail.
Power Factors Unity holds the records. An assistant without a governed way in answers from whatever someone pasted into the chat. The connector is the governed way in: named operations, the person's own permissions, every call logged.
What the connector answers, and what it will not do
Questions it answers
- Which turbines or inverters at site X have active alerts right now, and since when?
- What was the daily production of site Y last month?
- Which open tasks and downtime events are linked to site Z this week?
What it will not do
- Read more than the API key and the asking user's role allow; endpoint permissions come from Power Factors, not from the connector.
- Write anything: the documented Greenbyte API has read endpoints only, so this connector is read-only.
- Replace REMI inside Unity: error-code investigation there stays with Power Factors.
When this is the wrong page
If the work is investigating error codes and correlating signals inside Unity, REMI does that and Power Factors maintains it. A connector is right when Claude, ChatGPT or Copilot has to combine Unity data with systems outside it, such as ERP, contracts or e-mail.
Start with the Readiness Blueprint.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your Power Factors Unity owners and checks every backend against your release and licence. Week two tests whether a person's own Power Factors Unity permissions reach through the connector. You keep the manifest and a costed build plan, whoever builds it. All prices are net and exclude VAT.
What we need from you: a named Power Factors Unity administrator, a test or sandbox system we may call, and one business owner who can say which questions the assistant should answer first. The first production connector is usually a use-case pilot from €15,000; it runs in your environment, and the code is yours.
Related
- Connectors for 100 source systems — the dated catalogue this page belongs to
- Claude MCP server development — how we build an MCP server for any internal system
Questions Power Factors Unity teams ask before the first tool call
Does Power Factors have its own MCP server?
Not as of 21 September 2026. Power Factors' AI is REMI, an agentic engine embedded in Unity, with no external agent interface mentioned. An MCP server for assistants outside Unity has to be built against the Greenbyte API or the Drive API.
Do we need extra Power Factors licences or access for an AI connector?
You need an API key for your tenant with the right endpoint permissions, and for the Drive API a sign-in to the Power Factors API portal. Check with Power Factors which API your product generation uses and what access costs; the blueprint answers this first.
Can the assistant see data a user is not allowed to see in Unity?
No. The API key is scoped to the endpoints you grant, and the connector adds the asking person's role on top. Two users asking the same question can get two different answers, and that is tested before go-live.
What does a Power Factors Unity connector cost?
The two-week Readiness Blueprint is fixed at €4,900: agreed tool list, backends checked against your release, identity tested end to end, costed build plan. The production connector is usually a use-case pilot from €15,000. Prices are net, excluding VAT.
Next step
Not a sales call. An architecture call.
Thirty minutes with the engineer who would build the connector, with your Power Factors Unity administrator in the room if you like.