# Japan Renewable Energy FIT/FIP Certified Facilities (`jpopendata/japan-renewable-fit`) Actor

Certified renewable energy facilities (solar, wind, hydro, biomass, geothermal) from Japan's official METI/ANRE FIT/FIP disclosure (fit-portal.go.jp). English field schema, municipality-level locations, corporate operators only (individuals' data is redacted), source attribution embedded in every…

- **URL**: https://apify.com/jpopendata/japan-renewable-fit.md
- **Developed by:** [JP Open Data](https://apify.com/jpopendata) (community)
- **Categories:** Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Japan Renewable Energy FIT/FIP Certified Facilities

**Japan's officially certified renewable-energy plants — solar, wind, hydro, biomass, geothermal — as English-schema JSON, from METI's public FIT/FIP disclosure.**

This Actor delivers the 事業計画認定情報 (certified business plan) disclosure published monthly by METI / the Agency for Natural Resources and Energy on fit-portal.go.jp: facility ID, corporate operator, energy type, output in kW, municipality-level location, certification and operation-start dates, FIT period end, and solar decommissioning-reserve status. One prefecture per run, two upstream requests, everything parsed offline.

> **Unofficial tool.** Not affiliated with or endorsed by METI, the Agency for Natural Resources and Energy, or the Government of Japan. Records are edited/processed data from the fit-portal public disclosure (出典：再生可能エネルギー電子申請サイトの事業計画認定情報を編集・加工して作成); the site's terms (政府標準利用規約 2.0, declared CC BY 4.0-compatible) permit commercial reuse with attribution and a processed-data notice — both are embedded in every record.

***

### Who is this for?

- **Renewable-energy investors and asset managers** — screen Japan's certified capacity by region, technology, size, and operating status; identify operators and portfolios; track FIT period ends (repowering and secondary-market signals).
- **Market analysts & consultants** — capacity mapping, operator concentration, decommissioning-reserve compliance patterns in Japan's post-FIT transition.
- **Data & AI teams** — a structured alternative to 47 monthly Excel files behind changing download links.

### What you get, and what we deliberately leave out

The upstream disclosure file contains substantial personal data — roughly a third of low-voltage solar operators are private individuals, listed with personal names, home addresses, and phone numbers. **This Actor is built not to republish any of it:**

- **Individual operator names are withheld.** `operatorName` passes a positive corporate/institutional test (legal-form designators, public bodies, cooperatives). Any name not positively identifiable as a legal entity becomes `null` with `operatorNameWithheld: true`. We accept losing some real companies to this filter; we do not accept publishing a person's name. (Measured on a live prefecture file: 1,120 kept / 565 withheld.)
- **Locations are truncated to municipality level** (市区町村). The upstream parcel-level address of a rooftop plant is effectively a home address; unparseable addresses fail safe to `null`.
- **The operator's own address and phone columns are never read** — they are deny-listed by header name, and automated legal tests verify that none of their values appear anywhere in the output.

If you need parcel-level locations or individual operators, this is the wrong tool — and we'd encourage you to think carefully before building that dataset from any source.

### Sample output (dataset item)

```json
{
  "facilityId": "AXXXXXXXXX",
  "operatorName": "○○エナジー株式会社",
  "operatorNameWithheld": false,
  "energyType": "solar",
  "energyTypeJa": "太陽光",
  "outputKw": 1990.0,
  "prefecture": "鳥取県",
  "prefectureCode": "31",
  "prefectureRomaji": "tottori",
  "municipality": "鳥取市",
  "certificationDate": "2013-03-29",
  "operationStartReportedMonth": "2014-11",
  "isOperating": true,
  "fitPeriodEndMonth": "2034-10",
  "decommissionReserveMethod": "外部積立",
  "decommissionReserveStatus": "積立中",
  "asOfDate": "2026-07-31",
  "source": "再生可能エネルギー電子申請サイト（経済産業省）",
  "sourceUrl": "https://www.fit-portal.go.jp/",
  "license": "政府標準利用規約2.0 (CC BY 4.0 compatible) — 事業計画認定情報を編集・加工して作成",
  "retrievedAt": "2026-08-25T09:12:44Z"
}
```

### Input example

```json
{
  "prefecture": "chiba",
  "energyType": "solar",
  "minOutputKw": 50,
  "maxItems": 5000
}
```

One run covers **one prefecture** (the upstream publishes one file per prefecture). For nationwide coverage, run all 47 prefectures — e.g., on an Apify schedule; that's 94 polite upstream requests in total, deliberately not crammed into a single run.

### Pricing

Pay per result — see the pricing tab. A mid-size prefecture's solar fleet above 50 kW is typically a few thousand records.

### FAQ

**Where does the data come from?**
From the FIT/FIP certified-facility disclosure (事業計画認定情報) on fit-portal.go.jp, published by METI / the Agency for Natural Resources and Energy and refreshed monthly. The Actor resolves the current month's download link at run time and stamps `asOfDate` from the page's own reference date.

**Is this an official government service?**
No. **Unofficial**, independently built and maintained. Every record carries the required attribution and the processed-data notice.

**How complete is the coverage?**
The disclosure covers FIT/FIP-certified facilities and **excludes solar below 20 kW** (upstream policy). `isOperating` is `true` when an operation-start report month is published and `null` otherwise — legacy transition-certified plants may be operating without a report on file, and the Actor does not guess.

**Why are some operator names null?**
See above: those are (or could not be proven not to be) private individuals, and we don't republish personal data. `operatorNameWithheld: true` marks them, and each run's summary reports the withheld count, so the filtering is visible rather than silent.

**How fresh is the data?**
Monthly upstream refresh, sometimes with a publication lag of several months relative to the stated reference date — `asOfDate` always tells you what you actually got.

**What about server load?**
Two requests per run, ≥1.2 s apart, exponential backoff on 429/5xx, explicit User-Agent, no rate-limit evasion. On persistent blocking the run fails visibly rather than working around it.

### Search terms this Actor answers

Japan solar FIT data · Japan renewable energy database · FIT certified facilities Japan · Japan solar plant list · METI FIT disclosure English · Japan wind power data · renewable energy Japan dataset · Japan FIP facilities

### More Japan public-data Actors by the same developer

- **Japan Government Tenders & Awards** — tender notices and award results from the kkj.go.jp portal.
- **Japan Medical Facilities** — every registered hospital, clinic, dental clinic, and pharmacy (MHLW open data).
- **Japan Care Facilities** — long-term care providers across 35 service types (MHLW open data, CC BY).
- **Japan Government Subsidies & Grants** — open subsidy calls from the official jGrants API.
- **Japan Financial Licenses & Registrations** — FSA-licensed banks, securities firms, crypto exchanges and more.
- **Japan Construction & Real-Estate Licenses** — licensed contractors and brokers from MLIT's register.
- **Japan Trade Statistics** — monthly import/export flows by HS code and partner country, from Japan Customs.

***

*Data source: 再生可能エネルギー電子申請サイト（fit-portal.go.jp）事業計画認定情報 — edited and processed; attribution and processing notice embedded in every record per the site's terms.*

# Actor input Schema

## `prefecture` (type: `string`):

The upstream publishes one file per prefecture; one run covers one prefecture. Default is Tottori (the smallest file — a fast first run). Japanese names (e.g. `東京都`) are also accepted via the API.

## `energyType` (type: `string`):

Filter by energy category. `solar` covers 太陽光; `wind` covers onshore/offshore 風力; `hydro` covers 水力 (incl. replacements); `biomass` バイオマス; `geothermal` 地熱. Note: the upstream disclosure excludes solar under 20 kW.

## `minOutputKw` (type: `integer`):

Only facilities with 発電出力 (generation output) at or above this many kW are returned. 0 = no minimum. E.g. 1000 keeps utility-scale plants (>= 1 MW) only.

## `maxItems` (type: `integer`):

Maximum number of records to output. The whole prefecture file is downloaded either way (that is how the upstream publishes); this truncates the output client-side after filtering.

## `maxApiRequests` (type: `integer`):

Hard safety cap on upstream requests in one run. A run needs exactly 2 (portal page + one prefecture file); the headroom only covers polite retries after 429/5xx. Politeness (1 connection, >= 1.2 s spacing, exponential backoff) is enforced in code.

## `proxyConfiguration` (type: `object`):

Apify proxy settings. Default is NO proxy (direct connection). The actor backs off exponentially on 429/5xx and fails visibly on a persistent block — it never attempts rate-limit evasion.

## Actor input object example

```json
{
  "prefecture": "tottori",
  "energyType": "all",
  "minOutputKw": 0,
  "maxItems": 1000,
  "maxApiRequests": 6,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `records` (type: `string`):

Structured records with source attribution (source, sourceUrl, license, retrievedAt) on every item.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("jpopendata/japan-renewable-fit").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("jpopendata/japan-renewable-fit").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call jpopendata/japan-renewable-fit --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jpopendata/japan-renewable-fit"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/1x09KVg32Q2IDXHxA/builds/POoCRX1UnjnAibT9M/openapi.json