# 🇯🇵 Japan MoF FX Intervention · 財務省 為替介入 (`nexgendata/japan-mof-fx-intervention-tracker`) Actor Live feed of Japan MoF yen FX intervention disclosures (FEIO) — every USD/JPY, EUR/JPY, GBP/JPY operation back to 1991, including the 2022 + 2024 yen-defense episodes. JPY normalized + USD estimates + bilingual descriptions. Built for FX desks, macro PMs, options-vol quants. - **URL**: https://apify.com/nexgendata/japan-mof-fx-intervention-tracker.md - **Developed by:** [NexGenData](https://apify.com/nexgendata) (community) - **Categories:** Business - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $150.00 / 1,000 fx intervention 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/platform/actors/running/actors-in-store#pay-per-event ## What's an Apify Actor? Actors are a software tools running on the Apify platform, for all kinds of web data extraction and automation use cases. 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. In JavaScript/TypeScript projects, use official [JavaScript/TypeScript client](https://docs.apify.com/api/client/js.md): ```bash npm install apify-client ``` In Python projects, use official [Python client library](https://docs.apify.com/api/client/python.md): ```bash pip install apify-client ``` In shell scripts, use [Apify CLI](https://docs.apify.com/cli/docs.md): ````bash # MacOS / Linux curl -fsSL https://apify.com/install-cli.sh | bash # Windows irm https://apify.com/install-cli.ps1 | iex ```bash In AI frameworks, you might use the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp.md). If your project is in a different language, use 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 MoF FX Intervention Tracker — Yen Intervention Disclosures > **Live structured feed of every Japanese Ministry of Finance yen intervention disclosure** — every USD/JPY, EUR/JPY, GBP/JPY operation back to April 1991, including the 2022 and 2024 yen-defense episodes. The only programmatic source for the MoF FEIO (Foreign Exchange Intervention Operations) record on Apify Store. When the yen breaks ¥160/USD and the MoF presses the button, the world's FX desks need to know within seconds — but the official disclosure is a Shift-JIS CSV buried three navigation clicks deep on `mof.go.jp`, half in Japanese, half in English, with imperial-calendar dates and amounts in `億円` (100-million-yen units). This actor delivers that data clean — Gregorian dates, JPY in millions, USD-equivalent estimated at the intervention-year reference rate, and a normalized `intervention_type` (`sell_USD` = yen defense, `buy_USD` = yen weakening). --- ### ⚡ What you get Every record is one MoF FX intervention disclosure (or quarterly summary when `currency_pair_filter=all`) with **16 normalized fields**: | Field | Type | Example | Notes | |---|---|---|---| | `report_date` | ISO date | `2024-04-29` | Intervention day. Null on quarterly summary rows. | | `fiscal_year_jp` | string | `令和6年` | Japanese imperial calendar fiscal year (Reiwa/Heisei). | | `currency_pair` | string | `USD-JPY` | Normalized pair. `QUARTERLY-SUMMARY` for quarter-end roll-ups. | | `base_currency` | string | `USD` | Foreign side of the pair. | | `quote_currency` | string | `JPY` | Always JPY for MoF interventions. | | `amount_oku_yen_raw` | number | `59185.0` | Original CSV unit: 100-million yen (`億円`). | | `amount_JPY_millions` | number | `5918500.0` | Converted to millions of yen. | | `amount_USD_equivalent_at_intervention_rate` | number | `39087.6` | Millions of USD at the year's reference USDJPY. | | `estimation_rate_USDJPY` | number | `151.41` | The reference USDJPY used for the estimate. | | `intervention_type` | string | `sell_USD` | `sell_USD` = MoF sold USD/bought JPY (yen defense); `buy_USD` = opposite. | | `description_en` | string | `the US dollar (sold) the Japanese yen (bought)` | Original English description from MoF. | | `description_jp` | string | `米ドル売り・日本円買い` | Original Japanese description. | | `is_quarterly_summary` | boolean | `false` | True for quarter-end aggregate rows. | | `source_url` | string | `https://www.mof.go.jp/english/policy/international_policy/reference/feio/index.html` | MoF English landing page. | | `source_url_jp` | string | `https://www.mof.go.jp/policy/international_policy/reference/feio/index.html` | MoF Japanese landing page. | | `fetched_at` | ISO datetime | `2026-05-31T20:30:00+00:00` | When this actor pulled the CSV. | The MoF historical CSV at `foreign_exchange_intervention_operations.csv` covers every recorded intervention since April 1991 (Heisei 3) — that's three+ decades of yen-defense history. Use `intervention_only=true` (default) to skip zero-month rows; switch to `false` to pull the full series including the long quiet stretches when MoF didn't act. --- ### 🎯 Use cases **FX desk — real-time intervention monitoring.** A JPY trader at a global macro fund watches the spot move ¥160.50 → ¥154.20 in 40 minutes. Was that MoF? Pull `report_date` matches against the last 72 hours; the MoF posts the daily-detail disclosure on the last business day of each month — so the existence of the action is confirmable in real-time via this feed plus the BoJ current-account anomaly. The amount confirms within four weeks. **Macro PM — yen-policy regime detection.** Aggregate `amount_JPY_millions` by fiscal year. The 2022 cycle hit ¥9.19 trillion across three operations (¥2.84T Sep 22, ¥5.62T Oct 21, plus October mid-month follow-up). The 2024 cycle hit ¥15.55 trillion across April + July. When a new cycle starts, the size + cadence of the first operation tells you whether MoF is in "warning" mode (¥3-5T per shot) or "all-in" mode (¥7T+). **Hedge fund options desk — vol-curve build.** Mark a structural USDJPY vol spike against historical intervention dates. The 2-week implied rises 200-400bp in the 5 trading days before each MoF action (the leak risk premium) and collapses 100-200bp in the 3 days after. Backtest with this feed + your vol-history database. **Sovereign-debt analyst — yen reserve drawdown.** Each MoF yen-buying intervention draws down the FX reserves account at the BoJ. Cross-join this feed against the BoJ Foreign Reserve series — the delta tells you the marked-to-market vs. effective rate of the intervention and the remaining ammunition. **Quant — economic-surprise factor extension.** Add intervention amount as an event-window factor to your USDJPY momentum model. The 5-day post-intervention return distribution is materially different from random news days (skew: positive for yen, kurtosis: elevated). **Compliance — central bank action tracking.** A US bank's FX compliance team logs every official intervention worldwide. The MoF series is one of the four mandatory G10-currency feeds (SNB, RBA, BoJ/MoF, NB are the others). --- ### 📊 Sample Output ![MoF FX Intervention Tracker dashboard](https://api.apify.com/v2/key-value-stores/8gLgXMBveEI1tTz1z/records/japan-mof-fx-intervention-tracker-output.png) *Above: live sample output from a `currency_pair_filter: "USD-JPY", intervention_only: true, max_records: 5` run — five most recent yen-defense interventions from the 2022 + 2024 cycles, with normalized JPY amounts, USD-equivalent estimates, and the original bilingual descriptions.* --- ### 🚀 How to use #### Default smoke test (last year's interventions) ```json { "currency_pair_filter": "all", "intervention_only": true, "max_records": 100 } ```` #### Yen-defense focus (2022 → today, USD-JPY only) ```json { "currency_pair_filter": "USD-JPY", "date_from": "2022-01-01", "date_to": "2026-12-31", "intervention_only": true, "max_records": 50 } ``` #### Full historical series (1991 → today, all pairs, including quiet months) ```json { "currency_pair_filter": "all", "date_from": "1991-04-01", "date_to": "2026-12-31", "intervention_only": false, "max_records": 500 } ``` #### Python (apify-client) ```python from apify_client import ApifyClient client = ApifyClient("YOUR_APIFY_TOKEN") run = client.actor("nexgendata/japan-mof-fx-intervention-tracker").call( run_input={ "currency_pair_filter": "USD-JPY", "date_from": "2022-01-01", "date_to": "2026-12-31", "intervention_only": True, "max_records": 20, } ) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item["report_date"], item["intervention_type"], item["amount_JPY_millions"], "millions JPY") ``` #### cURL ```bash curl -X POST "https://api.apify.com/v2/acts/nexgendata~japan-mof-fx-intervention-tracker/runs?token=YOUR_APIFY_TOKEN" \ -H "Content-Type: application/json" \ -d '{"currency_pair_filter":"USD-JPY","intervention_only":true,"max_records":10}' ``` *** ### 🇯🇵 日本語の説明 このアクターは、財務省が公表する「外国為替平衡操作の実施状況」（FEIO）データを構造化されたJSON形式で配信します。データソースは財務省の公式CSV（Shift-JIS形式）で、1991年4月（平成3年4月）以降のすべての為替介入記録を網羅しています。 **主な用途:** - 為替トレーダー — 米ドル/円介入のリアルタイム監視 - マクロPM — 円政策レジームの検出（2022年・2024年介入サイクルの分析） - ヘッジファンドオプションデスク — ボラティリティ曲線への介入イベントの織り込み - 国債アナリスト — 外貨準備の取り崩し追跡 - クオンツ — エコノミックサプライズファクターへの介入イベント追加 **入力パラメーター:** - `currency_pair_filter`: 通貨ペアフィルター（USD-JPY / EUR-JPY / GBP-JPY / all）。デフォルト `all` - `date_from` / `date_to`: 期間指定（ISO 8601 形式 `YYYY-MM-DD`） - `intervention_only`: ゼロ介入月を除外するか（デフォルト `true`） - `max_records`: 最大レコード数（1〜500、デフォルト100） **出力スキーマ（介入レコードあたり16フィールド）:** 報告日（`report_date`）、和暦の年度（`fiscal_year_jp`）、通貨ペア（`currency_pair`）、ベース通貨、決済通貨、原データの億円単位金額、百万円換算、当該年の参照USDJPYレートでのドル建て概算、介入タイプ（売買方向）、英文・和文の取引説明、四半期合計フラグ、ソースURL（英語版・日本語版）、取得日時。 **法的根拠:** 外国為替及び外国貿易法第7条に基づき、財務省は為替介入の実施額を月次・四半期で公表しています。本アクターはこの公開データを取得・整理するもので、追加の権利申請は不要です。 **接続ポリシー:** ユーザーエージェントはMoFオープンデータ慣行に則り `Mozilla/5.0 (compatible; NexGenDataBot/1.0; +https://nexgendata.com/bot; contact: hello@thenextgennexus.com)` を使用しています。連絡先: hello@thenextgennexus.com *** ### ⚖️ Legal & data sources - **Source:** Japan Ministry of Finance, Foreign Exchange Intervention Operations (FEIO). - English landing: - Japanese landing: - Historical CSV: `foreign_exchange_intervention_operations.csv` (Shift-JIS encoded, updated monthly). - **Disclosure mandate:** Foreign Exchange and Foreign Trade Act (外国為替及び外国貿易法) §7 — transparency obligation for FX intervention. - **Cadence:** Daily-detail amounts are published on the last business day of each month, covering the prior 28-31-day window. Quarterly summary rows are published with the final monthly release of each quarter. - **License:** MoF open-data policy — public records, free to redistribute with attribution. - **User-Agent policy:** `Mozilla/5.0 (compatible; NexGenDataBot/1.0; +https://nexgendata.com/bot; contact: hello@thenextgennexus.com)` per Japanese government open-data convention (MoF/FSA/NTA/INPIT explicitly invite identified crawlers). - **Rate limit:** This actor fetches the historical CSV at most once per run (~43 KB). No rate-limit pressure on MoF infrastructure. *** ### ❓ FAQ **Q: Why is the USD-equivalent an "estimate"?** A: MoF discloses amounts in JPY only, not in the foreign currency. Daily intra-month effective rates aren't published; the only fully reliable conversion is the daily TTM fix at the BoJ — which we don't yet pull into this actor. We use the annual average USDJPY reference rate as a per-year estimate (e.g. 2022: 131.50, 2024: 151.41). For trading-precision USD amounts, recompute against your own daily fix. **Q: Are quarterly summary rows duplicates of the daily rows?** A: Quarterly summary rows are roll-ups of the daily rows. By default (`intervention_only=true` with a specific currency\_pair\_filter), quarterly rows are skipped. Set `currency_pair_filter=all` to include them — useful for cross-checking that the daily rows sum to the official quarter total. **Q: Why do some rows have a null `report_date`?** A: Quarterly summary rows don't have a single intervention date — they aggregate the full quarter. `report_date` is null for those; `fiscal_year_jp` still resolves the period. **Q: How does `intervention_type` work?** A: MoF describes interventions as e.g. *"the US dollar (sold), the Japanese yen (bought)"*. We classify by what was done to the **foreign currency** — so `sell_USD` means MoF sold USD and bought JPY (yen defense, the classic 2022 + 2024 mode). `buy_USD` would mean yen-weakening intervention, which Japan hasn't run since the early 2000s. **Q: What's the difference between this and the BoJ Foreign Reserve series?** A: This feed shows the gross transaction. The BoJ reserve series shows the net portfolio impact (which includes mark-to-market on existing USD holdings, JGB-USD swap roll, and the intervention's cash leg). Both are needed for a full picture of yen-defense ammunition. **Q: Does the actor pull the daily-detail breakdown (which session, which counterparty)?** A: The monthly disclosure only publishes the aggregate amount per intervention day and the currency pair. Counterparty and session-time breakdowns are not in the public MoF series — those would require BoJ supplementary statistics and a paid Bloomberg / Refinitiv feed. *** ### 🔗 Related Actors The macro-FX cluster on NexGenData (currently public on Apify Store): - **[currency-exchange-rates](https://apify.com/nexgendata/currency-exchange-rates)** — 150+ FX pairs (USD/JPY, JPY/KRW, EUR/JPY) for USD-equivalent recomputation and cross-rate analysis. - **[treasury-yields-bonds](https://apify.com/nexgendata/us-treasury-yields-bonds)** — US Treasury yield curve, the other side of the USDJPY carry trade. *(verify public before linking)* - **[tse-japan-stock-screener](https://apify.com/nexgendata/tse-japan-stock-screener)** — Tokyo Stock Exchange equity screener for the equity-side response to yen-defense moves. - **[japan-edinet-insider-filings](https://apify.com/nexgendata/japan-edinet-insider-filings)** — Japanese listed-company filings (EDINET) for the disclosure-cycle context around MoF actions. - **[sec-form-13f-tracker-pro](https://apify.com/nexgendata/sec-form-13f-tracker-pro)** — institutional positioning data for JPY-exposed equities + the yen-carry-trade investor pool. For Japanese fixed-income context, see the BoJ JGB-auction + macro-rates sibling actor (Wave 12 build, may be in private review). *** ### 🏷️ About NexGenData NexGenData builds programmatic feeds for niche disclosure data that institutional research teams pay $10K+/yr for via terminal subscriptions. Our Japan/Korea cluster covers the disclosure-velocity sources that don't have English-language equivalents on Apify Store: TDnet timely disclosures, EDINET filings, MoF FX intervention, BoJ macro stats, JPX short-balance, DART OpenDART, KIPO patents, and more. Contact: **hello@thenextgennexus.com** · [nexgendata.com](https://nexgendata.com/) # Actor input Schema ## `currency_pair_filter` (type: `string`): Restrict to a specific currency pair, or 'all' for every pair (and to include quarterly summary rows). Default 'all'. ## `date_from` (type: `string`): Inclusive lower bound for the intervention report\_date (ISO YYYY-MM-DD). Defaults to one year ago. ## `date_to` (type: `string`): Inclusive upper bound for the intervention report\_date (ISO YYYY-MM-DD). Defaults to today. ## `intervention_only` (type: `boolean`): When true, exclude zero-intervention months (¥0 reports). Set false to include the full historical series including zero months. Default true. ## `max_records` (type: `integer`): Maximum number of intervention records to emit (1-500). Default 100. ## Actor input object example ```json { "currency_pair_filter": "all", "date_from": "2022-01-01", "date_to": "2026-05-31", "intervention_only": true, "max_records": 100 } ``` # 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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "currency_pair_filter": "all", "date_from": "2022-01-01", "date_to": "2026-05-31", "max_records": 100 }; // Run the Actor and wait for it to finish const run = await client.actor("nexgendata/japan-mof-fx-intervention-tracker").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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "currency_pair_filter": "all", "date_from": "2022-01-01", "date_to": "2026-05-31", "max_records": 100, } # Run the Actor and wait for it to finish run = client.actor("nexgendata/japan-mof-fx-intervention-tracker").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"]) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "currency_pair_filter": "all", "date_from": "2022-01-01", "date_to": "2026-05-31", "max_records": 100 }' | apify call nexgendata/japan-mof-fx-intervention-tracker --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=nexgendata/japan-mof-fx-intervention-tracker", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "🇯🇵 Japan MoF FX Intervention · 財務省 為替介入", "description": "Live feed of Japan MoF yen FX intervention disclosures (FEIO) — every USD/JPY, EUR/JPY, GBP/JPY operation back to 1991, including the 2022 + 2024 yen-defense episodes. JPY normalized + USD estimates + bilingual descriptions. Built for FX desks, macro PMs, options-vol quants.", "version": "0.0", "x-build-id": "nAak6wbVazV0EjqyH" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/nexgendata~japan-mof-fx-intervention-tracker/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-nexgendata-japan-mof-fx-intervention-tracker", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for its completion, and returns Actor's dataset items in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } }, "/acts/nexgendata~japan-mof-fx-intervention-tracker/runs": { "post": { "operationId": "runs-sync-nexgendata-japan-mof-fx-intervention-tracker", "x-openai-isConsequential": false, "summary": "Executes an Actor and returns information about the initiated run in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/runsResponseSchema" } } } } } } }, "/acts/nexgendata~japan-mof-fx-intervention-tracker/run-sync": { "post": { "operationId": "run-sync-nexgendata-japan-mof-fx-intervention-tracker", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for completion, and returns the OUTPUT from Key-value store in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } } }, "components": { "schemas": { "inputSchema": { "type": "object", "properties": { "currency_pair_filter": { "title": "Currency pair filter", "enum": [ "USD-JPY", "EUR-JPY", "GBP-JPY", "all" ], "type": "string", "description": "Restrict to a specific currency pair, or 'all' for every pair (and to include quarterly summary rows). Default 'all'.", "default": "all" }, "date_from": { "title": "Date from (ISO 8601)", "type": "string", "description": "Inclusive lower bound for the intervention report_date (ISO YYYY-MM-DD). Defaults to one year ago.", "default": "2025-05-31" }, "date_to": { "title": "Date to (ISO 8601)", "type": "string", "description": "Inclusive upper bound for the intervention report_date (ISO YYYY-MM-DD). Defaults to today.", "default": "2026-05-31" }, "intervention_only": { "title": "Intervention months only", "type": "boolean", "description": "When true, exclude zero-intervention months (¥0 reports). Set false to include the full historical series including zero months. Default true.", "default": true }, "max_records": { "title": "Maximum records", "minimum": 1, "maximum": 500, "type": "integer", "description": "Maximum number of intervention records to emit (1-500). Default 100.", "default": 100 } } }, "runsResponseSchema": { "type": "object", "properties": { "data": { "type": "object", "properties": { "id": { "type": "string" }, "actId": { "type": "string" }, "userId": { "type": "string" }, "startedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "finishedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "status": { "type": "string", "example": "READY" }, "meta": { "type": "object", "properties": { "origin": { "type": "string", "example": "API" }, "userAgent": { "type": "string" } } }, "stats": { "type": "object", "properties": { "inputBodyLen": { "type": "integer", "example": 2000 }, "rebootCount": { "type": "integer", "example": 0 }, "restartCount": { "type": "integer", "example": 0 }, "resurrectCount": { "type": "integer", "example": 0 }, "computeUnits": { "type": "integer", "example": 0 } } }, "options": { "type": "object", "properties": { "build": { "type": "string", "example": "latest" }, "timeoutSecs": { "type": "integer", "example": 300 }, "memoryMbytes": { "type": "integer", "example": 1024 }, "diskMbytes": { "type": "integer", "example": 2048 } } }, "buildId": { "type": "string" }, "defaultKeyValueStoreId": { "type": "string" }, "defaultDatasetId": { "type": "string" }, "defaultRequestQueueId": { "type": "string" }, "buildNumber": { "type": "string", "example": "1.0.0" }, "containerUrl": { "type": "string" }, "usage": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "integer", "example": 1 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } }, "usageTotalUsd": { "type": "number", "example": 0.00005 }, "usageUsd": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "number", "example": 0.00005 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } } } } } } } } } ```