# Real Estate Agent Lead-Gen — Phones & Verified Emails (`nexgendata/realestate-agent-leadgen`) Actor Find real-estate AGENTS / brokerages and their PUBLIC business contact info by ZIP or city: name, brokerage, title, phone, website, and MX-verified business email. For B2B outreach to realtors. Public agent/business data only — not consumer skip-tracing. - **URL**: https://apify.com/nexgendata/realestate-agent-leadgen.md - **Developed by:** [NexGenData](https://apify.com/nexgendata) (community) - **Categories:** Real estate, Lead generation - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $5.00 / 1,000 agent founds 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 ## 🏠 Real Estate Agent Lead-Gen — MX-Verified Realtor Contacts by City & ZIP Build targeted realtor contact lists in minutes. Give this actor a list of cities or ZIP codes and it returns one clean record per real-estate agent — agent / team name, brokerage, title, phone — plus a **business email pulled from the agent's own website and MX-verified** before it lands in your dataset. Perfect for **recruiting brokerages**, **vendors selling to agents** (CRMs, photographers, sign companies, title & mortgage), and **referral networks** building a roster by market. No login, no scraping of consumer data — just the public business contact info agents publish so people can reach them. Optional one-run delivery straight to your **Notion CRM**. It uses **only public agent and business-contact data** — the same listings, brokerages, phone numbers, and websites anyone can see on Google Maps and the agent's own site. It deliberately does **not** touch consumer/homeowner data, MLS-gated content, or anything behind a login. ### 📊 Sample Output [![Real Estate Agent Lead-Gen sample output — public real-estate agents in Miami, FL enriched with MX-verified business contact emails, brokerage, phone, and email status for B2B agent outreach, brokerage recruiting, and referral networks](https://api.apify.com/v2/key-value-stores/8gLgXMBveEI1tTz1z/records/realestate-agent-leadgen-sample)](https://apify.com/nexgendata/realestate-agent-leadgen?fpr=2ayu9b) Real agents returned by this actor for **Miami, FL** — every email below was **MX-verified** in the same run: | Agent / Team | Brokerage | Phone | Verified Business Email | |---|---|---|---| | Ivan and Mike Team | Compass | (305) 907-7948 | martirena96@gmail.com | | Miami Realty Solution Group | Independent | (305) 728-0840 | martini@miamirealtysolution.com | | Sebastian Acosta | ONE Sotheby's Int'l | (305) 244-6222 | sacosta@onesothebysrealty.com | | Blackbook Properties | Blackbook Properties | (786) 400-2296 | contact@condoblackbook.com | | Riley Smith Group | Riley Smith Group | (305) 342-1623 | rileys@rileysmithgroup.com | > Every email above was found by **resolving the agent's listed website** (and its `/contact` / `/about` pages) and then **MX-verified** against the domain's real mail server — a Maps-only scraper would hand you the phone but not a reachable, deliverable email. In this 8-agent Miami run, 5 of 8 agents had a verified business email; the other 3 still returned full name, brokerage, phone, rating, and website. ### ⚖️ vs the alternatives | | NexGenData Real Estate Agent Lead-Gen | cleansyntax realtor-agents | generic Maps scraper | |---|---|---|---| | What you get | **Agents + brokerage + phone + MX-verified email** | Raw listing rows | Place name + phone | | Email | **Found on agent site + MX-verified** | Not included | Not included | | Phone | **Per-agent, formatted + international** | Sometimes | Yes | | Discovery | **By city / ZIP, Maps-backed** | Bulk rows, you filter | Single query | | One-run CRM delivery | **Built-in Notion connector** | No | No | | Pricing model | $0.005 / agent found + $0.010 / verified email | ~$3 / 1k raw rows | Per-query / compute | | Output | Flat typed fields, ready for outreach | Listings to clean yourself | Loose place data | Most teams pick this actor not because raw rows are cheaper somewhere else, but because what you get back is **actionable**: the emails are **found on the agent's own website and MX-verified** (your outreach list isn't full of dead addresses), you get a **formatted phone** for every agent, and the whole roster can drop straight into your **Notion CRM** in one run. A bulk-listings export at $3/1k gives you rows to clean; this gives you a contact you can email today. You only pay the small per-email surcharge **when an email is actually found and verified** — no email, no charge. ### What you get Per agent, a flat, typed record: - **Identity** — `name`, `brokerage`, `title` - **Contact** — `phone`, `phone_international`, `email` (primary, verified), `emails[]` (all found), `email_source` (`website` / `none`), `email_verified` (MX check) - **Profile** — `agent_profile_url`, `website`, `social_links` (facebook / instagram / linkedin) - **Coverage** — `areas_served`, `address`, `latitude`, `longitude` - **Reputation** — `rating`, `review_count` - **Provenance** — `source`, `source_query`, `scraped_at`, `status` (`ok` / `no_email` / error) > `maxAgents` is a **hard cap** across all locations, so a broad multi-city search can never blow up your cost — compute and per-agent charges stop at the cap. ### Sample inputs **1. One city** ```json { "locations": ["Miami, FL"], "maxAgents": 50 } ```` **2. A list of ZIP codes** ```json { "locations": ["78704", "78745", "78702"], "maxAgents": 100 } ``` **3. Mixed cities and ZIPs, with a niche keyword** ```json { "locations": ["Austin, TX", "78704"], "keywords": ["luxury real estate agent"], "maxAgents": 80 } ``` **4. Phone-only run (skip email resolution for speed)** ```json { "locations": ["Scottsdale, AZ"], "resolveEmails": false, "maxAgents": 50 } ``` **5. Build a list and deliver straight to your Notion CRM** ```json { "locations": ["Denver, CO"], "maxAgents": 100, "notionConnector": "your-notion-mcp-connector" } ``` #### Input fields | Field | Type | What it does | |---|---|---| | `locations` | array | **Required.** One or more `ZIP` codes or `City, ST` strings to search (e.g. `78704`, `Miami, FL`). One per line. | | `keywords` | array | Maps search phrases run per location. Defaults to `real estate agents`. Add `realtor`, `real estate broker`, or a niche like `luxury real estate agent`. Optional. | | `maxAgents` | int | **Hard cap** on total agents returned across all locations (1–1000). Keeps cost predictable. | | `resolveEmails` | bool | Visit each agent's website (+ `/contact`, `/about`) to find a business email and MX-verify it. Turn off for a faster phone-only run. Default on. | | `proxyConfiguration` | object | Apify proxy — **residential** is the default and strongly recommended (the Maps source blocks datacenter IPs). | | `notionConnector` | string | Optional one-run delivery to your Notion workspace. | ### 📄 Sample record (JSON) One representative record straight from the live Miami run above: ```json { "name": "Riley Smith Group | Best Miami Realtors", "brokerage": "Riley Smith Group", "title": "Real estate agent", "phone": "(305) 342-1623", "phone_international": "+13053421623", "email": "rileys@rileysmithgroup.com", "email_verified": true, "emails": ["rileys@rileysmithgroup.com"], "email_source": "website", "agent_profile_url": "https://www.google.com/maps/search/?api=1&query=Riley+Smith+Group...", "website": "https://www.rileysmithgroup.com/", "social_links": { "facebook": "https://www.facebook.com/rileysmithgroup", "instagram": "https://www.instagram.com/rileysmithgroup", "linkedin": "https://www.linkedin.com/company/riley-smith-group" }, "areas_served": "Miami, FL", "rating": 4.8, "review_count": 0, "source": "google_maps", "source_query": "real estate agents in Miami, FL", "scraped_at": "2026-06-15T00:44:47Z", "status": "ok" } ``` ### ⚙️ How it works 1. **Location → agent discovery** — for each `location` (ZIP or `City, ST`) the actor runs your `keywords` (default `real estate agents`) against Google Maps and collects matching agents, teams, and brokerages — deduped, capped at `maxAgents`. From each listing it reads name, brokerage, title, phone, rating, address, website, and social links. 2. **Website resolution** — when an agent lists a website, the actor visits it and its likely contact pages (`/contact`, `/about`) to extract a business email. This is where agents actually publish the address they want business inquiries sent to, so it materially raises yield over a Maps-only scrape. 3. **MX verification** — every candidate email is checked against the domain's real mail servers (MX records) before it's marked `email_verified: true`, so your outreach list isn't full of typo'd or dead addresses. It does not send a test email. 4. **Output (+ optional Notion)** — each agent is written as a flat, typed record. Authorize a Notion connector and the whole roster lands in your CRM in the same run. > **Public data only.** This actor reads the same public Google Maps listings and agent websites anyone can open in a browser, plus the business contact email the agent chose to publish. It does **not** touch consumer/homeowner records, MLS-gated data, or anything behind a login. ### 📈 Yield — set the right expectation Not every agent publishes a reachable business email on their website — that's a property of the market, not the scraper. In practice roughly **50–70%** of discovered agents yield a reachable, MX-verified business email, depending on the market (dense metros with established teams skew higher; sparse rural ZIPs lower). The rest come back with `status: no_email` but still return full name, brokerage, phone, rating, website, and social links — useful for phone outreach on its own. You pay **$0.005 per agent found** and only an extra **$0.010 when a business email is found *and* MX-verified** for that agent. No email, no email charge — so your spend tracks the value you actually receive. ### 💰 Pricing example - **Per agent found:** $0.005 (name, brokerage, phone, website, rating) - **Per MX-verified email:** $0.010 (charged only on a verified hit) A **100-agent run** where 60 agents yield a verified email = `(100 × $0.005) + (60 × $0.010) = $0.50 + $0.60 = $1.10`. A phone-only run of the same 100 agents (`resolveEmails: false`) = `$0.50`. No monthly minimum, no seats. You're billed per agent found, and only extra for emails that actually verify. ### ⚖️ Legal & ToS This actor reads **only public real-estate agent and business-contact data** — the listings, brokerages, phone numbers, and website emails agents publish so clients, recruiters, and vendors can reach them. It does **not** access consumer or homeowner data, private MLS records, data behind authentication, or anything behind a login. The intended use case is **B2B outreach** — recruiting brokerages reaching agents, vendors selling to agents, and referral networks building a roster. You are responsible for using the output in line with the source sites' terms, anti-spam laws (e.g. CAN-SPAM, GDPR/CASL), Do-Not-Call rules where they apply, and your local regulations. ### 🔗 Related Actors Pair this with the rest of the NexGenData lead-gen & outreach stack: - [📍 Google Maps Extractor — Local Business Data](https://apify.com/nexgendata/google-maps-extractor?fpr=2ayu9b) — pull any local-business category (not just agents) with ratings and contact data at scale - [✉️ B2B Contact Enricher — Verified Emails & Phones](https://apify.com/nexgendata/b2b-contact-enricher?fpr=2ayu9b) — enrich any list of names/companies/domains with MX-verified business emails - [🗂️ Leads to Notion CRM — Auto-Sync Pipeline](https://apify.com/nexgendata/leads-to-notion-crm?fpr=2ayu9b) — push scraped agent records straight into a Notion CRM - 🏢 **About NexGenData** — we maintain 260+ production Apify actors for lead-gen, competitive intelligence, and web data. Browse the full catalog at [apify.com/nexgendata](https://apify.com/nexgendata?fpr=2ayu9b). ### ❓ FAQ **Q: Do I need a login or API key?** A: No. The actor works entirely off public Google Maps listings and agent websites — no login, no MLS access, no API quota. **Q: Where do the emails come from?** A: The **agent's own website** — the actor visits the site they list and its `/contact` / `/about` pages and extracts the business email they publish there. `email_source` tells you the source (`website` or `none`), and `email_verified` shows the MX result. **Q: Is this consumer / homeowner data?** A: No. This actor returns **business contact data for real-estate professionals** — the same info agents publish so people can hire them. It does not touch homeowner, buyer, or any consumer records. **Q: What does "MX-verified" actually mean?** A: Before an email is marked `email_verified: true`, the actor checks that the domain has live mail-exchange (MX) records — a real mail server that can receive mail. This filters out typos and dead domains so your outreach bounces less. It does not send a test email. **Q: Why did some agents come back with no email?** A: They simply didn't publish a reachable business email on their website (`status: no_email`). Roughly 50–70% of agents do, depending on the market; the rest don't. You still get their name, brokerage, phone, rating, website, and socials — and you're not charged the email fee for them. **Q: Can I search by ZIP code?** A: Yes. `locations` accepts ZIP codes (`78704`), `City, ST` strings (`Miami, FL`), or a mix of both — one per line. **Q: Can results go straight into Notion?** A: Yes — authorize a Notion MCP connector in Apify Console → Settings → API & Integrations, select it in `notionConnector`, and the agents + emails are written into your Notion workspace in the same run. The actor never sees your Notion credentials. ### 🆘 Troubleshooting - **`status: no_email`** — that agent didn't publish a reachable business email on their website. Expected for a chunk of any market; not an error, and not billed the email fee. - **Fewer emails than agents** — normal. Only ~50–70% of agents publish a verified business email depending on the market; you pay $0.005 per agent found regardless, and only $0.010 extra on a verified hit. - **Datacenter proxy errors / empty results** — the Google Maps source blocks datacenter IPs. Keep `proxyConfiguration` on **RESIDENTIAL** (the default). - **A location returned few agents** — sparse or very specific ZIPs have fewer agents. Try the surrounding `City, ST`, add nearby ZIPs, or broaden `keywords` (e.g. add `realtor`, `real estate broker`). - **Email looks unverified** (`email_verified: false`) — the address was found but its domain has no live MX record; treat it as low-confidence. - **Want phone only / a faster run** — set `resolveEmails: false` to skip website resolution and the email surcharge entirely. *** ### ⭐ Found this useful? If this actor saved you list-building time, a quick **[review on the Apify Store](https://apify.com/nexgendata/realestate-agent-leadgen?fpr=2ayu9b)** helps other teams discover it. Feature request or bug? Open it from the **Issues** tab — we read every one. # Actor input Schema ## `locations` (type: `array`): One or more locations to search for real-estate agents. Use ZIP codes (e.g. 78704) or 'City, ST' (e.g. Miami, FL). One per line. ## `keywords` (type: `array`): Maps search phrases run per location. Defaults to 'real estate agents'. You can add 'realtor', 'real estate broker', or a niche like 'luxury real estate agent'. ## `maxAgents` (type: `integer`): Hard cap on the total number of agents returned across all locations. Compute can never exceed this. Max 1000. ## `resolveEmails` (type: `boolean`): When on, the actor visits each agent's listed website (and /contact, /about) to extract a business email, then MX-verifies it. Turn off for a faster phone-only run. ## `proxyConfiguration` (type: `object`): Proxy settings. RESIDENTIAL is strongly recommended (and the default) because the Google Maps source blocks datacenter IPs. ## `notionConnector` (type: `string`): Optional Apify Notion connector ID. When set, the run also writes a summary page of the agents (and their verified emails) to your Notion workspace. ## `notionParentId` (type: `string`): Optional Notion parent page ID to nest the delivered summary under. ## Actor input object example ```json { "locations": [ "78704", "Miami, FL" ], "keywords": [ "real estate agents" ], "maxAgents": 50, "resolveEmails": true, "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ] } } ``` # 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 = { "locations": [ "78704", "Miami, FL" ], "keywords": [ "real estate agents" ], "maxAgents": 50, "resolveEmails": true, "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ] } }; // Run the Actor and wait for it to finish const run = await client.actor("nexgendata/realestate-agent-leadgen").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 = { "locations": [ "78704", "Miami, FL", ], "keywords": ["real estate agents"], "maxAgents": 50, "resolveEmails": True, "proxyConfiguration": { "useApifyProxy": True, "apifyProxyGroups": ["RESIDENTIAL"], }, } # Run the Actor and wait for it to finish run = client.actor("nexgendata/realestate-agent-leadgen").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 '{ "locations": [ "78704", "Miami, FL" ], "keywords": [ "real estate agents" ], "maxAgents": 50, "resolveEmails": true, "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ] } }' | apify call nexgendata/realestate-agent-leadgen --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=nexgendata/realestate-agent-leadgen", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "Real Estate Agent Lead-Gen — Phones & Verified Emails", "description": "Find real-estate AGENTS / brokerages and their PUBLIC business contact info by ZIP or city: name, brokerage, title, phone, website, and MX-verified business email. For B2B outreach to realtors. Public agent/business data only — not consumer skip-tracing.", "version": "0.0", "x-build-id": "v2BFuNcHZ41giHzIM" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/nexgendata~realestate-agent-leadgen/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-nexgendata-realestate-agent-leadgen", "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~realestate-agent-leadgen/runs": { "post": { "operationId": "runs-sync-nexgendata-realestate-agent-leadgen", "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~realestate-agent-leadgen/run-sync": { "post": { "operationId": "run-sync-nexgendata-realestate-agent-leadgen", "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", "required": [ "locations" ], "properties": { "locations": { "title": "Locations (ZIP or City, ST)", "type": "array", "description": "One or more locations to search for real-estate agents. Use ZIP codes (e.g. 78704) or 'City, ST' (e.g. Miami, FL). One per line.", "items": { "type": "string" } }, "keywords": { "title": "Search keywords", "type": "array", "description": "Maps search phrases run per location. Defaults to 'real estate agents'. You can add 'realtor', 'real estate broker', or a niche like 'luxury real estate agent'.", "default": [ "real estate agents" ], "items": { "type": "string" } }, "maxAgents": { "title": "Max agents (hard cap)", "minimum": 1, "maximum": 1000, "type": "integer", "description": "Hard cap on the total number of agents returned across all locations. Compute can never exceed this. Max 1000.", "default": 50 }, "resolveEmails": { "title": "Resolve & verify business emails", "type": "boolean", "description": "When on, the actor visits each agent's listed website (and /contact, /about) to extract a business email, then MX-verifies it. Turn off for a faster phone-only run.", "default": true }, "proxyConfiguration": { "title": "Proxy configuration", "type": "object", "description": "Proxy settings. RESIDENTIAL is strongly recommended (and the default) because the Google Maps source blocks datacenter IPs.", "default": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ] } }, "notionConnector": { "title": "Notion connector (optional)", "type": "string", "description": "Optional Apify Notion connector ID. When set, the run also writes a summary page of the agents (and their verified emails) to your Notion workspace." }, "notionParentId": { "title": "Notion parent page ID (optional)", "type": "string", "description": "Optional Notion parent page ID to nest the delivered summary under." } } }, "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 } } } } } } } } } } ```