# FERC seller summary (`get_ferc_seller_summary`)

A read-only tool of the Load Factor MCP server (https://mcp.loadfactorenergy.com/mcp), in the PPAs & offtake group.

One FERC wholesale seller, summarized: the company's total contracted MW and energy/capacity contract count, its buyers by MWh, quarters active, and the data year; with the PPA module's unit-error and merchant-sale guards applied. `seller` matches the stored FERC filer name (case-insensitive); a near miss returns a short did-you-mean list, never another seller's data. Computed live from FERC Electric Quarterly Report filings.

Returns {summary, matched, seller, contracts, long_term_contracts, contracted_mw, products, buyers, total_mwh, quarters_active, data_year, scope, caveats, source}. `buyers` is the top 25 by MWh, each with `avg_price_usd_per_mwh` from the filed settlements (not a Load Factor estimate); `total_mwh` sums those 25 buyers only; `scope` names the markets covered. With no match, `matched` is false and `did_you_mean` lists close filer names, if any.

## Parameters

| Parameter | Type | Required | Description | Allowed values | Default |
|---|---|---|---|---|---|
| `seller` | string | yes | Seller name as filed in FERC EQR, e.g. 'Avangrid Renewables'. Exact stored-name match; near misses return did-you-mean. |  |  |

## Example

Ask your assistant: "What did Avangrid Renewables sell in FERC wholesale markets, and to whom?"

It would call the tool with a request like this one (your client builds and sends it for you):

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_ferc_seller_summary",
    "arguments": {
      "seller": "Avangrid Renewables"
    }
  }
}
```

## 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](https://loadfactorenergy.com/developers/mcp/access-and-permissions).
