# TOML Validator & Converter (`automation-lab/toml-validator`) Actor Validate TOML files and convert between TOML, JSON, and YAML. Paste documents or fetch from URLs. Bulk processing with exact error line numbers. - **URL**: https://apify.com/automation-lab/toml-validator.md - **Developed by:** [Stas Persiianenko](https://apify.com/automation-lab) (community) - **Categories:** Developer tools - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, NaN bookmarks - **User rating**: No ratings yet ## 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. 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 ## TOML Validator & Converter Validate TOML syntax, detect errors with exact line numbers, and convert between **TOML**, **JSON**, and **YAML** formats β€” in bulk, via API, or as part of any automation pipeline. --- ### What does it do? TOML Validator & Converter is a pure-computation Apify actor that processes TOML, JSON, and YAML documents without touching any websites or requiring proxies. You paste documents directly or provide URLs to raw config files, and the actor returns: - βœ… **Validation status** β€” is the document syntactically valid TOML? - πŸ”’ **Error line number** β€” exactly where is the syntax error? - πŸ“„ **Error message** β€” human-readable description of the problem - πŸ”„ **Converted output** β€” the document reformatted as TOML, JSON, or YAML It processes documents in bulk (up to hundreds in one run), making it ideal for CI/CD pipelines, config file audits, and data transformation workflows. --- ### Who is it for? #### πŸ¦€ Rust developers Validate and lint `Cargo.toml` files programmatically. Catch syntax errors in dependency manifests before `cargo build` fails. Convert Cargo configuration to JSON for automated tooling. #### πŸ—οΈ DevOps and platform engineers Validate configuration files (Prometheus, Vector, InfluxDB, Gitea, Hugo, uv, pyproject.toml) before deploying. Automate config file validation across hundreds of repositories or microservices. #### πŸ”§ Python / Node.js developers Convert between `pyproject.toml`, `package.json`, and YAML-based configurations when migrating between ecosystems. Validate `pyproject.toml` files as part of publishing pipelines. #### πŸ“Š Data engineers Normalize configuration data from multiple sources (TOML, JSON, YAML) into a consistent format before loading into databases or data pipelines. #### πŸ€– Automation builders Use with Apify integrations (Zapier, Make, n8n) to validate config files generated by other automation steps before processing them downstream. Gate CI/CD workflows on TOML validity. --- ### Why use TOML Validator & Converter? - **No setup required** β€” runs instantly, no browser, no proxy, no scraping - **Precise error reporting** β€” exact line numbers, not just "invalid TOML" - **Multi-format support** β€” TOML, JSON, and YAML all in one actor - **Bidirectional conversion** β€” any format to any other format (TOMLβ†’JSON, JSONβ†’TOML, YAMLβ†’TOML, etc.) - **Bulk processing** β€” validate dozens of documents in a single run at low cost - **URL fetching** β€” point at raw GitHub URLs, CDN-hosted configs, or any public endpoint - **API-first** β€” programmatic access via REST API, Node.js SDK, Python SDK - **Zero proxy costs** β€” pure computation, no bandwidth charges --- ### What data does it extract? Each processed document produces one row in the dataset: | Field | Type | Description | |-------|------|-------------| | `index` | number | 1-based position in the input list | | `source` | text | `inline-N` for pasted docs, URL for fetched docs | | `inputFormat` | text | Detected or specified format: `toml`, `json`, or `yaml` | | `isValid` | boolean | `true` if the document is syntactically valid | | `errorMessage` | text | Human-readable error description (null if valid) | | `errorLine` | number | Line number where error occurred (null if valid) | | `outputFormat` | text | Target format for conversion (null if validate-only) | | `convertedContent` | text | Converted document string (null if validate-only or invalid) | | `originalContent` | text | Original input text (only if `includeOriginal` is enabled) | --- ### How much does it cost to validate TOML and convert formats? This actor uses **pay-per-event (PPE) pricing** β€” you only pay for what you process, with volume discounts for higher subscription tiers: | Event | Free | Bronze | Silver | Gold | Platinum | Diamond | |-------|------|--------|--------|------|----------|---------| | πŸš€ Actor start (per run) | $0.005 | $0.00475 | $0.00425 | $0.00375 | $0.003 | $0.0025 | | πŸ“„ Document processed | $0.001 | $0.0009 | $0.0008 | $0.00065 | $0.0005 | $0.0004 | **Example costs (Free tier):** - Validate 1 Cargo.toml: $0.005 + 1 Γ— $0.001 = **$0.006** - Validate 10 config files: $0.005 + 10 Γ— $0.001 = **$0.015** - Convert 50 TOML files to JSON: $0.005 + 50 Γ— $0.001 = **$0.055** - Validate 100 pyproject.toml files: $0.005 + 100 Γ— $0.001 = **$0.105** **Free plan**: Apify's free tier includes $5/month of platform credits β€” enough to process **~4,900 documents per month** at no cost. This actor uses **zero proxy** (pure computation only), so there are no proxy bandwidth costs. --- ### How to use TOML Validator & Converter #### Step 1 β€” Open the actor Go to [https://apify.com/automation-lab/toml-validator](https://apify.com/automation-lab/toml-validator) and click **Try for free**. #### Step 2 β€” Choose your input method **Option A: Paste documents directly** Add your TOML, JSON, or YAML documents in the **Documents** field. Each entry in the list is one complete document. **Option B: Provide URLs** Add raw file URLs in the **URLs to Fetch** field. For example: - GitHub raw: `https://raw.githubusercontent.com/owner/repo/main/Cargo.toml` - pyproject.toml: `https://raw.githubusercontent.com/owner/repo/main/pyproject.toml` - Any public HTTP endpoint returning a config file #### Step 3 β€” Select operation - **Validate only** β€” checks syntax and reports errors with line numbers - **Convert** β€” transforms documents to the target format (TOML, JSON, or YAML) #### Step 4 β€” Configure format options - **Input Format**: `auto` (recommended) detects TOML, JSON, and YAML automatically - **Output Format**: choose `toml`, `json`, or `yaml` (only for convert operation) #### Step 5 β€” Run and export Click **Start** and wait a few seconds. Download results as JSON, CSV, or Excel from the **Dataset** tab. --- ### Input parameters | Parameter | Type | Default | Description | |-----------|------|---------|-------------| | `documents` | string[] | β€” | Raw document texts to validate or convert | | `urls` | string[] | β€” | URLs to fetch and process as documents | | `operation` | string | `validate` | `validate` or `convert` | | `inputFormat` | string | `auto` | `auto`, `toml`, `json`, or `yaml` | | `outputFormat` | string | `json` | `toml`, `json`, or `yaml` (for convert only) | | `jsonIndent` | integer | `2` | Spaces for JSON indentation (0 = minified) | | `stopOnError` | boolean | `false` | Stop processing after the first invalid document | | `includeOriginal` | boolean | `false` | Include original document text in output | --- ### Output example For a validation run on two documents (one valid Cargo.toml, one invalid): ```json [ { "index": 1, "source": "inline-1", "inputFormat": "toml", "isValid": true, "errorMessage": null, "errorLine": null, "outputFormat": null, "convertedContent": null }, { "index": 2, "source": "inline-2", "inputFormat": "toml", "isValid": false, "errorMessage": "Unexpected character, expecting string, number, datetime, boolean, inline array or inline table at row 2, col 8, pos 18", "errorLine": 2, "outputFormat": null, "convertedContent": null } ] ```` For a conversion run (TOML to JSON): ```json [ { "index": 1, "source": "inline-1", "inputFormat": "toml", "isValid": true, "errorMessage": null, "errorLine": null, "outputFormat": "json", "convertedContent": "{\n \"package\": {\n \"name\": \"my-app\",\n \"version\": \"1.0.0\"\n },\n \"dependencies\": {\n \"serde\": \"1.0\"\n }\n}" } ] ``` *** ### Tips for best results πŸ’‘ **Use `auto` format detection** β€” the actor correctly identifies TOML, JSON, and YAML from content patterns. Only specify a format if your documents are ambiguous. πŸ’‘ **Validate before converting** β€” if you're converting many documents, run a validate pass first. Invalid documents produce no converted output. πŸ’‘ **Use `stopOnError: true` in CI/CD** β€” gates your pipeline on the first error, making failures fast and obvious. πŸ’‘ **TOML output requires a top-level object** β€” arrays and scalar values cannot be serialized to TOML (TOML spec). If your document is an array at the top level, convert to JSON or YAML instead. πŸ’‘ **URL fetching supports any public HTTP endpoint** β€” GitHub raw URLs, S3 presigned URLs, and CDN-hosted files all work. The actor follows redirects and handles standard HTTP responses. πŸ’‘ **Batch many documents in one run** β€” the start fee is $0.005 regardless of document count. Processing 100 documents in one run is far cheaper than 100 separate runs. πŸ’‘ **TOML integers use underscore separators** β€” when converting JSON numbers like `8080` to TOML, the output may use `8_080` (valid TOML notation for readability). This is standard TOML behavior. *** ### Integrations #### πŸ”— CI/CD pipeline gate (GitHub Actions) Validate all TOML configs before deployment: ```yaml - name: Validate TOML configs run: | curl -s -X POST \ "https://api.apify.com/v2/acts/automation-lab~toml-validator/run-sync-get-dataset-items?token=${{ secrets.APIFY_TOKEN }}" \ -H "Content-Type: application/json" \ -d '{ "urls": ["${{ env.CARGO_TOML_URL }}"], "operation": "validate", "stopOnError": true }' | python3 -c " import sys, json items = json.load(sys.stdin) if any(not item['isValid'] for item in items): print('TOML validation failed!') sys.exit(1) print('All TOML files valid.') " ``` #### πŸ”— Make (Integromat) workflow Trigger on file upload β†’ validate TOML β†’ branch on `isValid` β†’ send Slack alert on invalid config. #### πŸ”— Zapier automation Validate TOML text from a form submission β†’ convert to JSON β†’ push to Airtable or Google Sheets. #### πŸ”— n8n workflow Fetch config files from GitHub via HTTP Request β†’ batch-validate with TOML Validator β†’ filter invalid rows β†’ create GitHub Issues for each error. #### πŸ”— Apify integration chain Combine with other automation-lab actors: - [YAML Validator](https://apify.com/automation-lab/yaml-validator) β€” validate YAML syntax and convert between YAML, JSON, and TOML - [JSON CSV Converter](https://apify.com/automation-lab/json-csv-converter) β€” convert JSON output to CSV for spreadsheet analysis - [cURL to Code Converter](https://apify.com/automation-lab/curl-to-code-converter) β€” convert cURL commands to code in multiple languages *** ### API usage #### Node.js ```javascript import { ApifyClient } from 'apify-client'; const client = new ApifyClient({ token: 'YOUR_API_TOKEN' }); const run = await client.actor('automation-lab/toml-validator').call({ documents: [ '[package]\nname = "my-app"\nversion = "1.0.0"\n\n[dependencies]\nserde = "1.0"\n', '{ "name": "Jane", "age": 25 }' ], operation: 'convert', outputFormat: 'toml' }); const { items } = await client.dataset(run.defaultDatasetId).listItems(); console.log(items); ``` #### Python ```python from apify_client import ApifyClient client = ApifyClient(token="YOUR_API_TOKEN") run = client.actor("automation-lab/toml-validator").call(run_input={ "urls": [ "https://raw.githubusercontent.com/owner/repo/main/Cargo.toml", "https://raw.githubusercontent.com/owner/repo/main/pyproject.toml" ], "operation": "validate" }) items = client.dataset(run["defaultDatasetId"]).list_items().items for item in items: status = "valid" if item["isValid"] else f"INVALID (line {item['errorLine']}): {item['errorMessage']}" print(f"{item['source']}: {status}") ``` #### cURL ```bash curl -X POST \ "https://api.apify.com/v2/acts/automation-lab~toml-validator/runs?token=YOUR_API_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "documents": ["[package]\nname = \"my-app\"\nversion = \"1.0.0\"\n"], "operation": "convert", "outputFormat": "json" }' ``` *** ### Use with Claude (MCP) Connect this actor as an MCP tool to validate and convert TOML/JSON/YAML directly in Claude conversations. #### Claude Code / Cursor / VS Code ```bash claude mcp add --transport http apify "https://mcp.apify.com?tools=automation-lab/toml-validator" ``` #### Claude Desktop Add to your `claude_desktop_config.json`: ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com?tools=automation-lab/toml-validator", "headers": { "Authorization": "Bearer YOUR_APIFY_TOKEN" } } } } ``` **Example prompts:** - "Validate this Cargo.toml for syntax errors: \[paste TOML]" - "Convert this JSON config to TOML format: \[paste JSON]" - "Check if my pyproject.toml is valid and report any errors" - "I have 5 TOML files at these GitHub URLs β€” validate them all and tell me which ones have errors" - "Convert this YAML config to TOML so I can use it in my Rust project" *** ### Is it legal to use? Yes. This actor performs local data transformation only β€” it does not scrape any websites, does not access any third-party services, and processes only the data you explicitly provide. There are no legal concerns around terms of service or robots.txt because no crawling takes place. *** ### FAQ #### What TOML version is supported? The actor uses [@iarna/toml](https://github.com/iarna/iarna-toml) v2, which supports TOML v0.5 specification including inline tables, arrays of tables (`[[array]]`), multi-line strings, datetime values, and all standard data types. #### Does it support TOML arrays of tables (`[[section]]`)? Yes. Arrays of tables (like multiple `[[worker]]` or `[[dependency]]` entries) are fully supported and correctly parsed into JavaScript arrays of objects. #### Why does my JSON number like `8080` become `8_080` in TOML output? TOML supports underscore separators in integer literals for readability (e.g., `8_080` or `1_000_000`). This is valid TOML notation and will parse correctly in any TOML parser. If you need the number without underscores, you can post-process the output. #### My TOML conversion is failing with "top-level value must be an object" β€” why? TOML requires the root of the document to be a key-value map (object). If your JSON or YAML document has an array at the top level (e.g., `[1, 2, 3]` or `- item: value`), it cannot be serialized to TOML. Convert to JSON or YAML instead. #### The actor detected my TOML file as YAML β€” what do I do? Set `inputFormat: "toml"` explicitly. Auto-detection uses content heuristics (TOML uses `=` assignments, YAML uses `:` mappings) and can occasionally misclassify edge cases, especially for minimal or unusual files. #### My URL fetch is failing β€” what could be wrong? - Ensure the URL returns raw text (not an HTML page wrapping the file) - For GitHub, use `raw.githubusercontent.com` URLs, not the `github.com` browse URLs - Private URLs are not supported β€” the URL must be publicly accessible - Check that the URL returns a `200 OK` status code #### Can I validate private config files without exposing them? Yes β€” paste the document content directly in the `documents` field. The content is processed within your actor run and only the validation results are saved to the Apify dataset. Nothing is sent to external services. #### Can I validate TOML and JSON in the same run? Yes. Set `inputFormat: "auto"` (the default) and mix TOML, JSON, and YAML documents freely. The actor detects each document's format independently. *** ### Related scrapers - [YAML Validator](https://apify.com/automation-lab/yaml-validator) β€” validate YAML syntax and convert between YAML, JSON, and TOML - [Fake Test Data Generator](https://apify.com/automation-lab/fake-test-data-generator) β€” generate bulk test data in JSON, CSV, or NDJSON - [JSON CSV Converter](https://apify.com/automation-lab/json-csv-converter) β€” convert between JSON and CSV formats - [cURL to Code Converter](https://apify.com/automation-lab/curl-to-code-converter) β€” convert cURL commands to code in multiple languages # Actor input Schema ## `documents` (type: `array`): Enter one or more documents to validate or convert. Each item should be the full text of a TOML, JSON, or YAML document. ## `urls` (type: `array`): Provide URLs pointing to raw TOML, JSON, or YAML files (e.g., GitHub raw URLs, Cargo.toml endpoints). Each URL will be fetched and processed as a separate document. ## `operation` (type: `string`): Choose what to do with each document: 'validate' checks syntax and reports errors; 'convert' transforms the document to the target format. ## `inputFormat` (type: `string`): Specify the format of your input documents. Use 'auto' to detect automatically (TOML, JSON, or YAML). ## `outputFormat` (type: `string`): Target format for conversion. Only used when operation is 'convert'. Choose TOML, JSON, or YAML. ## `jsonIndent` (type: `integer`): Number of spaces for JSON output indentation. Set to 0 for compact (minified) JSON. ## `stopOnError` (type: `boolean`): If enabled, the actor stops processing after the first document with a validation error. Useful for CI/CD pipelines where any error is a blocker. ## `includeOriginal` (type: `boolean`): If enabled, the original document text is included in each dataset result row. ## Actor input object example ```json { "documents": [ "[package]\nname = \"my-app\"\nversion = \"1.0.0\"\nedition = \"2021\"\n\n[dependencies]\nserde = { version = \"1.0\", features = [\"derive\"] }\ntokio = { version = \"1\", features = [\"full\"] }\n\n[profile.release]\nopt-level = 3" ], "urls": [], "operation": "validate", "inputFormat": "auto", "outputFormat": "json", "jsonIndent": 2, "stopOnError": false, "includeOriginal": false } ``` # Actor output Schema ## `overview` (type: `string`): No description # 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 = { "documents": [ "[package]\nname = \"my-app\"\nversion = \"1.0.0\"\nedition = \"2021\"\n\n[dependencies]\nserde = { version = \"1.0\", features = [\"derive\"] }\ntokio = { version = \"1\", features = [\"full\"] }\n\n[profile.release]\nopt-level = 3" ], "urls": [], "operation": "validate", "inputFormat": "auto", "outputFormat": "json", "jsonIndent": 2, "stopOnError": false, "includeOriginal": false }; // Run the Actor and wait for it to finish const run = await client.actor("automation-lab/toml-validator").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 = { "documents": ["""[package] name = \"my-app\" version = \"1.0.0\" edition = \"2021\" [dependencies] serde = { version = \"1.0\", features = [\"derive\"] } tokio = { version = \"1\", features = [\"full\"] } [profile.release] opt-level = 3"""], "urls": [], "operation": "validate", "inputFormat": "auto", "outputFormat": "json", "jsonIndent": 2, "stopOnError": False, "includeOriginal": False, } # Run the Actor and wait for it to finish run = client.actor("automation-lab/toml-validator").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 '{ "documents": [ "[package]\\nname = \\"my-app\\"\\nversion = \\"1.0.0\\"\\nedition = \\"2021\\"\\n\\n[dependencies]\\nserde = { version = \\"1.0\\", features = [\\"derive\\"] }\\ntokio = { version = \\"1\\", features = [\\"full\\"] }\\n\\n[profile.release]\\nopt-level = 3" ], "urls": [], "operation": "validate", "inputFormat": "auto", "outputFormat": "json", "jsonIndent": 2, "stopOnError": false, "includeOriginal": false }' | apify call automation-lab/toml-validator --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=automation-lab/toml-validator", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "TOML Validator & Converter", "description": "Validate TOML files and convert between TOML, JSON, and YAML. Paste documents or fetch from URLs. Bulk processing with exact error line numbers.", "version": "0.1", "x-build-id": "faQYBdVB7deMBbs9K" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/automation-lab~toml-validator/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-automation-lab-toml-validator", "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/automation-lab~toml-validator/runs": { "post": { "operationId": "runs-sync-automation-lab-toml-validator", "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/automation-lab~toml-validator/run-sync": { "post": { "operationId": "run-sync-automation-lab-toml-validator", "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", "properties": { "documents": { "title": "πŸ“„ TOML / JSON / YAML Documents", "type": "array", "description": "Enter one or more documents to validate or convert. Each item should be the full text of a TOML, JSON, or YAML document.", "items": { "type": "string" } }, "urls": { "title": "πŸ”— URLs to Fetch", "type": "array", "description": "Provide URLs pointing to raw TOML, JSON, or YAML files (e.g., GitHub raw URLs, Cargo.toml endpoints). Each URL will be fetched and processed as a separate document.", "items": { "type": "string" } }, "operation": { "title": "βš™οΈ Operation", "enum": [ "validate", "convert" ], "type": "string", "description": "Choose what to do with each document: 'validate' checks syntax and reports errors; 'convert' transforms the document to the target format.", "default": "validate" }, "inputFormat": { "title": "πŸ“₯ Input Format", "enum": [ "auto", "toml", "json", "yaml" ], "type": "string", "description": "Specify the format of your input documents. Use 'auto' to detect automatically (TOML, JSON, or YAML).", "default": "auto" }, "outputFormat": { "title": "πŸ“€ Output Format", "enum": [ "toml", "json", "yaml" ], "type": "string", "description": "Target format for conversion. Only used when operation is 'convert'. Choose TOML, JSON, or YAML.", "default": "json" }, "jsonIndent": { "title": "JSON Indent Spaces", "minimum": 0, "maximum": 8, "type": "integer", "description": "Number of spaces for JSON output indentation. Set to 0 for compact (minified) JSON.", "default": 2 }, "stopOnError": { "title": "Stop on first error", "type": "boolean", "description": "If enabled, the actor stops processing after the first document with a validation error. Useful for CI/CD pipelines where any error is a blocker.", "default": false }, "includeOriginal": { "title": "Include original content in output", "type": "boolean", "description": "If enabled, the original document text is included in each dataset result row.", "default": false } } }, "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 } } } } } } } } } } ```