# X / Twitter B2b Email Scraper (`scrapevanta/twitter-x-b2b-lead-generator-email-scraper`) Actor Twitter B2B Email Scraper extracts publicly available business emails, profile data, company details, and contact information from Twitter/X profiles. Ideal for lead generation, sales prospecting, outreach campaigns, market research, and building targeted B2B contact lists fast. - **URL**: https://apify.com/scrapevanta/twitter-x-b2b-lead-generator-email-scraper.md - **Developed by:** [ScrapeVanta](https://apify.com/scrapevanta) (community) - **Categories:** Lead generation, Social media, Automation - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $5.99 / 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/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 ### Twitter X B2b Lead Generator Email Scraper 🚀 Cold prospecting gets stuck when you can’t quickly turn Twitter X activity into real contact emails. **Twitter X B2b Lead Generator Email Scraper** extracts public email addresses from X (Twitter) profiles and tweets so you can build targeted lead lists fast. It’s ideal for twitter x lead generator email scraper workflows, twitter x email extractor for leads, and x.com email scraper for b2b teams. Sales teams, researchers, and data analysts use it to find journalists, founders, and crypto leads in real time—and collect up to thousands of emails per run based on your limits. --- ### See the Data: Sample Output Here's a real record from a single run: ```json { "searchTerm": "crypto", "title": "Name / Handle", "url": "https://x.com/example_profile", "description": "Bio / description text pulled from the profile or post context", "email": "contact@company.com", "email_domain": "company.com", "source_region": "Profiles", "country": "United States" } ```` | Field | Type | What It Tells You | |---|---|---| | `searchTerm` | string | Which keyword/topic you used to discover this lead (useful for segmenting results). | | `title` | string | The name/handle shown for the discovered account, so you can identify the person instantly. | | `url` | string | A direct link back to the source profile for quick verification and context. | | `description` | string | The bio/description text captured alongside the lead, helpful for scoring and personalization. | | `email` | string | The extracted email address you can use for outreach and lead follow-up. | | `email_domain` | string | The company/domain part of the email, great for filtering by industry or account lists. | | `source_region` | string | Whether the lead came from `Profiles` or `Posts` (or `All`, depending on your selection). | | `country` | string | The target country you selected for localized lead searching. | Export your full dataset as JSON, CSV, or Excel from the Apify dashboard. *** ### Setting It Up Drop this into your `input.json` and you're ready to go: ```json { "searchTerms": [ "saas founder", "marketing", "crypto" ], "country": "United States", "sourceRegion": "All", "engine": "legacy", "maxEmails": 20 } ``` | Parameter | Required | What It Does | |---|---|---| | `searchTerms` | ✅ | Provides the topics, hashtags, or job titles to search on X (Twitter) for potential leads. | | `country` | ✅ | Sets the country used for localized lead searching. | | `sourceRegion` | ✅ | Chooses whether to scrape `All`, `Profiles`, or `Posts` (Tweets). | | `engine` | ⬜ | Selects the scraping engine method: `cost-effective` or `legacy` (different speed/behavior tradeoffs). | | `maxEmails` | ✅ | Caps how many emails to collect so you can control the run size (minimum 1, up to 10000). | | ↳ `engine` = `cost-effective` | ⬜ | Uses the “Performance (New)” scraping approach described in the actor configuration. | | ↳ `engine` = `legacy` | ⬜ | Uses the “Standard” / legacy approach described in the actor configuration. | *** ### What It Does **Twitter X B2b Lead Generator Email Scraper** extracts public emails from X (Twitter) profiles and tweets, turning search keywords into outreach-ready lead records. #### Finds leads by your X keywords (profiles and tweets) Use `searchTerms` to define what you want to find on X (Twitter)—topics, hashtags, or job titles. The actor then collects contact emails associated with the discovered accounts so you can build a twitter x b2b lead scraping tool pipeline quickly. #### Filters by content type with `sourceRegion` Switch `sourceRegion` to `Profiles`, `Posts`, or `All` depending on whether your twitter x prospecting lead generation is account-focused or content-focused. This helps you control where the leads come from as you build a twitter x lead list builder. #### Produces clean, integration-friendly records Each discovered lead is saved with consistent fields like `email`, `email_domain`, `url`, and `description`, so downstream steps like deduping, CRM import, and enrichment are easier. The output is designed to support twitter x email scraping software workflows without extra reformatting. #### Uses your filters to keep results relevant Your `country` selection scopes the lead search for localized prospecting. Combined with `maxEmails`, you can run quick tests first, then scale once your lead quality looks right. #### Stops with a clear cap for cost control `maxEmails` limits how many emails are collected, so you can avoid runaway runs while testing different keyword sets. This makes it practical for iterative work in a twitter x b2b lead mining process. Overall, **Twitter X B2b Lead Generator Email Scraper** helps you go from X discovery to email leads in one automated run—fast. *** ### Why Twitter X B2b Lead Generator Email Scraper? There are plenty of ways to pull data from X—here's why Twitter X B2b Lead Generator Email Scraper stands out. #### Built for lead lists, not just raw pages You get structured lead records with `email` and `email_domain` alongside `url` and `description`. That’s exactly what teams need for outreach, scoring, and segmentation in x.com b2b lead generation automation. #### Flexible scraping engine choice You can pick an engine option via `engine` to match your priorities (speed vs. the “Standard” approach). This is useful when you’re running twitter x email extractor for leads at different scales. #### Practical output limits to match your workflow With `maxEmails`, you can collect just enough for validation or gather larger volumes up to the configured maximum. That supports twitter x lead generation with email without overpaying for unnecessary volume. *** ### Real-World Use Cases Here's how different teams put Twitter X B2b Lead Generator Email Scraper to work: **Sales Teams**\ A B2B sales team wants to prospect founders and decision-makers discussing their industry on X. They run the actor with a few targeted `searchTerms`, set `country` to match their ICP, and use `maxEmails` for quick daily refreshes. The result is a focused list of emails tied to profiles and content, so reps can start outreach sooner. **Marketing Agencies**\ An agency building campaigns for multiple niches needs consistent lead data per keyword theme. They run several batches using different search terms like marketing and saas founder, then segment leads by `email_domain` and source context using `source_region`. This helps them deliver clean datasets as inputs for outreach and reporting. **Freelance Researchers**\ A researcher compiling a contact database for journalists and founders wants verifiable sources. They rely on the `url` field for quick checks and use the `description` text to understand context before contacting anyone. The workflow turns twitter x contact email scraper goals into structured outputs without manual copy-paste. **Crypto & Tech Teams**\ A crypto startup wants to find relevant community leads and operators who publicly share their work. They set `searchTerms` around crypto-related topics, keep the scope aligned to a specific `country`, and pull up to their configured `maxEmails`. They then use the email addresses to streamline outreach for partnerships and announcements. **Developers & Automation Specialists**\ A data engineer wants to connect lead generation to an internal pipeline. They trigger the actor on a schedule and then import the dataset fields (`searchTerm`, `title`, `url`, `email`, `email_domain`, `source_region`, `country`) into a database for deduping and enrichment. This makes it a solid twitter x sales prospecting email tool component in an automation stack. *** ### How to Run It No code required. Here's how to get your first results in under 5 minutes: 1. **Open the actor on Apify**\ Go to [console.apify.com](https://console.apify.com) and open the actor page for Twitter X B2b Lead Generator Email Scraper. 2. **Enter your inputs**\ Add your `searchTerms`, set `country`, choose `sourceRegion` (`All`, `Profiles`, or `Posts`), and set `maxEmails` to control the run size. 3. **Configure the scraping method (optional)**\ If you want a different behavior than the default, set `engine` to either `cost-effective` or `legacy`. 4. **Start the run and watch the live log**\ Monitor progress in real time from the Apify run view. 5. **Open the Dataset tab to see results**\ As the run completes, you’ll see extracted leads with fields like `email`, `email_domain`, `url`, and `description`. 6. **Export in your preferred format**\ Download your dataset as JSON, CSV, or Excel directly from the Apify dashboard. The whole setup takes under 5 minutes — results start appearing quickly after launch. *** ### Export & Integration Options Once your data is collected, Twitter X B2b Lead Generator Email Scraper fits directly into your existing workflow. You can export your results from the Apify dataset tab as JSON, CSV, or Excel. If you’re building a twitter x lead list builder into a CRM, spreadsheet, or enrichment flow, these formats make it easy to move fast. For automation and engineering workflows, you can use Apify’s API and integrations (including options like webhooks, scheduled runs, and no-code tools such as Zapier/Make) to push data downstream when runs finish. *** ### Pricing Twitter X B2b Lead Generator Email Scraper runs on Apify, which includes a **free tier** — no credit card needed to start. Free tier usage begins with $5 platform credits on sign-up, enough for several real test runs. For larger campaigns, Apify uses pay-as-you-go billing based on Actor compute units (CU). Subscription plans are available for heavier workloads—check the Apify pricing page for the latest details. Start free at [apify.com](https://apify.com) — scale up when you need to. *** ### Reliability & Limitations | What We Handle | How | |---|---| | Rate limiting risk | Uses built-in scraping resilience with delays and fallbacks described at a high level. | | Data consistency | Saves structured lead records with consistent dataset fields. | | Run size control | Enforced by `maxEmails` so you can stop at the volume you want. | | Scope control | `sourceRegion` lets you restrict results to `Profiles`, `Posts`, or `All`. | Limitations: This actor extracts only **publicly available** emails associated with the targeted X (Twitter) content. It cannot access login-gated or private information, so some profiles may not yield an email if none is publicly present. For enterprise-scale needs or custom configurations, reach out and we’ll help. *** ### Frequently Asked Questions #### Is there a free plan? Yes—Apify offers a free tier with usage credits, so you can test Twitter X B2b Lead Generator Email Scraper before committing to larger runs. It’s a good fit for validating keyword sets and lead quality. #### Do I need to log in or create an account on X (Twitter)? No. This actor is intended to extract **publicly available** data from X (Twitter) without requiring you to log in. #### How accurate is the extracted data? The extracted email data is only as accurate as what is publicly present in the targeted profiles or posts. The actor outputs the detected email and `email_domain` alongside the `url` and `description` so you can verify context quickly. #### How many results can I get per run? You can control volume with `maxEmails`, which caps how many emails to collect. The maximum allowed value is 10000, and the default is 20. #### How fresh is the data? Results reflect what is publicly available when the actor runs. If you need fresher leads, schedule more frequent runs and adjust `maxEmails` for the desired daily/weekly volume. #### Is this legal? Does it comply with GDPR / CCPA? The actor is designed to work with **publicly available data**. However, compliance with GDPR, CCPA, and applicable regulations depends on how you store, process, and contact people—so you should apply your own legal review and outreach practices. #### Can I export to Google Sheets or Excel? Yes. You can export from the Apify dashboard as JSON, CSV, or Excel, then import into Google Sheets or your spreadsheet tool. This is especially useful for twitter x lead list builder workflows. #### Can I schedule this to run automatically? Yes. You can use Apify’s scheduling capabilities to run the actor on a recurring basis (for example, to refresh leads by keyword and country). #### Can I access results via the API? Yes. Apify supports programmatic access to actor runs and datasets via the Apify API, which is ideal if you want to integrate Twitter X B2b Lead Generator Email Scraper into a bigger data pipeline. #### What happens when the actor encounters an error? The actor is designed to be resilient and will keep producing dataset records when possible. If it cannot retrieve data for a particular request or run, you’ll see that reflected in the run logs and the resulting dataset content for what was successfully collected. *** ### Get Help & Use Responsibly Got a question about Twitter X B2b Lead Generator Email Scraper or a feature you'd like added? Email us at and we’ll help you get the best results—common requests include keyword strategy improvements and output workflow suggestions for crm imports. **publicly available data** only. It does **not** access private accounts, login-gated pages, or password-protected content. You are responsible for compliance with GDPR, CCPA, platform ToS, and applicable email/contact regulations. For data-removal requests, contact . Use responsibly, ethically, and only for lawful purposes. # Actor input Schema ## `searchTerms` (type: `array`): Topics, hashtags, or job titles to search on X (Twitter). ## `country` (type: `string`): Select the country for localized lead searching. ## `sourceRegion` (type: `string`): Select content type: Profiles or Posts (Tweets). ## `engine` (type: `string`): Select your preferred scraping method. ⚡ Performance (New): Faster, cheaper, uses residential proxies. 🛡️ Standard: Reliable, uses GOOGLE\_SERP proxy, but slower. ## `maxEmails` (type: `integer`): Limit the number of emails to collect. ## Actor input object example ```json { "searchTerms": [ "saas founder", "crypto", "marketing" ], "country": "United States", "sourceRegion": "All", "engine": "legacy", "maxEmails": 20 } ``` # 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 = { "searchTerms": [ "saas founder", "crypto", "marketing" ] }; // Run the Actor and wait for it to finish const run = await client.actor("scrapevanta/twitter-x-b2b-lead-generator-email-scraper").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 = { "searchTerms": [ "saas founder", "crypto", "marketing", ] } # Run the Actor and wait for it to finish run = client.actor("scrapevanta/twitter-x-b2b-lead-generator-email-scraper").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 '{ "searchTerms": [ "saas founder", "crypto", "marketing" ] }' | apify call scrapevanta/twitter-x-b2b-lead-generator-email-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=scrapevanta/twitter-x-b2b-lead-generator-email-scraper", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "X / Twitter B2b Email Scraper", "description": "Twitter B2B Email Scraper extracts publicly available business emails, profile data, company details, and contact information from Twitter/X profiles. Ideal for lead generation, sales prospecting, outreach campaigns, market research, and building targeted B2B contact lists fast.", "version": "1.0", "x-build-id": "6C4OT2EpqvJJbUoxt" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/scrapevanta~twitter-x-b2b-lead-generator-email-scraper/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-scrapevanta-twitter-x-b2b-lead-generator-email-scraper", "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/scrapevanta~twitter-x-b2b-lead-generator-email-scraper/runs": { "post": { "operationId": "runs-sync-scrapevanta-twitter-x-b2b-lead-generator-email-scraper", "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/scrapevanta~twitter-x-b2b-lead-generator-email-scraper/run-sync": { "post": { "operationId": "run-sync-scrapevanta-twitter-x-b2b-lead-generator-email-scraper", "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": [ "searchTerms", "country", "sourceRegion", "maxEmails" ], "properties": { "searchTerms": { "title": "Search Keywords", "type": "array", "description": "Topics, hashtags, or job titles to search on X (Twitter).", "items": { "type": "string" } }, "country": { "title": "Target Country", "enum": [ "United States", "United Kingdom", "Canada", "Australia", "Germany", "France", "India", "Japan", "Brazil", "Italy", "Spain", "Netherlands", "Sweden", "Norway", "Denmark", "Finland", "Poland", "Czech Republic", "Hungary", "Romania", "Bulgaria", "Croatia", "Slovenia", "Slovakia", "Estonia", "Latvia", "Lithuania", "Portugal", "Greece", "Cyprus", "Malta", "Luxembourg", "Ireland", "Belgium", "Austria", "Switzerland", "Liechtenstein", "Iceland", "South Korea", "China", "Mexico", "Argentina", "Chile", "Colombia", "Peru", "Venezuela", "Ecuador", "Uruguay", "Paraguay", "Bolivia", "Guyana", "Suriname", "French Guiana", "Falkland Islands (Malvinas)", "South Georgia and the South Sandwich Islands", "Bonaire, Sint Eustatius and Saba", "Curaçao", "Aruba", "Sint Maarten (Dutch part)", "Turks and Caicos Islands", "British Virgin Islands", "Anguilla", "Montserrat", "Antigua and Barbuda", "Barbados", "Dominica", "Grenada", "Saint Kitts and Nevis", "Saint Lucia", "Saint Vincent and the Grenadines", "Trinidad and Tobago", "Jamaica", "Bahamas", "Belize", "Costa Rica", "Guatemala", "Honduras", "Nicaragua", "Panama", "El Salvador", "Cuba", "Dominican Republic", "Haiti", "Puerto Rico", "U.S. Virgin Islands", "American Samoa", "Guam", "Northern Mariana Islands", "Saudi Arabia", "United Arab Emirates", "Bahrain", "Iraq", "Iran, Islamic Republic of", "Israel", "Jordan", "Kuwait", "Lebanon", "Oman", "Qatar", "Syrian Arab Republic", "Yemen", "Afghanistan", "Bangladesh", "Bhutan", "Maldives", "Nepal", "Pakistan", "Sri Lanka", "Myanmar", "Cambodia", "Lao People's Democratic Republic", "Thailand", "Viet Nam", "Malaysia", "Singapore", "Brunei Darussalam", "Philippines", "Indonesia", "Timor-Leste", "Papua New Guinea", "Fiji", "New Zealand", "Solomon Islands", "Vanuatu", "New Caledonia", "French Polynesia", "Wallis and Futuna", "Samoa", "Tonga", "Tuvalu", "Kiribati", "Nauru", "Federated States of Micronesia", "Marshall Islands", "Palau", "Cook Islands", "Niue", "Tokelau" ], "type": "string", "description": "Select the country for localized lead searching.", "default": "United States" }, "sourceRegion": { "title": "Content Type", "enum": [ "All", "Profiles", "Posts" ], "type": "string", "description": "Select content type: Profiles or Posts (Tweets).", "default": "All" }, "engine": { "title": "Scraping Engine", "enum": [ "cost-effective", "legacy" ], "type": "string", "description": "Select your preferred scraping method. ⚡ Performance (New): Faster, cheaper, uses residential proxies. 🛡️ Standard: Reliable, uses GOOGLE_SERP proxy, but slower.", "default": "legacy" }, "maxEmails": { "title": "Maximum Emails", "minimum": 1, "maximum": 10000, "type": "integer", "description": "Limit the number of emails to collect.", "default": 20 } } }, "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 } } } } } } } } } } ```