MCP Tool
PPA counterparties
Who buys a seller's power, or who sells to a buyer, from FERC EQR filings.
- MCP
- Read-only
- Updated
Declaration
ppa_counterparties(
seller?: string,
buyer?: string,
market?: string,
since_year?: integer,
limit?: integer
)Parameters
sellerstringOptional- Seller name substring (at least 3 characters), e.g. 'Little Bear Solar' or 'Avangrid'. Give either seller or buyer, not both.
buyerstringOptional- Buyer (offtaker) name substring (at least 3 characters), e.g. 'Amazon' or 'Marin Clean Energy'.
marketstringOptional- Optional ISO, region or EQR balancing-authority code(s), comma-separated (see
ppa_price_benchmarks). Default: every market you can access. since_yearintegerOptional- Only relationships active in or after this year (contracts ending on/after Jan 1, volumes reported from that year).
limitintegerOptional- Counterparty rows to return (max 50).Default:
20
Return Value
Returns {summary, role, query, market, matched_names, total_counterparties, counterparties, contracts_total, contracts, iso_market_sales, linked_queue_projects, data_vintage, source, caveats}.
Discussion
Who buys a seller's power, or who sells to a buyer, from FERC EQR filings. Pass exactly one of seller (an SPV such as 'Little Bear Solar' or a company name) or buyer (e.g. 'Amazon', 'Marin Clean Energy'); matching is a case-insensitive substring, and the response lists the name variants that matched.
Each counterparty row merges three EQR views: contracts on file (count, long-term count, contracted MW, first start and last end date), buyer-seller volume rollups (MWh, $/MWh, period) and quarterly settlement data (MWh, $/MWh, quarters). A list of individual contracts follows (distribution/transmission tariff service agreements excluded). For a seller, sales into ISO/RTO markets are summarised separately because they are not PPAs, and queue projects Load Factor has linked to the seller are listed in linked_queue_projects, each with an attribution label (unverified leads).
Returns {summary, role, query, market, matched_names, total_counterparties, counterparties, contracts_total, contracts, iso_market_sales, linked_queue_projects, data_vintage, source, caveats}. Names are matched, not reviewed: check matched_names and each row's name_variants. volumes_pairs and volumes_quarterly overlap and are not additive; a contract's linked_project is an inferred, unverified link. $/MWh figures are as reported in FERC EQR filings, not Load Factor estimates.
Use ppa_top_buyers to rank offtakers across a market and ppa_expiring_contracts for contracts ending soon.
Example
Ask your assistant:
Who buys power from NextEra, according to FERC EQR filings?
It would call the tool with a request like this one (your client builds and sends it for you):
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "ppa_counterparties",
"arguments": {
"seller": "NextEra"
}
}
}Availability
Listed to accounts with the Developer Tracker module. Results follow your Load Factor permissions (ISOs, detail level, evidence depth and rows per call). See Access & permissions.