# Tinder Phone Number Scraper (`solid-scraper/tinder-phone-number-scraper`) Actor 📱 Tinder Phone Number Scraper helps you extract verified phone contacts from profiles for targeted outreach. Ideal for marketers, recruiters, and agencies—faster prospecting, cleaner lists, better conversions. 🚀 - **URL**: https://apify.com/solid-scraper/tinder-phone-number-scraper.md - **Developed by:** [SolidScraper](https://apify.com/solid-scraper) (community) - **Categories:** Lead generation, Automation, Other - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $2.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 ### Tinder Phone Number Scraper 🔍 **Tinder Phone Number Scraper** is a focused scraping tool that extracts phone numbers from Tinder profiles, bios, and post content—then saves results in a structured dataset you can use for lead enrichment and research workflows. If you’re searching for a **Tinder phone number scraper**, a **Tinder contact info extraction tool**, or a way to **Tinder scrape phone numbers** at scale, this actor helps you turn publicly available web data into a clean list of phone contacts—saving you hours of manual work. --- ### 🚀 Why choose Tinder Phone Number Scraper? | Feature | Benefit | | --- | --- | | ✅ **Phone number extraction from Tinder content** | Pulls phone numbers from Tinder bios, profiles, and post content for targeted lead lists | | ✅ **Keyword-based targeting** | Uses your keywords to find relevant profiles faster (great for **Tinder phone number finder** use cases) | | ✅ **Country targeting with dial code support** | Filters results by selected country code for more accurate **Tinder phone number list** outputs | | ✅ **Reliability improvements** | Includes resilience with delays and fallback-style behavior so long runs keep progressing | | ✅ **Structured dataset output** | Writes each result with fields like `phone_number`, `url`, `country`, and `dial_code` for easy exports | | ✅ **Incremental data saving** | Pushes discovered records as it goes, so you don’t lose progress during long jobs | --- ### 🔑 Key features - 🎯 **Keyword-driven extraction**: Use your own terms to power **Tinder phone number scraper** runs with better relevance. - 🌍 **Country code targeting**: Select a specific country (with its dial code) to filter phone formats in the output. - 📄 **Captures from multiple Tinder content surfaces**: Extracts from bios, profiles, and post content—not just one place. - 🛡️ **Resilience for large jobs**: Built to handle longer scraping tasks more reliably with run-time controls. - 💾 **Structured results ready for analysis**: Every pushed record includes key context fields for downstream filtering. - 🔄 **Avoids duplicates**: Keeps a “seen numbers” set so you don’t repeatedly collect the same phone number in one run. - 📊 **Limit control for lead volume**: Use `maxPhoneNumbers` to stop after enough results (helpful for **Tinder leads phone number extractor** workflows). --- ### 📝 Input Provide input via an `input.json` file. Example structure: ```json { "keywords": ["marketing", "founder"], "location": "London", "country": "United Kingdom (+44)", "maxPhoneNumbers": 20 } ```` #### Input Fields | Field | Required | Description | | --- | --- | --- | | `keywords` | ✅ | Keywords to guide the phone number extraction (e.g., “marketing”, “founder”). Use this to build your **Tinder contact details scraper** targeting. | | `location` | ❌ | Optional location filter (e.g., “London”, “California”). Leave empty for a global search. | | `country` | ✅ | Country to target for phone numbers. Choose one country so the scraper formats/filters phone numbers appropriately using that country’s dial code. | | `maxPhoneNumbers` | ❌ | Stop scraping after this many phone numbers are found. Higher values typically increase runtime (default is `20`). For free users, an internal cap may apply. | *** ### 📦 Output The actor saves each discovered record into the **Tinder Phone Numbers Dataset** as structured items. Example output object: ```json { "platform": "Tinder", "keyword": "marketing", "title": "No title", "description": "No data", "url": "No URL", "phone_number": "+447700900123", "country": "United Kingdom", "dial_code": "+44" } ``` #### Output Fields | Field | Type | Description | | --- | --- | --- | | `platform` | string | The platform label for each result (`"Tinder"`). | | `keyword` | string | The keyword used for that extraction batch. | | `title` | string | Title text associated with the discovered item (falls back to `"No title"`). | | `description` | string | Extracted text/context around the phone number (may be `"No data"`). | | `url` | string | The discovered source URL (may be `"No URL"` if not available). | | `phone_number` | string | The extracted phone number in E.164 format (deduplicated across the run). | | `country` | string | Target country name used for this run’s results. | | `dial_code` | string | Dial code used for formatting/filtering phone numbers. | You can export the dataset from Apify in formats like JSON or CSV, depending on your workflow. *** ### 🚀 How to use Tinder Phone Number Scraper (via Apify Console) 1. **Open Apify Console**\ Log in at [console.apify.com](https://console.apify.com) and go to the Actors section. 2. **Find Tinder Phone Number Scraper**\ Search for **Tinder Phone Number Scraper** and open the actor details page. 3. **Set your INPUT values**\ In the **INPUT** section, enter: `keywords` (required), `country` (required), and optionally `location` and `maxPhoneNumbers`. 4. **Review runtime expectations**\ If you request more phone numbers, the run can take longer. Use `maxPhoneNumbers` to control lead volume. 5. **Start the run**\ Click **Run**. Monitor the log output for progress and discovery updates. 6. **Wait for completion**\ The actor pushes results incrementally to the dataset as they’re found, so you can start analyzing once output begins. 7. **Open the OUTPUT dataset**\ After the run finishes, open **Scraped Phone Numbers** in the dataset tab. 8. **Export results**\ Export the dataset to JSON/CSV as needed for your CRM, spreadsheets, or analysis pipeline. No coding required—get **Tinder phone number scraper** results in minutes. *** ### ⚙️ Advanced features & SEO optimization - 🧠 **Engineered for Tinder phone number lead generation**: This Tinder phone number scraper is built specifically for “Tinder phone number list” style workflows using keywords and country targeting. - 🔄 **Handles long scraping runs**: Includes controls for large extraction tasks, and you can limit output with `maxPhoneNumbers`. - 🔎 **Targets relevance via keyword and location filters**: Helps improve outcomes when you’re using a **Tinder phone number finder** approach for specific niches. - 🧾 **Clean, structured records**: Each record includes `url`, `phone_number`, `keyword`, `country`, and `dial_code`—ideal for automated enrichment pipelines. - 💬 **Resilient extraction behavior**: Uses retries/fallback-style resilience so large scraping tasks don’t fail silently. *** ### ✅ Best use cases - 📈 **Lead generation for outbound campaigns**: Build a **Tinder phone number list** for outreach workflows with phone contacts. - 🔍 **B2C market research**: Analyze phone contact availability by keywords and country targeting for region-specific insights. - 🗂️ **CRM enrichment**: Feed extracted `phone_number` values into CRM matching and segmentation (pair with other public data). - 🎯 **Competitive intel & niche scouting**: Use **Tinder scrape phone numbers** to quickly gather phone contacts for specific communities or roles. - 📊 **Data analyst workflows**: Export structured results (`dial_code`, `country`, `url`) and join with other datasets for reporting. - 🧑‍💻 **Automation pipelines**: Automate **Tinder contact details scraper** steps as part of scheduled lead collection jobs. *** ### 🔧 Technical specifications - **Supported Input Formats** ✅\ `keywords` (array of strings), `location` (string), `country` (string from the predefined list), `maxPhoneNumbers` (integer). - **Proxy Support** ✅\ Built-in proxy support for reliable scraping during longer runs. - **Retry Mechanism** ✅\ Includes retries and fallbacks for resilience when requests fail. - **Dataset Structure** ✅\ Saves items to the **Tinder Phone Numbers Dataset** with the dataset view **Scraped Phone Numbers** using fields: `keyword`, `title`, `description`, `url`, `phone_number`, `country`, `dial_code`. - **Limit Controls** ✅\ `maxPhoneNumbers` stops extraction once enough unique phone numbers are found. - **Rate Limits & Performance**\ Large scraping tasks may take time—use `maxPhoneNumbers` to manage runtime. - **Limitations**\ Results depend on the presence of publicly available phone number data in Tinder bios, profiles, and post content, and on the chosen `country`/keyword targeting. *** ### ❓ FAQ #### Does Tinder Phone Number Scraper require coding? ✅ No. You can provide your settings in the Apify Console via the input form or an `input.json` file, then review results in the dataset output. #### What phone numbers does it extract? ✅ It extracts phone numbers from Tinder bios, profiles, and post content, based on your provided `keywords` and selected `country` targeting. #### What happens if I set `maxPhoneNumbers`? ✅ The actor stops once it finds enough unique phone numbers to meet your `maxPhoneNumbers` limit. This is useful when you want a fixed-size lead batch (common in **Tinder leads phone number extractor** use cases). #### Can I filter by a specific location? ✅ Yes. You can set `location` to narrow targeting (example values like “London” or “California”). Leave it empty to search more broadly. #### What do the output fields mean? ✅ Each dataset item includes `phone_number` (in E.164 format), plus context like `url`, `keyword`, `country`, and `dial_code` so you can interpret and export the results cleanly. #### Is it okay to collect results for lead generation? ✅ The actor is designed to work with publicly available web data. You should ensure your use complies with applicable laws, privacy requirements, and platform rules for outreach and messaging. #### How can I request help or custom improvements? ✅ For support or custom scraping needs, contact . #### How do I remove scraped data? ✅ For data removal requests, email . *** ### 🤝 Support & feature requests Want to improve your **Tinder phone number scraper** results or propose enhancements? 💡 **Feature Requests**: Examples include additional export formats, stronger filtering options, or workflow improvements for **Tinder contact info extraction tool** users.\ 📧 **Contact**: Reach out via . Your feedback helps shape the roadmap for this Tinder phone number list and phone contact extraction tool. *** ### *Tinder Phone Number Scraper* — final thoughts *If you’re looking for the most comprehensive and SEO-optimized Tinder phone number scraper experience, start with clear keywords and the right country targeting.* *You’ll quickly get structured phone number results ready for analysis, enrichment, and outreach at scale.* *** ### Disclaimer **This tool only accesses publicly accessible sources.** It does not access private profiles, authenticated data, or password-protected pages. You are responsible for complying with applicable laws and regulations (including GDPR/CCPA where relevant), as well as respecting platform terms and anti-spam rules. Use responsibly, ethically, and for legitimate purposes. For data removal requests, contact . # Actor input Schema ## `keywords` (type: `array`): Enter keywords to search for (e.g., 'Target Keyword'). ## `location` (type: `string`): Filter by location (e.g., 'London', 'California'). Leave empty for global search. ## `country` (type: `string`): Select the country to target for phone numbers. ## `maxPhoneNumbers` (type: `integer`): Stop scraping after this many phone numbers are found. Setting a higher limit extends the scraping duration. ## Actor input object example ```json { "keywords": [ "marketing", "founder" ], "country": "United Kingdom (+44)", "maxPhoneNumbers": 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 = { "keywords": [ "marketing", "founder" ] }; // Run the Actor and wait for it to finish const run = await client.actor("solid-scraper/tinder-phone-number-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 = { "keywords": [ "marketing", "founder", ] } # Run the Actor and wait for it to finish run = client.actor("solid-scraper/tinder-phone-number-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 '{ "keywords": [ "marketing", "founder" ] }' | apify call solid-scraper/tinder-phone-number-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=solid-scraper/tinder-phone-number-scraper", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "Tinder Phone Number Scraper", "description": "📱 Tinder Phone Number Scraper helps you extract verified phone contacts from profiles for targeted outreach. Ideal for marketers, recruiters, and agencies—faster prospecting, cleaner lists, better conversions. 🚀", "version": "0.1", "x-build-id": "WBxWaEdbQq76siOhw" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/solid-scraper~tinder-phone-number-scraper/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-solid-scraper-tinder-phone-number-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/solid-scraper~tinder-phone-number-scraper/runs": { "post": { "operationId": "runs-sync-solid-scraper-tinder-phone-number-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/solid-scraper~tinder-phone-number-scraper/run-sync": { "post": { "operationId": "run-sync-solid-scraper-tinder-phone-number-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": [ "keywords", "country" ], "properties": { "keywords": { "title": "Keywords", "type": "array", "description": "Enter keywords to search for (e.g., 'Target Keyword').", "default": [ "marketing", "founder" ], "items": { "type": "string" } }, "location": { "title": "Location", "type": "string", "description": "Filter by location (e.g., 'London', 'California'). Leave empty for global search." }, "country": { "title": "Country", "enum": [ "Afghanistan (+93)", "Albania (+355)", "Algeria (+213)", "Andorra (+376)", "Angola (+244)", "Antigua And Barbuda (+1-268)", "Argentina (+54)", "Armenia (+374)", "Australia (+61)", "Austria (+43)", "Azerbaijan (+994)", "Bahamas (+1-242)", "Bahrain (+973)", "Bangladesh (+880)", "Barbados (+1-246)", "Belarus (+375)", "Belgium (+32)", "Belize (+501)", "Benin (+229)", "Bhutan (+975)", "Bolivia (+591)", "Bosnia And Herzegovina (+387)", "Botswana (+267)", "Brazil (+55)", "Brunei (+673)", "Bulgaria (+359)", "Burkina Faso (+226)", "Burundi (+257)", "Cambodia (+855)", "Cameroon (+237)", "Canada (+1)", "Cape Verde (+238)", "Central African Republic (+236)", "Chad (+235)", "Chile (+56)", "China (+86)", "Colombia (+57)", "Comoros (+269)", "Congo (Democratic Republic) (+243)", "Congo (Republic) (+242)", "Costa Rica (+506)", "Croatia (+385)", "Cuba (+53)", "Cyprus (+357)", "Czech Republic (+420)", "Denmark (+45)", "Djibouti (+253)", "Dominica (+1-767)", "Dominican Republic (+1-809)", "East Timor (+670)", "Ecuador (+593)", "Egypt (+20)", "El Salvador (+503)", "Equatorial Guinea (+240)", "Eritrea (+291)", "Estonia (+372)", "Eswatini (+268)", "Ethiopia (+251)", "Fiji (+679)", "Finland (+358)", "France (+33)", "Gabon (+241)", "Gambia (+220)", "Georgia (+995)", "Germany (+49)", "Ghana (+233)", "Greece (+30)", "Grenada (+1-473)", "Guatemala (+502)", "Guinea (+224)", "Guinea-Bissau (+245)", "Guyana (+592)", "Haiti (+509)", "Honduras (+504)", "Hungary (+36)", "Iceland (+354)", "India (+91)", "Indonesia (+62)", "Iran (+98)", "Iraq (+964)", "Ireland (+353)", "Israel (+972)", "Italy (+39)", "Jamaica (+1-876)", "Japan (+81)", "Jordan (+962)", "Kazakhstan (+7)", "Kenya (+254)", "Kiribati (+686)", "Korea, North (+850)", "Korea, South (+82)", "Kuwait (+965)", "Kyrgyzstan (+996)", "Laos (+856)", "Latvia (+371)", "Lebanon (+961)", "Lesotho (+266)", "Liberia (+231)", "Libya (+218)", "Liechtenstein (+423)", "Lithuania (+370)", "Luxembourg (+352)", "Madagascar (+261)", "Malawi (+265)", "Malaysia (+60)", "Maldives (+960)", "Mali (+223)", "Malta (+356)", "Marshall Islands (+692)", "Mauritania (+222)", "Mauritius (+230)", "Mexico (+52)", "Micronesia (+691)", "Moldova (+373)", "Monaco (+377)", "Mongolia (+976)", "Montenegro (+382)", "Morocco (+212)", "Mozambique (+258)", "Myanmar (+95)", "Namibia (+264)", "Nauru (+674)", "Nepal (+977)", "Netherlands (+31)", "New Zealand (+64)", "Nicaragua (+505)", "Niger (+227)", "Nigeria (+234)", "North Macedonia (+389)", "Norway (+47)", "Oman (+968)", "Pakistan (+92)", "Palau (+680)", "Panama (+507)", "Papua New Guinea (+675)", "Paraguay (+595)", "Peru (+51)", "Philippines (+63)", "Poland (+48)", "Portugal (+351)", "Qatar (+974)", "Romania (+40)", "Russia (+7)", "Rwanda (+250)", "Saint Kitts And Nevis (+1-869)", "Saint Lucia (+1-758)", "Saint Vincent And The Grenadines (+1-784)", "Samoa (+685)", "San Marino (+378)", "Sao Tome And Principe (+239)", "Saudi Arabia (+966)", "Senegal (+221)", "Serbia (+381)", "Seychelles (+248)", "Sierra Leone (+232)", "Singapore (+65)", "Slovakia (+421)", "Slovenia (+386)", "Solomon Islands (+677)", "Somalia (+252)", "South Africa (+27)", "South Sudan (+211)", "Spain (+34)", "Sri Lanka (+94)", "Sudan (+249)", "Suriname (+597)", "Sweden (+46)", "Switzerland (+41)", "Syria (+963)", "Taiwan (+886)", "Tajikistan (+992)", "Tanzania (+255)", "Thailand (+66)", "Togo (+228)", "Tonga (+676)", "Trinidad And Tobago (+1-868)", "Tunisia (+216)", "Turkey (+90)", "Turkmenistan (+993)", "Tuvalu (+688)", "Uganda (+256)", "Ukraine (+380)", "United Arab Emirates (+971)", "United Kingdom (+44)", "United States (+1)", "Uruguay (+598)", "Uzbekistan (+998)", "Vanuatu (+678)", "Vatican City (+39-06)", "Venezuela (+58)", "Vietnam (+84)", "Yemen (+967)", "Zambia (+260)", "Zimbabwe (+263)" ], "type": "string", "description": "Select the country to target for phone numbers.", "default": "United Kingdom (+44)" }, "maxPhoneNumbers": { "title": "Max Phone Numbers", "minimum": 1, "maximum": 10000, "type": "integer", "description": "Stop scraping after this many phone numbers are found. Setting a higher limit extends the scraping duration.", "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 } } } } } } } } } } ```