# Poland KRZ National Debtor Registry Scraper (`maximedupre/poland-krz-debtor-registry-scraper`) Actor Search Poland’s public KRZ for companies, people, cases, proceedings, announcements, partners, estate assets, and restructuring advisors. Export available identifiers, statuses, dates, court details, and official source links. - **URL**: https://apify.com/maximedupre/poland-krz-debtor-registry-scraper.md - **Developed by:** [Maxime Dupré](https://apify.com/maximedupre) (community) - **Categories:** Business, Automation, Developer tools - **Stats:** 2 total users, 1 monthly users, 50.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $2.70 / 1,000 public registry matches This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. 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 ### 🔎 Search Poland’s public KRZ with structured output For compliance teams, legal researchers, finance teams, and developers, Poland KRZ Registry searches the public **Krajowy Rejestr Zadłużonych (KRZ)** and returns available names, identifiers, proceedings, statuses, courts, dates, announcements, estate assets, advisor contacts, and official source links. Screen a list of the same kind of subject or retrieve a specific case-related entry without supplying a KRZ account, cookie, or API key. - Run a **[KRZ company search](https://apify.com/maximedupre/poland-krz-debtor-registry-scraper/examples/krz-company-search)** by name, KRS, NIP, or REGON for counterparty screening. - Perform a **[KRZ person lookup](https://apify.com/maximedupre/poland-krz-debtor-registry-scraper/examples/krz-person-lookup)** by PESEL or NIP while keeping submitted PESEL values out of output. - Complete a **[Poland debtor registry check](https://apify.com/maximedupre/poland-krz-debtor-registry-scraper/examples/poland-debtor-registry-check)** for sole traders by name, NIP, REGON, or PESEL. - Use **[KRZ court case search](https://apify.com/maximedupre/poland-krz-debtor-registry-scraper/examples/krz-court-case-search)** to find public case context from a complete case signature. - Run a **[KRZ proceeding lookup](https://apify.com/maximedupre/poland-krz-debtor-registry-scraper/examples/krz-proceeding-lookup)** by an exact proceeding identifier. - Perform a **[KRZ court announcements search](https://apify.com/maximedupre/poland-krz-debtor-registry-scraper/examples/krz-court-announcements-search)** by date range, case signature, or proceeding identifier. - Run a **[KRZ company partner search](https://apify.com/maximedupre/poland-krz-debtor-registry-scraper/examples/krz-company-partner-search)** by personal-company name, KRS, NIP, or REGON. - Use a **[bankruptcy estate asset search](https://apify.com/maximedupre/poland-krz-debtor-registry-scraper/examples/bankruptcy-estate-asset-search)** to retrieve public inventory status, asset descriptions, and valuations. - Run a **[restructuring advisor search](https://apify.com/maximedupre/poland-krz-debtor-registry-scraper/examples/restructuring-advisor-search)** by name, licence number, or city. #### 📦 Data returned Choose one Target per run. Depending on that Target, each successful match can include: - registered names and available KRS, NIP, or REGON identifiers; - proceeding ID, case signature, type, status, role, court, and opening or closing dates; - proceeding summaries attached to matched companies, people, and sole traders; - announcement ID, date, title, content, case context, and court; - company and partner names, identifiers, partner type, and role; - estate inventory status plus asset category, description, quantity, valuation, currency, and status; - advisor name, licence number, city, address, phone, and email; - `checkNumber`, `queryComplete`, `rowType`, and `sourceUrl` on every row. `queryComplete: false` means KRZ capped the source query or the requested advisor limit was reached before all source matches were delivered. Do not treat it as a complete absence check. For estate inventories, `confirmedAbsent` means the public registry positively reported no inventory; retrieval failures are not reported this way. A PESEL supplied for a check is never included in dataset rows or public logs. #### ▶️ Running the Actor 1. Choose one **Target**. 2. Fill in the criteria shown for that Target. 3. Set **Maximum results per check** to bound delivered matches and cost. 4. Start the Actor and open the default dataset. A run can process multiple checks of the same kind. Run separately configured registry areas in separate runs. Public KRZ coverage begins on **1 December 2021**. #### ⚙️ Input The Target determines which fields are used: - `companies`: `companyQueries` - `persons`: `personQueries` - `soleTraders`: `traderQueries` - `courtCases`: `caseSignatures` - `proceedings`: `proceedingIds` - `announcements`: `announcementFrom`, `announcementTo`, optional `announcementQueries`, `announcementCaseSignatures`, and `announcementProceedingIds` - `partners`: `partnerCompanies` - `estateAssets`: `assetSubjects`, `assetProceedingIds`, `assetCaseSignatures`, and optional `assetType` - `advisors`: `advisorQueries` and optional `advisorCity` `maxResults` applies per submitted check or announcement search. Inputs belonging to inactive Targets are ignored. Example company input: ```json { "target": "companies", "companyQueries": ["ORLEN", "KRS:0000304735"], "maxResults": 25 } ```` Natural-person criteria must be an 11-digit value prefixed with `PESEL:` or a 10-digit value prefixed with `NIP:`. Names are not supported for that Target. #### 🧾 Output Successful matches are written to the default dataset. The exact row shape depends on `rowType`. A company row can look like this: ```json { "rowType": "company", "checkNumber": 1, "queryComplete": true, "name": "Example Sp. z o.o.", "nip": "5250001009", "krs": "0000123456", "regon": "012345678", "proceedings": [ { "proceedingId": "example-proceeding-id", "caseSignature": "WA1M/GUp/12/2024", "status": "open", "court": "District Court in Warsaw", "openingDate": "2024-05-10" } ], "sourceUrl": "https://krz.ms.gov.pl/" } ``` This is an illustrative schema-conforming example, not a statement about a real company. Empty checks and failures do not create dataset rows. Export saved rows through Apify as JSON, CSV, Excel, XML, RSS, or HTML. #### 💳 Pricing The Actor uses pay-per-event pricing. You are charged once for each successful final public KRZ match delivered to the default dataset. Empty checks, retries, failures, and internal detail requests are not charged as matches. Use `maxResults` to bound the number of delivered matches for each check. #### 🔌 Integrations Run the Actor through the Apify API, schedule repeat runs, or send dataset output to another system with webhooks and Apify integrations. Scheduling does not turn the Actor into a watchlist or change detector; compare outputs in your own workflow when you need change monitoring. https://www.youtube.com/watch?v=bNACk1\_S\_6w\&list=PLObrtcm1Kw6MUrlLNDbK9QRg8VDJg0gOW\&index=4 #### ❓ FAQ ##### Can I search a natural person by name? No. The public person Target requires either an 11-digit PESEL or a 10-digit NIP. The identifier is used for the source request; submitted PESEL values are not exported. ##### Does a zero-row run prove that a subject has no debt? No. It means the completed search in the selected public KRZ area returned no match. It is not a credit score, solvency conclusion, KYC/AML decision, or legal advice. ##### What does an incomplete query mean? A false `queryComplete` value means a source or requested limit was reached before the Actor could represent the search as complete. Narrow the search criteria or review a higher result limit where appropriate. ##### Does it access all Polish debtor history? No. The Actor covers the public KRZ period beginning 1 December 2021. It does not add earlier history or data from private debtor databases. ##### Do I need KRZ credentials? No user-supplied credentials are required. The Actor accesses only public KRZ material and does not retrieve authenticated or private content. ##### Can one run search several registry areas? No. Choose one Target per run. You can submit multiple same-kind checks in that run, then launch separate runs for other Targets. ##### Can the Actor monitor subjects or provide alerts? It does not maintain watchlists or detect changes. Use Apify schedules, webhooks, and your own comparison logic around separate runs. ### 📝 Changelog - 0.1: Initial release. ### 🆘 Support For issues, questions, or feature requests, [file a ticket](https://console.apify.com/actors/maximedupre~poland-krz-debtor-registry-scraper/issues) and I'll fix or implement it in less than 24h 🫡 ### 🔗 Related Actors - [GLEIF LEI Lookup](https://apify.com/maximedupre/gleif-lei-lookup) — enrich counterparties with public Legal Entity Identifier, registration, address, and parent relationship data. - [Pappers Sirene Scraper](https://apify.com/maximedupre/pappers-sirene-scraper) — search and enrich French companies with SIREN/SIRET identifiers and official registry data. **Made with ❤️ by Maxime Dupré** # Actor input Schema ## `target` (type: `string`): Choose the KRZ source surface and result family. Run differently configured searches separately. ## `companyQueries` (type: `array`): Enter one check per line: a full or partial company name of at least 3 characters, or an identifier prefixed with KRS:, NIP:, or REGON:. ## `personQueries` (type: `array`): Enter one public natural-person check per line as PESEL: followed by 11 digits or NIP: followed by 10 digits. KRZ does not provide public person-name search. Submitted PESEL values are used only for checks and are never exported. ## `traderQueries` (type: `array`): Enter one check per line: a full or partial business or person name of at least 3 characters, or an identifier prefixed with NIP:, REGON:, or PESEL:. PESEL is used only for the check and is not exported. ## `caseSignatures` (type: `array`): Enter one complete court case signature per line, in the form shown by KRZ. ## `proceedingIds` (type: `array`): Enter one exact KRZ proceeding identifier per line. ## `announcementFrom` (type: `string`): Earliest announcement date to include, in YYYY-MM-DD form. ## `announcementTo` (type: `string`): Latest announcement date to include, in YYYY-MM-DD form. ## `announcementQueries` (type: `array`): Optionally enter one subject name or exact announcement identifier per line. Prefix an identifier with ID:. ## `announcementCaseSignatures` (type: `array`): Optionally enter one complete court case signature per line. ## `announcementProceedingIds` (type: `array`): Optionally enter one exact KRZ proceeding identifier per line. ## `partnerCompanies` (type: `array`): Enter one check per line: a full or partial personal-company name of at least 3 characters, or an identifier prefixed with KRS:, NIP:, or REGON:. ## `assetSubjects` (type: `array`): Enter one debtor or estate subject per line as a full or partial name of at least 3 characters, or an identifier prefixed with KRS:, NIP:, REGON:, or PESEL:. Submitted PESEL values are never exported. You can instead provide proceeding context below. ## `assetProceedingIds` (type: `array`): Enter one exact KRZ proceeding identifier per line. You can instead provide subjects above or case signatures below. ## `assetCaseSignatures` (type: `array`): Enter one complete court case signature per line when a subject or proceeding identifier is unavailable. ## `assetType` (type: `string`): Optionally restrict assets to a registry category or type. ## `advisorQueries` (type: `array`): Enter one check per line: a full or partial advisor name of at least 3 characters, or a licence number prefixed with LICENCE:. ## `advisorCity` (type: `string`): Optionally search for advisors in a listed city, either alone or with the checks above. ## `maxResults` (type: `integer`): Stop each submitted check or announcement search after this many matches. If KRZ caps a broader query first, the output reports that the check is incomplete. ## Actor input object example ```json { "target": "companies", "companyQueries": [ "ABC" ], "maxResults": 5 } ``` # Actor output Schema ## `results` (type: `string`): Open successful public KRZ matches in the default dataset overview. # 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 = { "target": "companies", "companyQueries": [ "ABC" ], "maxResults": 5 }; // Run the Actor and wait for it to finish const run = await client.actor("maximedupre/poland-krz-debtor-registry-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 = { "target": "companies", "companyQueries": ["ABC"], "maxResults": 5, } # Run the Actor and wait for it to finish run = client.actor("maximedupre/poland-krz-debtor-registry-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 '{ "target": "companies", "companyQueries": [ "ABC" ], "maxResults": 5 }' | apify call maximedupre/poland-krz-debtor-registry-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=maximedupre/poland-krz-debtor-registry-scraper", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "Poland KRZ National Debtor Registry Scraper", "description": "Search Poland’s public KRZ for companies, people, cases, proceedings, announcements, partners, estate assets, and restructuring advisors. Export available identifiers, statuses, dates, court details, and official source links.", "version": "0.1", "x-build-id": "S9ubfEtQRMyaremXZ" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/maximedupre~poland-krz-debtor-registry-scraper/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-maximedupre-poland-krz-debtor-registry-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/maximedupre~poland-krz-debtor-registry-scraper/runs": { "post": { "operationId": "runs-sync-maximedupre-poland-krz-debtor-registry-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/maximedupre~poland-krz-debtor-registry-scraper/run-sync": { "post": { "operationId": "run-sync-maximedupre-poland-krz-debtor-registry-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": [ "target" ], "properties": { "target": { "title": "Target", "enum": [ "companies", "persons", "soleTraders", "courtCases", "proceedings", "announcements", "partners", "estateAssets", "advisors" ], "type": "string", "description": "Choose the KRZ source surface and result family. Run differently configured searches separately.", "default": "companies" }, "companyQueries": { "title": "Companies or identifiers", "type": "array", "description": "Enter one check per line: a full or partial company name of at least 3 characters, or an identifier prefixed with KRS:, NIP:, or REGON:.", "items": { "type": "string" }, "default": [ "ABC" ] }, "personQueries": { "title": "PESEL or NIP identifiers", "type": "array", "description": "Enter one public natural-person check per line as PESEL: followed by 11 digits or NIP: followed by 10 digits. KRZ does not provide public person-name search. Submitted PESEL values are used only for checks and are never exported.", "items": { "type": "string", "pattern": "^(?:PESEL:\\s*[0-9]{11}|NIP:\\s*[0-9]{10})$" } }, "traderQueries": { "title": "Sole traders or identifiers", "type": "array", "description": "Enter one check per line: a full or partial business or person name of at least 3 characters, or an identifier prefixed with NIP:, REGON:, or PESEL:. PESEL is used only for the check and is not exported.", "items": { "type": "string" } }, "caseSignatures": { "title": "Case signatures", "type": "array", "description": "Enter one complete court case signature per line, in the form shown by KRZ.", "items": { "type": "string" } }, "proceedingIds": { "title": "Proceeding identifiers", "type": "array", "description": "Enter one exact KRZ proceeding identifier per line.", "items": { "type": "string" } }, "announcementFrom": { "title": "Announcement date from", "pattern": "^[0-9]{4}-[0-9]{2}-[0-9]{2}$", "type": "string", "description": "Earliest announcement date to include, in YYYY-MM-DD form." }, "announcementTo": { "title": "Announcement date to", "pattern": "^[0-9]{4}-[0-9]{2}-[0-9]{2}$", "type": "string", "description": "Latest announcement date to include, in YYYY-MM-DD form." }, "announcementQueries": { "title": "Subjects or announcement identifiers", "type": "array", "description": "Optionally enter one subject name or exact announcement identifier per line. Prefix an identifier with ID:.", "items": { "type": "string" } }, "announcementCaseSignatures": { "title": "Case signatures", "type": "array", "description": "Optionally enter one complete court case signature per line.", "items": { "type": "string" } }, "announcementProceedingIds": { "title": "Proceeding identifiers", "type": "array", "description": "Optionally enter one exact KRZ proceeding identifier per line.", "items": { "type": "string" } }, "partnerCompanies": { "title": "Companies or identifiers", "type": "array", "description": "Enter one check per line: a full or partial personal-company name of at least 3 characters, or an identifier prefixed with KRS:, NIP:, or REGON:.", "items": { "type": "string" } }, "assetSubjects": { "title": "Subjects or identifiers", "type": "array", "description": "Enter one debtor or estate subject per line as a full or partial name of at least 3 characters, or an identifier prefixed with KRS:, NIP:, REGON:, or PESEL:. Submitted PESEL values are never exported. You can instead provide proceeding context below.", "items": { "type": "string" } }, "assetProceedingIds": { "title": "Proceeding identifiers", "type": "array", "description": "Enter one exact KRZ proceeding identifier per line. You can instead provide subjects above or case signatures below.", "items": { "type": "string" } }, "assetCaseSignatures": { "title": "Case signatures", "type": "array", "description": "Enter one complete court case signature per line when a subject or proceeding identifier is unavailable.", "items": { "type": "string" } }, "assetType": { "title": "Asset category or type", "type": "string", "description": "Optionally restrict assets to a registry category or type." }, "advisorQueries": { "title": "Advisors or licence numbers", "type": "array", "description": "Enter one check per line: a full or partial advisor name of at least 3 characters, or a licence number prefixed with LICENCE:.", "items": { "type": "string" } }, "advisorCity": { "title": "City", "type": "string", "description": "Optionally search for advisors in a listed city, either alone or with the checks above." }, "maxResults": { "title": "Maximum results per check", "minimum": 1, "type": "integer", "description": "Stop each submitted check or announcement search after this many matches. If KRZ caps a broader query first, the output reports that the check is incomplete.", "default": 5 } } }, "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 } } } } } } } } } } ```