Launching today
EnergyAtIt
Build on the API layer between AI agents and the power grid
51 followers
Build on the API layer between AI agents and the power grid
51 followers
Data centers are the largest energy buyers on earth — but they can't talk to the grid. The protocols are from the 1990s - we translated all 8 into REST APIs and MCP tools. What you can do today: → Ask Claude to "dispatch a battery at 2MW" — it does it → Generate a cryptographic carbon attestation in one API call → Read real-time grid carbon intensity per facility → Auto-detect energy subsidies your building qualifies for 200+ REST endpoints. 15 MCP tools. Live sandbox — no signup needed.
For the curious — here's how it works under the hood: EnergyAtIt sits between grid protocols (IEC 61850, DNP3, Modbus, OpenADR) and modern APIs. Think of it as Plaid, but instead of connecting to bank accounts, you're connecting to substations and batteries. The MCP server means any AI agent (Claude, GPT, etc.) can control energy infrastructure through natural language. Happy to go deep on the protocol translation if anyone's interested.
Quick start if you want to try it right now:
npx @energyatit/mcp-server
Add it to Claude Desktop and ask: 'What energy assets are available?' — the sandbox responds with live data. No API key needed.
If you're building anything that touches energy — EV charging, building automation, carbon reporting, demand response — these are the APIs you'd otherwise spend 6 months building yourself
v0.2.0 just shipped — zero config, no API key needed.
We heard the feedback: "I tried npx and got Authentication required." Fixed. Here are 3 ways to start building right now:
1. MCP Server (for Claude Code / Claude Desktop)
npx @energyatit/mcp-server@0.2.0
Then ask: "What energy assets are available?" — it returns 3 data centers, 12 assets, 30 days of meter readings. No env vars, no signup.
2. REST API (curl / Postman / any language)
curl https://energyatit.com/api/v1/demo/sites
curl https://energyatit.com/api/v1/demo/dr/events
curl https://energyatit.com/api/v1/demo/carbon
Public endpoints. No auth header. JSON back instantly.
3. Want write access? One POST.
curl -X POST https://energyatit.com/api/v1/sandbox/provision
Returns a sandbox API key. Dispatch commands to batteries, create DR events, write carbon records — all scoped to your sandbox.
What you can build with this:
- EV charging optimizer (we speak OCPP 2.0)
- Carbon accounting dashboard (hash-chained attestation built in)
- Demand response agent (Claude dispatches load curtailment via natural language)
- Building energy manager (Modbus + BACnet + OpenADR in one API)
Docs: energyatit.com/developers
npm: npmjs.com/package/@energyatit/mcp-server
What are you building? Drop it below — happy to help wire it up.
Everyone's building AI wrappers.
Few are controlling real infrastructure.
EnergyAtIt just shipped an MCP server that lets Claude/GPT talk to 8 grid protocols — the same ones running actual substations and data centers:
What you can do right now, zero config:
- Query 3 live data centers (Dubai, Riyadh, Abu Dhabi) — sites, 12 assets, 6 grid connections, 30 days of meter data
- Dispatch commands to batteries (BESS charge/discharge/curtail)
- Create and settle demand response events with carbon attestation
- Read hash-chained carbon records with SHA-256 verification
- Pull integration status across Modbus, OpenADR 2.0b, IEC 61850, OCPP 2.0, DNP3, BACnet
- Auto-provision a sandbox with one POST — get a scoped API key, dispatch to your own assets
Run:
npx @energyatit/mcp-server@0.2.0
Ask: "What energy assets are available?"
Ask: "Dispatch Dubai BESS Alpha at 8MW for 30 minutes"
Ask: "Show me the carbon chain for this facility"
Or go REST:
curl https://energyatit.com/api/v1/demo/sites
curl https://energyatit.com/api/v1/demo/carbon
curl -X POST https://energyatit.com/api/v1/sandbox/provision
This isn't a wrapper. It's the translation layer between 1990s grid protocols and modern APIs.
Docs: https://energyatit.com/developers
npm: https://npmjs.com/package/@energyatit/mcp-server
What would you build on top of energy infrastructure APIs?