EPEX SPOT
EPEX SPOT SE, the European Power Exchange, operates the organised short-term electricity markets across thirteen European countries - day-ahead and intraday auctions on the MATS trading system and continuous intraday trading on the M7 trading system. Day-ahead prices set on EPEX SPOT are the reference for much of the European power sector. EPEX SPOT exposes real machine-readable interfaces, but none of them are open self-serve APIs - trading APIs (MATS, M7) require exchange membership, and read-only market data APIs and SFTP file feeds require a paid Market Data Services subscription ordered through the EEX Group Webshop.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles EPEX SPOT the way a machine reads it — 6 machine-readable artifacts across 4 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 — EPEX SPOT scores 18.4/100 (emerging), with a separate agent-readiness read of 0/100 (human only). 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile EPEX SPOT
Each block below is one kind of artifact we hold for EPEX SPOT. 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 4
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.
EPEX SPOT Day-Ahead and Intraday Auction Market Data API
Read-only API subscription (Day-Ahead and pan-EU Intraday API Read-only, EUR 1,040.00/month for internal usage) delivering day-ahead and intraday auction results - prices and vo...
EPEX SPOT Continuous Intraday Market Data API
Read-only API subscription (Continuous API Read-only, EUR 3,360.00/month for internal usage) giving real-time access to production data - all trades and orders - on the continuo...
EPEX SPOT MATS Auction Trading API
Member trading API for the Multiple Auction Trading System (MATS), the platform that replaced the legacy ETS system for all EPEX SPOT auction markets. Supports submission of lin...
EPEX SPOT M7 Intraday Trading API
Member trading API for the M7 trading system that runs all EPEX SPOT continuous intraday markets. Clients exchange standardized messages with M7 over an AMQP (Advanced Message Q...
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Security Posture 1
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.
Resources
Every other property we hold for EPEX SPOT — 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.
Documentation 1
Reference material describing how the API behaves
Access & Security 1
Authentication, authorization, and security posture
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/epex-spot · machine-readable index on apis.io