# Meta Threads Scraper - Posts, Reply Trees, Bio Contacts (`constructive_calm/threads-scraper`) Actor Scrape Threads posts, profiles, hashtags & search with FULL recursive reply trees + bio email/phone extraction + monitoring mode. Beats incumbents on reply depth & outreach contact extraction. - **URL**: https://apify.com/constructive\_calm/threads-scraper.md - **Developed by:** [Omar Eldeeb](https://apify.com/constructive_calm) (community) - **Categories:** Social media, SEO tools, Lead generation - **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 2 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 ## Meta Threads Scraper โ€” Posts, Profiles, Discussion Trees, Bio Contacts Scrape Meta Threads (threads.com) public posts, profiles, search results, hashtag feeds, and full discussion trees โ€” with optional bio email/phone extraction and Linktree resolution. Designed for social-listening agencies, growth marketers, lead-gen, and brand-monitoring teams. **No login. No cookies. No GraphQL doc_id maintenance.** Pure SSR HTML extraction via Meta's public crawler-friendly endpoint. --- ### What this Actor does - ๐Ÿ“ฅ **Profiles** โ€” scrape any active public Threads profile (followers, bio, bio links, profile pic, verification, post count, public views) - ๐Ÿ“ฐ **Posts by user** โ€” fetch the most recent posts of any user with full engagement (likes, replies, reposts, quotes, media URLs, timestamps) - ๐ŸŒณ **Discussion trees** โ€” for any post URL, return the source post plus all public quote-reposts and discussion posts that reference it - ๐Ÿ” **Search** โ€” pull the top results for any keyword - #๏ธโƒฃ **Hashtag feed** โ€” pull top posts for any tag - ๐Ÿ“ก **Monitor** โ€” re-run any user list and emit only new posts since the last run (KV-backed watermark) - ๐Ÿ“ž **Premium: bio contact extraction** โ€” parse emails + phones from biography text + bio links, optionally resolve Linktree / Beacons / Stan / Bio.link aggregator pages into full contact lists - ๐Ÿ” **Concurrent + retry-aware** โ€” runs N usernames/URLs in parallel with timeouts and graceful per-target error handling --- ### Why use this Actor - **No anti-bot war.** No Cloudflare, no Akamai, no JavaScript challenge. Most existing Threads scrapers chase Meta's GraphQL `doc_id` rotations every few weeks โ€” this Actor doesn't, so it doesn't break. - **Bio contact extraction** as a first-class feature. Other Threads actors give you raw text; this one parses emails, phones, and resolves Linktree-style aggregators for cold outreach lead-gen. - **Discussion trees in one fetch.** Get the source post + everyone publicly quoting/responding to it โ€” perfect for influence tracking and competitive monitoring. - **Monitor mode is real incremental.** Most "scheduled" actors burn compute re-scraping the same 500 posts; this one stores a per-user watermark so you only pay for *new* posts. #### Buyer fit | Persona | Use case | |---|---| | Social-listening agency | Track brand mentions, competitor activity, sentiment across Threads | | Growth / SDR team | Pull bio contacts for cold outreach (creators, founders, brand owners) | | Brand-monitoring lead | Daily monitor mode: alert on negative posts about your brand | | ASO / mobile growth | Track creator+app mentions in hashtag feeds | | Researcher / journalist | Discovery via search; archive a public post's discussion tree | --- ### How to use 1. Pick a **mode** (most users start with `posts_by_user`) 2. Enter usernames, post URLs, search query, or hashtag depending on the mode 3. (Optional) Enable **extractBioContacts** for outreach-grade contact data (premium event) 4. Run โ€” first **50 chargeable events are free** every run You can schedule the actor in monitor mode for daily delta detection (your watermark persists between runs in the actor's Key-Value Store). --- ### Input examples #### 1) Pull recent posts from a list of users (most common) ```json { "mode": "posts_by_user", "usernames": ["zuck", "mosseri", "instagram"], "maxPostsPerUser": 25 } ```` #### 2) Profile + bio contact extraction for outreach ```json { "mode": "profile", "usernames": ["someinfluencer", "anotherbrand", "thirdcreator"], "extractBioContacts": true, "resolveLinktree": true } ``` #### 3) Discussion tree for a single post ```json { "mode": "post_detail", "postUrls": ["https://www.threads.com/@zuck/post/DXt5n9UlLl-"], "expandReplies": true, "maxReplyDepth": 3, "maxRepliesPerNode": 20 } ``` #### 4) Search keyword feed ```json { "mode": "search", "searchQuery": "vibe coding" } ``` #### 5) Hashtag feed ```json { "mode": "hashtag", "hashtag": "ai" } ``` #### 6) Monitor: emit only new posts since last run ```json { "mode": "monitor", "usernames": ["yourcompetitor", "anothercompetitor"], "maxPostsPerUser": 50 } ``` *** ### Output The dataset is a mix of `recordType: "profile"` and `recordType: "post"` (or `"reply"`) rows. #### Profile row ```json { "recordType": "profile", "username": "zuck", "userId": "63055343223", "fullName": "Mark Zuckerberg", "biography": "Mostly superintelligence and MMA takes", "followerCount": 5464936, "isVerified": true, "profilePicUrl": "https://instagram.fatz1-1.fna.fbcdn.net/...", "bioLinks": [{"url": "https://meta.com", "title": "Meta", "linkType": "external"}], "extractedEmails": ["press@meta.com"], "extractedPhones": [], "publicViews": null, "fetchedAt": "2026-05-08T12:00:00.000Z", "sourceUrl": "https://www.threads.com/@zuck" } ``` #### Post row ```json { "recordType": "post", "postId": "3886015488044874110", "code": "DXt5n9UlLl-", "url": "https://www.threads.com/@zuck/post/DXt5n9UlLl-", "username": "zuck", "userId": "63055343223", "fullName": "Mark Zuckerberg", "text": "As part of our philanthropic work to help cure all diseases...", "takenAt": "2026-04-25T08:46:07.000Z", "likeCount": 1443, "replyCount": 350, "repostCount": 111, "quoteCount": 9, "mediaUrls": [], "mediaType": "text", "parentPostId": null, "depth": 0, "fetchedAt": "2026-05-08T12:00:00.000Z", "sourceUrl": "https://www.threads.com/@zuck" } ``` #### Field reference | Field | Type | Notes | |---|---|---| | `recordType` | string | `profile` / `post` / `reply` | | `username` | string | Without `@` | | `userId` (`pk`) | string | Stable Meta numeric id | | `followerCount` | number | Profile only | | `bioLinks` | array | URL, title, link\_type | | `extractedEmails` / `extractedPhones` | string\[] | Only when `extractBioContacts: true` | | `text` | string | Caption text (post) | | `takenAt` | ISO datetime | Converted from unix | | `likeCount` / `replyCount` / `repostCount` / `quoteCount` | number | Engagement | | `mediaUrls` | string\[] | Image / carousel / video best-resolution URL(s) | | `mediaType` | enum | `text` / `image` / `carousel` / `video` | | `parentPostId` | string | null | Set on `reply` rows | | `depth` | number | 0 for root posts; >0 for replies in a discussion tree | *** ### Pricing โ€” pay-per-event You only pay for what you get. **First 50 chargeable events per run are free.** | Event | Price | Fires when | |---|---|---| | `profile-fetched` | $0.005 | One profile row emitted | | `post-fetched` | $0.0035 | One post row emitted | | `reply-fetched` | $0.0015 | One reply / discussion-tree row emitted | | `bio-contact-resolved` | $0.020 | Bio extraction + Linktree resolution ran (premium) | | `monitor-delta-detected` | $0.010 | New post discovered in monitor mode | Apify auto-charges `apify-actor-start` per platform billing on top of these. #### Typical run cost | Scenario | Volume | Approx cost | |---|---|---| | 1 profile + 25 posts | 1 + 25 events | $0.005 + (25 ร— $0.0035) = **~$0.09** | | 10 profiles + 25 posts each | 10 + 250 | $0.05 + $0.875 = **~$0.93** | | 50 search results | 50 | **~$0.18** | | 1 post + ~30 discussion posts | 1 + 30 | $0.0035 + (30 ร— $0.0015) = **~$0.05** | | Daily monitor of 100 brands (5 new posts/day on average) | 500 deltas | **~$5.00 / day** | | 100 outreach profiles w/ contact extraction | 100 + 100 | $0.50 + $2.00 = **~$2.50** | Compare against ZoomInfo + Bombora ($3,000+/month), Apollo Pro ($99+/seat), or building this in-house. *** ### Tips & gotchas - **Some profiles return a "Threads ยท Log in" gate.** Meta privacy-gates a fraction (~15%) of accounts from public crawling, even with social-bot UA. The actor logs a clear warning when this happens and skips the row. Most active accounts work fine. - **Posts per profile are limited to ~7-25 per fetch** in v1 (whatever Threads renders in the SSR HTML). Pagination beyond that requires a logged-in session and is out of scope. - **Discussion tree, not reply tree.** A post-detail fetch returns the source post + ~15-30 quote-reposts, parody/copycat posts, and discussion posts that reference it. The full nested reply chain (clickable inside the Threads app) lives behind a logged-in XHR endpoint and is not surfaced. - **Bio contact extraction is best-effort.** Emails parsed are valid-format, lowercased, deduped. Phone numbers are loosely matched on digit count + structure. Linktree-style aggregator pages are fetched only when `resolveLinktree: true`. - **Concurrency.** Default 4 parallel fetches. Bump to 8-10 if you provide an Apify residential proxy. Tested at 27 fetches/min sustained without proxy with no rate-limiting. - **Monitor mode** stores per-user watermarks under `monitor_watermarks_v1` in your run's Key-Value Store. Delete this key to reset. *** ### FAQ **Do I need to log in or provide cookies?** No. The actor uses Meta's crawler-friendly SSR endpoint (the same path Facebook / Twitter / Slack use for link previews). **Will Meta block my actor?** We've sustained 27+ fetches/min without rate-limiting in scale tests. Apify's residential proxy is supported but optional for moderate volume. Use it for runs >500 fetches. **Can I scrape DMs / private accounts / followers list?** No. This is a public-only scraper. Private profiles, follower lists, and DMs are not exposed in the public SSR HTML. **Why aren't all 350 replies on a post showing up?** The full reply tree requires a logged-in session. The discussion-tree mode returns the ~15-30 publicly-indexed posts that reference or quote the source post โ€” which is often the higher-signal data anyway (who's talking *about* this post). **Is this allowed by Threads' Terms of Service?** Meta's TOS forbids automated collection without permission as a blanket policy, similar to Instagram. Public-data scraping case law (hiQ v LinkedIn 2022; Meta v Bright Data 2024) generally protects logged-out scraping. Use this actor responsibly: don't store sessionid cookies, don't access logged-in content, comply with applicable privacy law in your jurisdiction. **You are responsible for your use.** *** ### Roadmap (post-v1) - Pagination beyond first SSR page (cursor-based, may require proxy) - Comment-thread resolution behind a logged-in BYO-cookie path (premium) - AI sentiment + intent classification on posts (Gemini Flash) - Engagement velocity (ฮ”-likes / ฮ”-replies between runs) - Weekly trend digest CSV export Built by **constructive\_calm**. Questions or feature requests: open an issue on the Apify Store listing. # Actor input Schema ## `mode` (type: `string`): Pick the scrape mode. Posts-by-user is the most common starting point. ## `usernames` (type: `array`): Threads usernames without the @. Used by profile, posts\_by\_user, monitor modes. ## `postUrls` (type: `array`): Full Threads post URLs. Used by post\_detail mode. Example: https://www.threads.com/@zuck/post/Cabc123 ## `searchQuery` (type: `string`): Keyword to search across Threads. Used by search mode. ## `hashtag` (type: `string`): Tag without the #. Used by hashtag mode. ## `maxPostsPerUser` (type: `integer`): Cap the number of posts returned per user. The Threads SSR HTML typically renders 7โ€“25 most-recent posts. ## `expandReplies` (type: `boolean`): When on, post\_detail mode returns all quote-reposts and discussion posts that reference the source post. ## `maxReplyDepth` (type: `integer`): How deep to follow nested reply chains, when present. 0 = source post only. ## `maxRepliesPerNode` (type: `integer`): Cap on how many replies/discussion posts to keep per parent. Top N by like count. ## `extractBioContacts` (type: `boolean`): Pull email + phone from author bio + resolve Linktree URLs into actual contacts. Charged per resolved profile. ## `resolveLinktree` (type: `boolean`): Follow bio links to Linktree / Beacons / Stan / Carrd to extract additional contact channels. Requires extractBioContacts=true. ## `incrementalMode` (type: `boolean`): Skip posts older than the last run's watermark (KV-store). ## `maxItems` (type: `integer`): Hard cap on dataset rows for this run (across all targets). ## `concurrency` (type: `integer`): Parallel fetches across input targets. Bump to 8-10 if using Apify residential proxy. ## `proxyConfiguration` (type: `object`): Residential proxy is recommended for runs >500 fetches. Datacenter works fine for tiny runs. ## Actor input object example ```json { "mode": "posts_by_user", "usernames": [ "zuck" ], "maxPostsPerUser": 25, "expandReplies": true, "maxReplyDepth": 3, "maxRepliesPerNode": 20, "extractBioContacts": false, "resolveLinktree": false, "incrementalMode": false, "maxItems": 500, "concurrency": 4, "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ] } } ``` # Actor output Schema ## `results` (type: `string`): All extracted profiles, posts, and replies in one dataset. # 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 = { "usernames": [ "zuck" ] }; // Run the Actor and wait for it to finish const run = await client.actor("constructive_calm/threads-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 = { "usernames": ["zuck"] } # Run the Actor and wait for it to finish run = client.actor("constructive_calm/threads-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 '{ "usernames": [ "zuck" ] }' | apify call constructive_calm/threads-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=constructive_calm/threads-scraper", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "Meta Threads Scraper - Posts, Reply Trees, Bio Contacts", "description": "Scrape Threads posts, profiles, hashtags & search with FULL recursive reply trees + bio email/phone extraction + monitoring mode. Beats incumbents on reply depth & outreach contact extraction.", "version": "0.1", "x-build-id": "1cSey0aq03fajFcUa" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/constructive_calm~threads-scraper/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-constructive_calm-threads-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/constructive_calm~threads-scraper/runs": { "post": { "operationId": "runs-sync-constructive_calm-threads-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/constructive_calm~threads-scraper/run-sync": { "post": { "operationId": "run-sync-constructive_calm-threads-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": [ "mode" ], "properties": { "mode": { "title": "What to scrape", "enum": [ "profile", "posts_by_user", "post_detail", "search", "hashtag", "monitor" ], "type": "string", "description": "Pick the scrape mode. Posts-by-user is the most common starting point.", "default": "posts_by_user" }, "usernames": { "title": "Usernames", "type": "array", "description": "Threads usernames without the @. Used by profile, posts_by_user, monitor modes.", "items": { "type": "string" } }, "postUrls": { "title": "Post URLs", "type": "array", "description": "Full Threads post URLs. Used by post_detail mode. Example: https://www.threads.com/@zuck/post/Cabc123", "items": { "type": "string" } }, "searchQuery": { "title": "Search query", "type": "string", "description": "Keyword to search across Threads. Used by search mode." }, "hashtag": { "title": "Hashtag", "type": "string", "description": "Tag without the #. Used by hashtag mode." }, "maxPostsPerUser": { "title": "Max posts per user", "minimum": 1, "maximum": 500, "type": "integer", "description": "Cap the number of posts returned per user. The Threads SSR HTML typically renders 7โ€“25 most-recent posts.", "default": 25 }, "expandReplies": { "title": "Expand discussion tree", "type": "boolean", "description": "When on, post_detail mode returns all quote-reposts and discussion posts that reference the source post.", "default": true }, "maxReplyDepth": { "title": "Max discussion-tree depth", "minimum": 0, "maximum": 10, "type": "integer", "description": "How deep to follow nested reply chains, when present. 0 = source post only.", "default": 3 }, "maxRepliesPerNode": { "title": "Max replies per node", "minimum": 1, "maximum": 200, "type": "integer", "description": "Cap on how many replies/discussion posts to keep per parent. Top N by like count.", "default": 20 }, "extractBioContacts": { "title": "Extract bio contacts (premium)", "type": "boolean", "description": "Pull email + phone from author bio + resolve Linktree URLs into actual contacts. Charged per resolved profile.", "default": false }, "resolveLinktree": { "title": "Resolve Linktree / aggregator links", "type": "boolean", "description": "Follow bio links to Linktree / Beacons / Stan / Carrd to extract additional contact channels. Requires extractBioContacts=true.", "default": false }, "incrementalMode": { "title": "Incremental mode", "type": "boolean", "description": "Skip posts older than the last run's watermark (KV-store).", "default": false }, "maxItems": { "title": "Max items", "minimum": 1, "maximum": 50000, "type": "integer", "description": "Hard cap on dataset rows for this run (across all targets).", "default": 500 }, "concurrency": { "title": "Concurrent requests", "minimum": 1, "maximum": 20, "type": "integer", "description": "Parallel fetches across input targets. Bump to 8-10 if using Apify residential proxy.", "default": 4 }, "proxyConfiguration": { "title": "Proxy", "type": "object", "description": "Residential proxy is recommended for runs >500 fetches. Datacenter works fine for tiny runs.", "default": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ] } } } }, "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 } } } } } } } } } } ```