Engrate
Engrate provides a unified platform for energy market communication, enabling balance responsible parties and suppliers to integrate with multiple energy markets through a single API. The solution abstracts diverse market protocols, message formats, identifiers, and deadlines, allowing seamless asset trading across bidding zones. By offering a comprehensive market communication layer, Engrate reduces integration complexity, accelerates time‑to‑market, and supports cost‑of‑energy analysis, documentation, and developer tools. Book a demo or explore the docs to learn how Engrate simplifies energy market interactions.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Engrate the way a machine reads it — 35 machine-readable artifacts across 2 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Engrate scores 45.3/100 (developing), with a separate agent-readiness read of 61/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-10-17 · rubric v0.24.0
Put this on your own site. The badge is drawn live from Engrate's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/engrate/"
title="Engrate on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/engrate.svg"
alt="Engrate Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/engrate/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/engrate/"
title="Engrate on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/engrate/card.svg"
alt="Engrate Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Engrate
Each block below is one kind of artifact we hold for Engrate. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 18
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Engrate Audit Logs API
The audit-logs API from Engrate — 1 operation(s) for audit-logs.
Engrate Benachrichtigung API
Abonnement von Änderungsereignissen.
Engrate Betrieb API
Umsetzungsstand und Betriebsinformationen.
Engrate Clearing API
Abweichende Sichtweisen als Vorgang mit definiertem Endzustand.
Engrate Core API
The Core API from Engrate — 5 operation(s) for core.
Engrate Cost Of Energy API
The Cost Of Energy API from Engrate — 5 operation(s) for cost of energy.
Engrate Geo API
The geo API from Engrate — 1 operation(s) for geo.
Engrate Holidays API
The holidays API from Engrate — 1 operation(s) for holidays.
Engrate Lokationen API
Einzelressourcen der referenzierten Netz-, Markt- und Messlokationen.
Engrate Lokationsbündel API
Abruf und Pflege von Lokationsbündeln in der Hoheit des Netzbetreibers.
Engrate Mabis API
The mabis API from Engrate — 13 operation(s) for mabis.
Engrate Netzbetreiberwechsel API
Übergabepaket beim Wechsel des zuständigen Netzbetreibers.
Engrate Nl Settlement API
The nl-settlement API from Engrate — 4 operation(s) for nl-settlement.
Engrate Profiles API
The profiles API from Engrate — 2 operation(s) for profiles.
Engrate Reference API
The reference API from Engrate — 2 operation(s) for reference.
Engrate Schedules API
The schedules API from Engrate — 10 operation(s) for schedules.
Engrate Status Request API
The status-request API from Engrate — 1 operation(s) for status-request.
Engrate Time Series API
The Time Series API from Engrate — 3 operation(s) for time series.
Scroll within the panel for all 18 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Engrate Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Engrate API Rules
SPECTRALJSON Schema 12
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
ClearingCaseWrite
JSON SCHEMAClearingPeriodResponse
JSON SCHEMAImplementationStatus
JSON SCHEMAMarketLocationDocument
JSON SCHEMAMeteringLocationDocument
JSON SCHEMANetworkLocationDocument
JSON SCHEMAObjectionResponse
JSON SCHEMAScheduleSeriesResponse
JSON SCHEMAScheduleVersionResponse
JSON SCHEMASimplifiedTariffResponse
JSON SCHEMASubscriptionWrite
JSON SCHEMATariff
JSON SCHEMAScroll within the panel for all 12 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Engrate — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/engrate · machine-readable index on apis.io
This is an independent, third-party profile of Engrate, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.