MISO
MISO — the Midcontinent Independent System Operator — is the not-for-profit Regional Transmission Organization that operates the electric grid and the wholesale electricity markets across fifteen US states and the Canadian province of Manitoba, serving a footprint of roughly forty-five million people from headquarters in Carmel, Indiana. Formed in 1998 and operating the region since December 2001, it is regulated by the Federal Energy Regulatory Commission, dispatches generation in real time, clears day-ahead and real-time energy and ancillary services markets, runs the ARR/FTR market and the generator interconnection queue, and plans the transmission system. It sits squarely in the middle of the value chain: it owns no generation, no wires and no retail customers, but it holds the market-wide operational data that every generator, transmission owner, load-serving entity and trader in the Midwest and the South depends on. Its API posture is the classic system operator split, and it is an unusually clean example of it. On the market side MISO is genuinely open — thirty-seven JSON endpoints at public-api.misoenergy.org return real-time fuel mix, load, prices, binding constraints and interchange to an anonymous GET with no key, no account and no click-through, and the full market report archive at docs.misoenergy.org downloads anonymously as CSV and XLSX. On the consumer side there is nothing to open: MISO is not a retail utility, holds no customer usage or billing data, and no energy-data mandate of any kind applies to it. Green Button is voluntary in the United States and is a distribution-utility standard; MISO publishes no Green Button, ESPI, or consumer data-sharing surface, and makes no claim to. Its newer MISO Data Exchange developer portal adds a keyed but self-serve tier over historical market report data, and its MUI 2.0 market interface is a genuinely closed, client-certificate-gated API for registered market participants only.
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 MISO the way a machine reads it — 139 machine-readable artifacts across 7 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 — MISO scores 51.9/100 (developing), with a separate agent-readiness read of 32/100 (agent ready). 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.
Put this on your own site. The badge is drawn live from MISO'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/miso/"
title="MISO on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/miso.svg"
alt="MISO Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/miso/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/miso/"
title="MISO on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/miso/card.svg"
alt="MISO 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 MISO
Each block below is one kind of artifact we hold for MISO. 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 38
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.
MISO Market Reports
MISO's long-running bulk market report surface — the second fully anonymous layer of its open market data, and the archive the Data Exchange APIs sit on top of. Every published ...
MISO File Download API
The bulk file-retrieval counterpart to MUI 2.0, on the same two client-certificate-gated hosts and documented only in a PDF. MISO's File Download Specification lays out a consis...
MISO FTR MPMA Market User API
The Financial Transmission Rights / Multi-Period Multi-Auction market user API — four SOAP services covering the FTR market itself, auctions, bulk download and the secondary mar...
MISO EDR Service (Electronic Data Reporting)
A SOAP service for uploading meter data and offer data to MISO, with a published WSDL and six XSD schemas (MdUploadPayload, MdUploadResponse, MeterData, OfferData, OfferDataUplo...
MISO CROW API (Outage Scheduling)
The outage-scheduling interface, built on the CROW product, documented in a PDF reference plus a MISO-specific addendum and shipped with worked XML request and response examples...
MISO Fuel and Consumables Data Request API
Data request API for fuel and consumables information, documented in a 171KB PDF API guide on MISO's CDN and nowhere else.
MISO Market Portal Meter Data and Settlement Statements API
Market Portal API for retrieving meter data and settlement statements, documented in a 1MB PDF on MISO's CDN. Sits alongside the File Download API in the settlements area of the...
MISO Ace API
The Ace API from MISO — 1 operation(s) for ace.
MISO Admin API
The Admin API from MISO — 6 operation(s) for admin.
MISO Aggregated Pnode API
The Aggregated Pnode API from MISO — 1 operation(s) for aggregated pnode.
MISO Bidding API
The Bidding API from MISO — 2 operation(s) for bidding.
MISO Binding Constraints API
The BindingConstraints API from MISO — 3 operation(s) for bindingconstraints.
MISO Contracts API
The Contracts API from MISO — 4 operation(s) for contracts.
MISO Coordinated Transaction Scheduling API
The CoordinatedTransactionScheduling API from MISO — 1 operation(s) for coordinatedtransactionscheduling.
MISO Csat Next Day Short Term Reserve Requirement API
The CsatNextDayShortTermReserveRequirement API from MISO — 1 operation(s) for csatnextdayshorttermreserverequirement.
MISO Csat Supply Demand API
The CsatSupplyDemand API from MISO — 1 operation(s) for csatsupplydemand.
MISO Day Ahead API
The Day Ahead API from MISO — 11 operation(s) for day ahead.
MISO Forecast API
The Forecast API from MISO — 6 operation(s) for forecast.
MISO Fuel Mix API
The FuelMix API from MISO — 3 operation(s) for fuelmix.
MISO Generation Outages API
The GenerationOutages API from MISO — 1 operation(s) for generationoutages.
MISO Historical API
The Historical API from MISO — 1 operation(s) for historical.
MISO IMM API
The IMM API from MISO — 1 operation(s) for imm.
MISO Interchange API
The Interchange API from MISO — 9 operation(s) for interchange.
MISO Market Pricing API
The MarketPricing API from MISO — 6 operation(s) for marketpricing.
MISO Model API
The Model API from MISO — 1 operation(s) for model.
MISO Notifications API
The Notifications API from MISO — 6 operation(s) for notifications.
MISO Notifications Format API
The Notifications Format API from MISO — 7 operation(s) for notifications format.
MISO Offer API
The Offer API from MISO — 7 operation(s) for offer.
MISO Real Time API
The Real Time API from MISO — 17 operation(s) for real time.
MISO Real Time RSG Commitments API
The RealTimeRSGCommitments API from MISO — 1 operation(s) for realtimersgcommitments.
MISO Real Time Total Load API
The RealTimeTotalLoad API from MISO — 1 operation(s) for realtimetotalload.
MISO Regional Directional Transfer API
The RegionalDirectionalTransfer API from MISO — 1 operation(s) for regionaldirectionaltransfer.
MISO Reports API
The Reports API from MISO — 14 operation(s) for reports.
MISO Reserves API
The Reserves API from MISO — 6 operation(s) for reserves.
MISO Snapshot API
The Snapshot API from MISO — 1 operation(s) for snapshot.
MISO Transactions API
The Transactions API from MISO — 5 operation(s) for transactions.
MISO Weather API
The Weather API from MISO — 1 operation(s) for weather.
MISO Wind Solar API
The WindSolar API from MISO — 7 operation(s) for windsolar.
Scroll within the panel for all 38 ·
Open Collections 33
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONMISO Public Ace API
OPEN COLLECTIONMUI - Public Specification Admin API
OPEN COLLECTIONPricing Aggregated Pnode API
OPEN COLLECTIONMUI - Public Specification Bidding API
OPEN COLLECTIONMISO Public Binding Constraints API
OPEN COLLECTIONMUI - Public Specification Contracts API
OPEN COLLECTIONMISO Public Coordinated Transaction Scheduling API
OPEN COLLECTIONMISO Public Csat Next Day Short Term Reserve Requirement API
OPEN COLLECTIONMISO Public Csat Supply Demand API
OPEN COLLECTIONMiso Day Ahead API
OPEN COLLECTIONMiso Forecast API
OPEN COLLECTIONMISO Public Fuel Mix API
OPEN COLLECTIONMISO Public Generation Outages API
OPEN COLLECTIONLoad, Generation, and Interchange Historical API
OPEN COLLECTIONMUI - Public Specification IMM API
OPEN COLLECTIONMISO Public Interchange API
OPEN COLLECTIONMISO Public Market Pricing API
OPEN COLLECTIONMUI - Public Specification Model API
OPEN COLLECTIONAPI Collection
OPEN COLLECTIONMUI - Public Specification Notifications API
OPEN COLLECTIONMUI - Public Specification Notifications Format API
OPEN COLLECTIONMUI - Public Specification Offer API
OPEN COLLECTIONMiso Real Time API
OPEN COLLECTIONMISO Public Real Time RSG Commitments API
OPEN COLLECTIONMISO Public Real Time Total Load API
OPEN COLLECTIONMISO Public Regional Directional Transfer API
OPEN COLLECTIONMUI - Public Specification Reports API
OPEN COLLECTIONMUI - Public Specification Reserves API
OPEN COLLECTIONMISO Public Snapshot API
OPEN COLLECTIONMUI - Public Specification Transactions API
OPEN COLLECTIONMISO Information Interface Weather API
OPEN COLLECTIONMISO Public Wind Solar API
OPEN COLLECTIONScroll within the panel for all 33 ·
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 things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Miso Plans
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Miso Rate Limits
RATE LIMITSExamples 63
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 63 ·
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 MISO — 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 5
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 5
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 4
Status, limits, changes, and where to get help
Commercial 4
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/miso · machine-readable index on apis.io
This is an independent, third-party profile of MISO, 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.