# @pipeworx/ferc-form1

FERC Form 1 annual financial reports of major US investor-owned electric, gas and combination utilities: income statement, comparative balance sheet and summary of utility plant, by respondent (utility) and report year, 1994 to date.

Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1867+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

## Tools

- `ferc1_find_utility(query, limit?)` — find a Form 1 respondent by name and get its FERC respondent id. `found:false` when nothing matches.
- `ferc1_income_statement(utility, year?, utility_type?)` — Schedule 114 line items for one utility-year, plus a headline block (total operating revenues, operating expenses, net utility operating income, net income). Answers "PacifiCorp total operating revenues 2023".
- `ferc1_income_history(utility, income_type?, utility_type?)` — one income-statement line across every year on file, for trends.
- `ferc1_balance_sheet(utility, year?)` — Schedule 110 assets and liabilities/equity with starting and ending balances.
- `ferc1_utility_plant(utility, year?, utility_type?)` — Schedule 200 plant in service, construction work in progress and accumulated depreciation by segment.

`utility` takes a name or the numeric FERC respondent id. An unknown respondent returns `found:false`; an ambiguous name returns `ambiguous:true` with candidates. Amounts are US dollars as filed. Rows marked `is_correction` are reconciliation adjustments added by the data processor so the columns sum.

This is not `ferc-elibrary` (FERC's filing and docket search) or `ferc-eqr` (wholesale power transactions), and it is not `sec-xbrl`: Form 1 includes non-listed and subsidiary respondents that SEC company facts do not break out. Form 1 figures follow FERC's Uniform System of Accounts, so a utility's total can differ slightly from its GAAP figure in an SEC filing.

## Auth

Keyless.

## Data sources

- Catalyst Cooperative, Public Utility Data Liberation (PUDL) project, processed FERC Form 1 tables — derived from the filings utilities submit to the US Federal Energy Regulatory Commission. Published under CC-BY-4.0 (PUDL README: "The PUDL data and documentation are published under the Creative Commons Attribution License v4.0"); the underlying FERC filings are US federal public data. Every response carries the attribution.

The PUDL tables are large bulk files (hundreds of thousands of rows) with no query API, so a refresh script (`scripts/refresh-form1.mjs`, run weekly by a scheduled job) groups them by respondent and writes one small object per respondent plus a respondent index to the shared R2 store (`ferc-form1/`). A call reads the index and one respondent's object. `data_as_of` is the publication date of the PUDL release the data comes from; `copy_refreshed_at` is when the copy was last rebuilt. A missing index or respondent object is an error, never `found:false`: only the index decides that a respondent does not exist.

## Notes

- Respondent ids are FERC's `respondent_id`; PUDL's own `utility_id_pudl` is returned alongside for joining to other PUDL data. FERC's test respondents are excluded.
- Several respondents share a trade name (for example "Duke Energy"); use `ferc1_find_utility` and pass the numeric id.
- Refresh: `node mcps/ferc-form1/scripts/refresh-form1.mjs` (R2 write needs `CLOUDFLARE_API_TOKEN` + `CLOUDFLARE_ACCOUNT_ID` or an operator wrangler login); `--out <dir>` writes the objects to a directory instead, `--dry-run` writes nothing.

## Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

```json
{
  "mcpServers": {
    "ferc-form1": {
      "url": "https://gateway.pipeworx.io/ferc-form1/mcp"
    }
  }
}
```

### What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/ferc-form1/mcp` returns the tools in the table
above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
`discover_tools`, `search_within`, `remember`/`recall` and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's `initialize` response states its exact scope, and
is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
`ask_pipeworx`, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed
directly, instead of just this one's:

```json
{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}
```

Both URLs reach the same gateway and the same 1867+ data sources. The
only difference is which pack's tools are listed **directly**; `ask_pipeworx`
reaches all of them from either one.

## No MCP client? Call it over HTTP

```bash
curl -X POST https://gateway.pipeworx.io/v1/tools/ferc1_find_utility \
  -H 'Content-Type: application/json' \
  -d '{"query":"PacifiCorp"}'
```

No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/ferc1_find_utility`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.

## Run it from npm

`@pipeworx/mcp-ferc-form1` is a local stdio bridge to the Pipeworx gateway: your MCP client
starts it with `npx`, and it forwards every call to the same
`https://gateway.pipeworx.io/ferc-form1/mcp` endpoint shown above. It needs network access;
there is no offline mode.

```json
{
  "mcpServers": {
    "ferc-form1": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-ferc-form1"]
    }
  }
}
```

Without a key it calls anonymously, capped at 50 calls a day. A free account
raises that to 200 a day: get a key at https://pipeworx.io/signup and add
`"env": { "PIPEWORX_API_KEY": "<your key>" }` to the server entry.
The key is sent as a Bearer token, the same way a hosted connection sends it,
so calls are metered and billed exactly as they are there.

It lists **only** this pack's tools by default. Set `PIPEWORX_META_TOOLS=1` to
also list `ask_pipeworx` and the other gateway-wide tools.

Behind an HTTPS proxy: Node's built-in `fetch` does not read `HTTPS_PROXY` by
default. Newer Node releases honour it when `NODE_USE_ENV_PROXY=1` is set; check
your Node version's documentation.

## Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English —
this works on the pack endpoint above as well as on the full gateway:

```
ask_pipeworx({ question: "your question about Ferc Form1 data" })
```

The gateway picks the right tool and fills the arguments automatically.

## More

- [Docs and guides](https://pipeworx.io/docs)
- [pipeworx.io](https://pipeworx.io)

## License

MIT