Energy Market Communication
Get your assets into the market. Keep them there.
See what you are responsible for, send the positions you intend to hold, read back what the market says you delivered, and keep the audit trail. One interface, whatever the market underneath asks for.
Getting started
Connect, and we'll build your portfolio
Connect
Use the API key and the credentials you already have. There's nothing to install.
We build your portfolio
We pull in the points you're responsible for, straight from the market. You don't load anything yourself.
Start
Send your first position and see what comes back. You can be live in days.
Capabilities
What you can do
Eight capabilities on one interface, grouped the way a market runs: who holds what, what you do each day, and what it came to.
Structuring
Portfolio
The accounting points you are responsible for, read from the market and kept current, master data included. See each point's state, with the market's own record beside it.
Structuring
Supplier switching
Take on a customer and have their accounting point registered to you on the day it should be. Move-ins and move-outs run the same way.
Operational
BRP nominations
Send the position you intend to hold before gate closure and revise it as your day changes. Day-ahead and intraday, internal and cross-border series, in quarter-hourly or hourly resolution. The API tells you when each market's gate opens and closes.
Operational
Physical scheduling and redispatch
Inform the grid operator of your intended asset schedule per resource or connection point, and take back the transport capacity you are allowed and the redispatch it asks for.
Operational
Trades
Your fills from the exchange and the trades you agreed bilaterally, held per counterparty the way settlement reads them.
Settlement
Metering data access
Validated meter values per accounting point, each value carrying how it was obtained and how final it is, so a preliminary estimate never reads as a settled figure.
Settlement
Settlement and imbalance
Read back what the market says was delivered and what your imbalance came to per settlement period, with the corrections the market issued afterwards. Reconcile it against what you nominated without exporting anything.
Across every capability
Audit trail and delivery status
Every message we composed on your behalf, every reply that came back, the version history behind it, and the state each submission is in right now. Searchable in the console and available over the API.
One delivery day
One delivery day,
from portfolio to the final settled figure
Start from your portfolio, declare tomorrow's position, revise it when the day changes, then read back what the market says you delivered.
- Portfolio
- in sync
- Declared
- 18.0 MW · 432.0 MWh
- Filed
- 14:30, sent
- Confirmed
- 426.0 MWh
- Delivered
- 427.2 MWh
- Imbalance
- +1.2 MWh, long
- Settled
- 37.20 EUR, paid
- Finality
- final
The whole day, in order
D-14 · You
Your portfolio is already in the market: the points you are responsible for, read from the market. A customer switching to you arrives the same way.
D-1 10:00 · You
Say what you plan to deliver tomorrow: a baseload block of 18 MW across the day. You give us the schedule and we communicate it to the market.
D-1 14:30 · Engrate
We turn that into the message this market expects and send it on straight away. What the market answers comes back to you as it arrives.
D-1 15:30 · The grid
The grid replies. Their numbers match yours, so tomorrow is agreed.
D 11:15 · You
Something changes. Drop the afternoon to 17.5 MW and we send the update. Nothing gets patched by hand; it's simply a newer version.
D+1 12:00 · Settlement
The market says what you actually delivered and puts a price on the gap. You delivered a little more than you promised, so you get paid. These numbers aren't final yet.
D+34 working days · Settlement
Weeks later the official numbers land and the day is settled for good. The earlier figures stay beside them.
D-14
You
Your portfolio is already in the market: the points you are responsible for, read from the market. A customer switching to you arrives the same way.
- Portfolio
- in sync
D-1 10:00
You
Say what you plan to deliver tomorrow: a baseload block of 18 MW across the day. You give us the schedule and we communicate it to the market.
- Declared
- 18.0 MW · 432.0 MWh
D-1 14:30
Engrate
We turn that into the message this market expects and send it on straight away. What the market answers comes back to you as it arrives.
- Filed
- 14:30, sent
D-1 15:30
The grid
The grid replies. Their numbers match yours, so tomorrow is agreed.
- Confirmed
- 432.0 MWh
D 11:15
You
Something changes. Drop the afternoon to 17.5 MW and we send the update. Nothing gets patched by hand; it's simply a newer version.
- Confirmed
- 426.0 MWh
D+1 12:00
Settlement
The market says what you actually delivered and puts a price on the gap. You delivered a little more than you promised, so you get paid. These numbers aren't final yet.
- Delivered
- 428.4 MWh
- Imbalance
- +2.4 MWh, long
- Settled
- 74.40 EUR, paid
- Finality
- preliminary
D+34 working days
Settlement
Weeks later the official numbers land and the day is settled for good. The earlier figures stay beside them.
- Delivered
- 427.2 MWh
- Imbalance
- +1.2 MWh, long
- Settled
- 37.20 EUR, paid
- Finality
- final
Why this is different
What is different
An API, on your timing
Your systems talk to the market directly, on your own timing, at whatever volume you need. Nobody is copying your positions into someone else's screen.
Declare the end state
One declaration per intent. When a market changes its rules, the change lands on our side and your codebase stays as it is.
One model for every country
Adding a market means configuring the model you already built against. You don't integrate a second time.
Questions
Common questions
Do we need to know each market's formats and rules?
No. You send us one message shape for every market. We speak each market's language underneath and keep up when the rules change.
Does Engrate make trading or commercial decisions?
No. Every decision is yours. We communicate it to the market and show you exactly what was sent and what came back.
Which roles does it serve?
Balance responsible parties and energy suppliers. Each product names the role it serves.
How do we get started?
Connect with an API key and the credentials you already have. We read the accounting points you are responsible for from the market, and you send your first position. Most teams are live in days.
Can a coding agent do the integration?
Yes. The docs are written for people and for agents, and an MCP server gives an agent the same API you use.
Start with one market. Add the rest when you need them.
Tell us what you operate and where. We will tell you what runs today and what your integration looks like.