# Home Assistant MCP Server (`parseforge/home-assistant-mcp-server`) Actor Control your Home Assistant smart home devices through AI agents using Model Context Protocol (MCP). Get states, call services, list entities, and manage lights, switches, sensors, climate controls, and more. Perfect for AI-powered home automation and voice assistants. - **URL**: https://apify.com/parseforge/home-assistant-mcp-server.md - **Developed by:** [ParseForge](https://apify.com/parseforge) (community) - **Categories:** Agents, MCP servers, Automation - **Stats:** 3 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: 5.00 out of 5 stars ## Pricing Pay per event 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 ![ParseForge Banner](https://github.com/ParseForge/apify-assets/blob/ad35ccc13ddd068b9d6cba33f323962e39aed5b2/banner.jpg?raw=true) ## ๐Ÿ  Home Assistant MCP Server > ๐Ÿš€ **Control your smart home through AI assistants in seconds.** Manage lights, switches, sensors, climate, and media players. No coding, no custom server setup required. > ๐Ÿ•’ **Last updated:** 2026-04-23 ยท **๐Ÿ› ๏ธ 5 tools** ยท **๐Ÿ“š 2 resources** ยท **๐Ÿ”Œ Full MCP Protocol support** ยท **๐Ÿ’ฐ Pay Per Event pricing** Home Assistant is the most popular open-source home automation platform, connecting hundreds of smart device brands into one unified system. This MCP (Model Context Protocol) server lets AI assistants interact with your Home Assistant instance directly. It provides **5 tools** (get_states, get_state, call_service, get_entities, get_services) and **2 resources** (entities list, services list) so your AI can read sensor data, toggle lights, adjust thermostats, play media, and call any Home Assistant service. The server runs in standby mode on Apify's infrastructure, meaning it stays active and responds instantly to requests. You provide your Home Assistant URL and a long-lived access token in each request body. There is no startup delay, no Docker containers to manage, and no port forwarding required. Just connect your AI assistant to this MCP endpoint and start controlling your smart home with natural language commands. | ๐ŸŽฏ Target Audience | ๐Ÿ’ก Use Cases | |---|---| | Smart home enthusiasts | Control devices through AI chat interfaces | | Home automation developers | Build AI-driven automation workflows | | IoT researchers | Prototype voice and text-based device control | | Accessibility advocates | Enable hands-free home control via AI | | System integrators | Connect Home Assistant to AI-driven dashboards | | Tech hobbyists | Experiment with MCP protocol and smart devices | --- ### ๐Ÿ“‹ What the Home Assistant MCP Server does - ๐Ÿ”Œ **Get all entity states** to see every device, sensor, and switch in your Home Assistant - ๐ŸŽฏ **Get specific entity state** to check the current value of any sensor, light, or switch - ๐Ÿ› ๏ธ **Call any service** to toggle lights, set temperatures, play media, or trigger automations - ๐Ÿ“‹ **List all entities** to discover available devices and their entity IDs - ๐Ÿ“š **List all services** to see every action your Home Assistant supports - ๐Ÿ’ฐ **Pay Per Event pricing** so you only pay for the requests you make The MCP server acts as a bridge between AI assistants and your Home Assistant instance. When your AI needs to check a temperature sensor, it calls the get_state tool with the entity ID. When it needs to turn on a light, it calls call_service with the appropriate domain, service, and entity. The server forwards these requests to your Home Assistant's REST API and returns the results to the AI. > ๐Ÿ’ก **Why it matters:** Without an MCP server, connecting an AI assistant to Home Assistant requires custom code, API wrappers, and server management. This actor handles all of that, giving your AI direct access to your smart home through a standard protocol. --- ### ๐ŸŽฌ Full Demo _๐Ÿšง Coming soon..._ --- ### โš™๏ธ Input
FieldTypeRequiredDescription
This actor runs in standby mode. No input is required at startup. Credentials are provided in each request body.
**Each request body must include:** | Field | Type | Required | Description | |---|---|---|---| | **homeAssistantUrl** | string | Yes | URL of your Home Assistant instance (e.g., `https://homeassistant.local:8123`) | | **homeAssistantApiKey** | string | Yes | Long-lived access token from Home Assistant | **Example 1: Get all entity states** ```json { "tool": "get_states", "homeAssistantUrl": "https://homeassistant.local:8123", "homeAssistantApiKey": "your_long_lived_access_token" } ```` **Example 2: Call a service to toggle a light** ```json { "tool": "call_service", "domain": "light", "service": "toggle", "entity_id": "light.living_room", "homeAssistantUrl": "https://homeassistant.local:8123", "homeAssistantApiKey": "your_long_lived_access_token" } ``` > โš ๏ธ **Good to Know:** You need a running Home Assistant instance and a long-lived access token. Create the token at Profile > Long-Lived Access Tokens in your Home Assistant dashboard. Your Home Assistant must be accessible from the internet (or use a tunnel like Nabu Casa). *** ### ๐Ÿ“Š Output #### ๐Ÿงพ Schema | Emoji | Field | Type | Description | |---|---|---|---| | ๐Ÿ†” | entity\_id | string | Unique identifier for the device or sensor | | ๐Ÿ“Š | state | string | Current state value (on, off, temperature, etc.) | | ๐Ÿท๏ธ | attributes | object | Device attributes (brightness, color, unit, etc.) | | ๐Ÿ“… | last\_changed | string | When the state last changed | | ๐Ÿ“… | last\_updated | string | When the state was last refreshed | | ๐Ÿ”ง | domain | string | Entity domain (light, switch, sensor, etc.) | | ๐Ÿ“‹ | friendly\_name | string | Human-readable device name | | โš ๏ธ | error | string | Error message if the request failed | #### ๐Ÿ“ฆ Sample records
๐Ÿ“„ Light entity state ```json { "entity_id": "light.living_room", "state": "on", "attributes": { "friendly_name": "Living Room Light", "brightness": 255, "color_temp": 370, "supported_features": 63 }, "last_changed": "2026-04-16T10:30:00.000Z", "last_updated": "2026-04-16T10:30:00.000Z" } ```
๐Ÿ“„ Temperature sensor state ```json { "entity_id": "sensor.outdoor_temperature", "state": "72.4", "attributes": { "friendly_name": "Outdoor Temperature", "unit_of_measurement": "F", "device_class": "temperature" }, "last_changed": "2026-04-16T11:00:00.000Z", "last_updated": "2026-04-16T11:05:00.000Z" } ```
๐Ÿ“„ Service call response ```json { "domain": "light", "service": "toggle", "entity_id": "light.living_room", "result": "success", "new_state": "off" } ```
*** ### โœจ Why choose this Actor | Feature | Details | |---|---| | ๐Ÿ”Œ Full MCP support | Standard Model Context Protocol for AI assistant integration | | ๐Ÿ› ๏ธ 5 tools | Get states, get state, call service, list entities, list services | | ๐Ÿ“š 2 resources | Entities list and services list for discovery | | โšก Standby mode | Always running, instant response with no cold start | | ๐Ÿ  Any device | Works with any device integrated into Home Assistant | | ๐Ÿ’ฐ Pay Per Event | Only pay for the requests you actually make | | ๐Ÿ”’ Secure | Credentials sent per-request, never stored | > ๐Ÿ“Š **Control any of the 2,000+ device integrations supported by Home Assistant through a single MCP endpoint.** *** ### ๐Ÿ“ˆ How it compares to alternatives | Feature | This Actor | Self-Hosted MCP | Custom API Wrapper | |---|---|---|---| | No server management | โœ… | โŒ | โŒ | | Standard MCP protocol | โœ… | โœ… | โŒ | | Instant response (standby) | โœ… | Depends | Depends | | Pay Per Event pricing | โœ… | โŒ | โŒ | | Works with any AI assistant | โœ… | โœ… | Custom | | No coding required | โœ… | โŒ | โŒ | | Automatic scaling | โœ… | โŒ | โŒ | Connect your AI to Home Assistant in minutes instead of building and maintaining custom infrastructure. *** ### ๐Ÿš€ How to use 1. **Create an Apify account** - [Sign up free with $5 credit](https://console.apify.com/sign-up?fpr=vmoqkp) 2. **Set up Home Assistant** - Install Home Assistant and integrate your smart devices 3. **Create an access token** - Go to Profile > Long-Lived Access Tokens in Home Assistant 4. **Start the MCP Server** - Launch the actor in standby mode on Apify 5. **Connect your AI assistant** - Point your MCP-compatible AI to the actor's endpoint with your credentials > โฑ๏ธ **Setup takes under 5 minutes. The server stays running and responds to requests instantly.** *** ### ๐Ÿ’ผ Business use cases
๐Ÿ  Smart Home Control
  • Toggle lights and switches through AI chat
  • Check sensor readings with natural language
  • Adjust thermostats and climate controls remotely
  • Trigger automation scenes via AI commands
 ๐Ÿ”ง Development & Prototyping
  • Build AI-driven home automation prototypes
  • Test MCP protocol integrations with real devices
  • Develop custom AI assistants for smart buildings
  • Create voice-controlled device management systems
โ™ฟ Accessibility
  • Enable hands-free home control for mobility-limited users
  • Create text-based interfaces for hearing-impaired users
  • Build simplified AI interfaces for elderly care
  • Automate routine tasks with conversational triggers
 ๐Ÿ“Š Monitoring & Analytics
  • Collect sensor data for energy usage analysis
  • Monitor home security sensors through AI dashboards
  • Track environmental conditions across rooms
  • Build reporting systems from device state data
*** *** ### ๐ŸŒŸ Beyond business use cases Data like this powers more than commercial workflows. The same structured records support research, education, civic projects, and personal initiatives.
#### ๐ŸŽ“ Research and academia - Empirical datasets for papers, thesis work, and coursework - Longitudinal studies tracking changes across snapshots - Reproducible research with cited, versioned data pulls - Classroom exercises on data analysis and ethical scraping #### ๐ŸŽจ Personal and creative - Side projects, portfolio demos, and indie app launches - Data visualizations, dashboards, and infographics - Content research for bloggers, YouTubers, and podcasters - Hobbyist collections and personal trackers
#### ๐Ÿค Non-profit and civic - Transparency reporting and accountability projects - Advocacy campaigns backed by public-interest data - Community-run databases for local issues - Investigative journalism on public records #### ๐Ÿงช Experimentation - Prototype AI and machine-learning pipelines with real data - Validate product-market hypotheses before engineering spend - Train small domain-specific models on niche corpora - Test dashboard concepts with live input
### ๐Ÿค– Ask an AI assistant about this scraper Open a ready-to-send prompt about this ParseForge actor in the AI of your choice: - ๐Ÿ’ฌ [**ChatGPT**](https://chat.openai.com/?q=How%20do%20I%20use%20the%20Home%20Assistant%20MCP%20Server%20by%20ParseForge%20on%20Apify%3F%20Show%20me%20input%20examples%2C%20output%20fields%2C%20common%20use%20cases%2C%20and%20how%20to%20integrate%20it%20into%20a%20workflow.) - ๐Ÿง  [**Claude**](https://claude.ai/new?q=How%20do%20I%20use%20the%20Home%20Assistant%20MCP%20Server%20by%20ParseForge%20on%20Apify%3F%20Show%20me%20input%20examples%2C%20output%20fields%2C%20common%20use%20cases%2C%20and%20how%20to%20integrate%20it%20into%20a%20workflow.) - ๐Ÿ” [**Perplexity**](https://perplexity.ai/search?q=How%20do%20I%20use%20the%20Home%20Assistant%20MCP%20Server%20by%20ParseForge%20on%20Apify%3F%20Show%20me%20input%20examples%2C%20output%20fields%2C%20common%20use%20cases%2C%20and%20how%20to%20integrate%20it%20into%20a%20workflow.) - ๐Ÿ…’ [**Copilot**](https://copilot.microsoft.com/?q=How%20do%20I%20use%20the%20Home%20Assistant%20MCP%20Server%20by%20ParseForge%20on%20Apify%3F%20Show%20me%20input%20examples%2C%20output%20fields%2C%20common%20use%20cases%2C%20and%20how%20to%20integrate%20it%20into%20a%20workflow.) ### โ“ Frequently Asked Questions
๐Ÿ’ณ Do I need a paid Apify plan to run this actor? No. You can start right now on the free Apify plan, which includes **$5 in free monthly credit**. That is enough to run this actor several times and explore the output before committing to anything. Paid plans unlock higher limits, more concurrent runs, and larger datasets. [Create a free Apify account here](https://console.apify.com/sign-up?fpr=vmoqkp) to get started.
๐Ÿšจ What happens if my run fails or returns no results? Failed runs are not charged. If the source site changes, proxies get rate-limited, or a specific input matches nothing, re-run the actor or open our [contact form](https://tally.so/r/BzdKgA) and we will investigate. You can also check the run log in the Apify console to see why the run stopped.
๐Ÿ“ How many items can I scrape per run? Free users are limited to **10 items per run** so you can preview the output and confirm the actor works for your use case. Paid users can raise maxItems up to **1,000,000** per run. [Upgrade here](https://console.apify.com/sign-up?fpr=vmoqkp) if you need full scale.
๐Ÿ•’ How fresh is the data? Every run fetches live data at the moment of execution. There is no cache or delay: the records you get reflect what the source returned at that moment. Schedule the actor to maintain a rolling snapshot of the data you need.
๐Ÿง‘โ€๐Ÿ’ป Can I call this actor from my own code? Yes. Apify exposes every actor as a REST endpoint and ships first-class SDKs for [Node.js](https://docs.apify.com/sdk/js) and [Python](https://docs.apify.com/sdk/python). You can start a run, read the dataset, and handle webhooks from your own app in a few lines. All you need is your Apify API token.
๐Ÿ“ค How do I export the data? Every Apify dataset can be downloaded in one click from the console as CSV, JSON, JSONL, Excel, HTML, XML, or RSS. You can also pull results programmatically via the [Apify API](https://docs.apify.com/api/v2) or stream them into BigQuery, S3, and other destinations through built-in integrations.
๐Ÿ“… Can I schedule the actor to run automatically? Yes. Use the Apify scheduler to run the actor on any cadence, from hourly to monthly. Results are saved to your dataset and can be delivered to webhooks, email, Slack, cloud storage, or automation tools such as Zapier and Make. ***
### ๐Ÿ”Œ Automating Home Assistant MCP Server Integrate the Home Assistant MCP Server into your workflow using the Apify API or client libraries. **Node.js:** ```javascript import { ApifyClient } from 'apify-client'; const client = new ApifyClient({ token: 'YOUR_API_TOKEN' }); const run = await client.actor("parseforge/home-assistant-mcp-server").call({}); // The actor runs in standby mode - connect to it via the MCP endpoint console.log("MCP server running at:", run.defaultKeyValueStoreId); ``` **Python:** ```python from apify_client import ApifyClient client = ApifyClient("YOUR_API_TOKEN") run = client.actor("parseforge/home-assistant-mcp-server").call(run_input={}) ## The actor runs in standby mode - connect to it via the MCP endpoint print("MCP server running") ``` - ๐Ÿ“– [Apify API reference](https://docs.apify.com/api/v2) - ๐Ÿ [Python client docs](https://docs.apify.com/api/client/python) - ๐Ÿ“ฆ [Node.js client docs](https://docs.apify.com/api/client/js) **Schedules:** The MCP server runs in standby mode, so it stays active continuously. No scheduling is needed. It responds to requests as they come in, with no cold start delay. ### ๐Ÿ”Œ Integrate with any app - ๐Ÿ”— **Make (Integromat)** - Connect Home Assistant events to 1,500+ apps and services - ๐Ÿ”— **Zapier** - Trigger workflows based on Home Assistant state changes - ๐Ÿ”— **Slack** - Get notified about smart home events in your channel - ๐Ÿ”— **Airbyte** - Stream sensor data into your data warehouse for analytics - ๐Ÿ”— **GitHub** - Store device configuration and automation scripts - ๐Ÿ”— **Google Drive** - Log sensor readings to spreadsheets automatically *** ### ๐Ÿ”— Recommended Actors | Actor | Description | |---|---| | [Markdown to PDF MCP Server](https://apify.com/parseforge/markdown-to-pdf-mcp) | Convert markdown documents to PDF through MCP protocol | | [HTML to JSON Smart Parser](https://apify.com/parseforge/html-to-json-smart-parser) | Parse HTML content into structured JSON data | | [Smart Apify Actor Scraper](https://apify.com/parseforge/smart-apify-actor-scraper) | Discover and analyze Apify actors with quality metrics | | [Lead Formatter Tool](https://apify.com/parseforge/lead-formatter) | Format and enrich lead data for CRM systems | | [MultiSite URL Shortener](https://apify.com/parseforge/multisite-url-shortener) | Generate shortened URLs across multiple services | > ๐Ÿ’ก **Pro Tip:** Combine the Home Assistant MCP Server with Make or Zapier to create automated workflows that respond to smart home events with external actions. *** **๐Ÿ†˜ Need Help?** [**Open our contact form**](https://tally.so/r/BzdKgA) and we will get back to you within 24 hours. We are happy to help with custom setups, integrations, or feature requests. *** > **Disclaimer:** This actor is not affiliated with, endorsed by, or connected to Home Assistant or Nabu Casa. It integrates with Home Assistant through its published REST API. Use responsibly and in accordance with applicable terms of service. # Actor input Schema ## Actor input object example ```json {} ``` # 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 = {}; // Run the Actor and wait for it to finish const run = await client.actor("parseforge/home-assistant-mcp-server").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 = {} # Run the Actor and wait for it to finish run = client.actor("parseforge/home-assistant-mcp-server").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 '{}' | apify call parseforge/home-assistant-mcp-server --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=parseforge/home-assistant-mcp-server", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "Home Assistant MCP Server", "description": "Control your Home Assistant smart home devices through AI agents using Model Context Protocol (MCP). Get states, call services, list entities, and manage lights, switches, sensors, climate controls, and more. Perfect for AI-powered home automation and voice assistants.", "version": "0.1", "x-build-id": "vANFpcAxmuTLrSWrD" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/parseforge~home-assistant-mcp-server/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-parseforge-home-assistant-mcp-server", "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/parseforge~home-assistant-mcp-server/runs": { "post": { "operationId": "runs-sync-parseforge-home-assistant-mcp-server", "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/parseforge~home-assistant-mcp-server/run-sync": { "post": { "operationId": "run-sync-parseforge-home-assistant-mcp-server", "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": {} }, "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 } } } } } } } } } } ```