# Japan JEPX Electricity Spot Price MCP (`fruitful_quintessence/japan-jepx-mcp`) Actor

MCP server: Japan wholesale electricity spot prices (JEPX). System + 9 areas, 30-min granularity (48 periods/day), JPY/kWh.

- **URL**: https://apify.com/fruitful\_quintessence/japan-jepx-mcp.md
- **Developed by:** [atushi ino](https://apify.com/fruitful_quintessence) (community)
- **Categories:** E-commerce
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Japan JEPX Electricity Spot Price MCP

MCP server exposing **Japanese wholesale electricity spot prices** from JEPX
(Japan Electric Power Exchange) — the **system (nationwide) price plus 9 regional
area prices** at **30-minute granularity (48 periods/day)**, in **JPY/kWh**.

Data source: JEPX spot settlement prices (Government Standard Terms of Use),
with OCCTO area-price forecast for regional deltas. A bundled seed cache
(`data/jepx_spot.json`, ~400 days × 48 periods = 19,200 records) guarantees
offline/fallback answers; a live fetch to JEPX.org is attempted and gracefully
falls back to the seed when the site is IP-restricted.

### Output sample

```json
{
  "date": "2026-09-17",
  "area": "tokyo",
  "area_label": "東京 (Tokyo)",
  "price": 15.24,
  "unit": "JPY/kWh",
  "period": 48
}
```

### Tools (MCP, 5)

| Tool | Description |
|------|-------------|
| `get_latest_spot_price` | Latest spot price for an area (default tokyo) |
| `get_spot_price_by_day` | Full 48-period day curve + min/max/avg |
| `get_spot_price_history` | Daily-average history (min/max/avg over window) |
| `get_cheapest_spot` | Cheapest 30-min slots, or cheapest-area ranking |
| `list_spot_areas` | Area catalogue + unit + latest date |

### REST endpoints (OpenAPI gateway)

| Endpoint | Description |
|----------|-------------|
| `GET /rest/latest?area=tokyo` | Latest spot price (numeric) |
| `GET /rest/date?area=tokyo&date=YYYY-MM-DD` | Full-day curve |
| `GET /rest/history?area=tokyo&days=14` | Daily-average history |
| `GET /rest/cheapest?area=tokyo&limit=5` | Cheapest slots / areas |
| `GET /rest/areas` | Area list + unit + periods/day |
| `GET /openapi.json` | OpenAPI document |

**Areas** (order of regional prices): `system` (nationwide), `hokkaido`,
`tohoku`, `tokyo`, `chubu`, `hokuriku`, `kinki` (aka kansai), `chugoku`,
`shikoku`, `kyushu`. Romaji and kanji (e.g. `tokyo` / `東京`) both accepted.

### Use cases

- EV charging scheduling / home-battery arbitrage
- Manufacturing load-shifting to cheap hours
- Electricity market monitoring and forecasting analysis
- Energy cost benchmarking for Japan

### Local run

```bash
uv run --directory . src/stdio_main.py   # stdio MCP (Claude Desktop / Cursor)
## or REST-only smoke against the seed:
JEPX_DATA_DIR=/tmp/jepx-smoke python3 smoke_rest.py
```

### Deployment

Apify Actor `japan-jepx-mcp` (Standby mode, `webServerMcpPath=/mcp`,
`Dockerfile CMD ["python", "-m", "src.main"]`):
`https://fruitful-quintessence--japan-jepx-mcp.apify.actor/mcp`

### Data & attribution

- **Source**: JEPX (Japan Electric Power Exchange) spot market settlement prices — [jepx.org](https://www.jepx.org) · OCCTO demand/supply area price forecast — [occto.or.jp](https://www.occto.or.jp)
- **Data licensing**: Government Standard Terms of Use (出典明示で商用利用可)
- **Unit**: JPY/kWh (円/kWh); 48 × 30-min periods per trading day

# Actor input Schema

## Actor input object example

```json
{}
```

# Actor output Schema

## `mcp_endpoint` (type: `string`):

Streamable-HTTP MCP endpoint of this run's Standby container (append /mcp, Bearer Apify token required).

## `run_output` (type: `string`):

Console view of this run (MCP servers return results inline over the protocol, not via dataset).

# 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("fruitful_quintessence/japan-jepx-mcp").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("fruitful_quintessence/japan-jepx-mcp").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 fruitful_quintessence/japan-jepx-mcp --silent --output-dataset

```

## MCP server setup

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

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/BxstMzzxh8jq6UtfS/builds/4DADL13Tg72vok6vM/openapi.json