CLI / CI

Free JSON validator command-line tool for Windows®

Validate JSON syntax and JSON Schema contracts from Windows scripts, builds, and CI with valbuddy.exe, actionable locations, logs, and process results.

Download JSONBuddy + CLI Use the ValBuddy agent skill

Command Prompt — JSONBuddy validation

C:\> valbuddy.exe -v -verbose -s
  "D:\Examples\Library\library_schema.json"
  "D:\Examples\Library\library.json"
  "D:\Examples\Library\library_invalid.json"

library.json: valid
library_invalid.json: invalid
Required property missing: title
Input location: /bib/book/2

Repeatable JSON checks

Run JSON validation in scripts and CI

The command-line workflow accepts one or more JSON or XML inputs, can apply a specific schema, and can emit a fuller diagnostic report for review. Use it for interactive checks, saved batch configurations, and repeatable Windows automation.

Start with one known-valid and one known-invalid example. Once the command, schema assignment, diagnostics, and process result behave as expected, use the same tested invocation for a larger file set or automated build.

Validate one file or a set

Pass individual documents directly for well-formedness or schema validation, and keep the input paths visible in the resulting log.

Inspect actionable diagnostics

Use the reported input location and schema location to connect a failed JSON value to the constraint that rejected it.

Reuse a configured batch task

Create a batch configuration in the desktop application, save the settings, and invoke that configuration from automation for repeatable automation.

Build a batch-validation workflow

Usage pattern

Make validation results useful to both people and pipelines

Choose the JSON documents and the schema or well-formedness check the workflow requires.
Run the command locally with verbose output until the inputs, paths, and diagnostics are understood.
Capture the process return value and preserve the validation log as a build artifact.
Move the tested invocation into a script or CI job and keep product/version context with the configuration.

Documented return-code behavior

Use the documented return value together with the validation log in your automation.

Platform availability

Choose where to run this workflow

Desktop / WindowsAvailable for configuring and testing the interactive workflow on Windows.
CLI / CIFeatured access: valbuddy.exe in the documented Windows portable-package journey.

Continue the automation path

Keep adjacent workflows distinct

Use the batch page for directory and settings-based processing, the large-data page for streaming-oriented validation, and the dedicated conversion page for repeatable XML/JSON transformations. These URLs answer separate search and workflow needs.

Agent and CI workflow

Run the file locally. Return the finding, not the whole document.

The same command can be called by a developer, an AI coding agent, or a Windows CI runner. That avoids repeated dependency selection, validator setup, and one-off glue code while keeping the validation step reproducible.

Run valbuddy.exe -v -verbose -s "D:\Schemas\library_schema.json" "D:\Data\library.json".
Treat exit code 0 as success and every non-zero value as failure.
Give the agent the status and relevant diagnostics so it can explain or correct the focused issue.
Run the same command again after a change.

Local execution boundary

The CLI opens the specified files in the Windows environment. An agent may still send selected data or diagnostics to its model provider, and schemas can resolve remote references when the workflow permits network access.

Use the ValBuddy skill to reuse tested wrappers and argument order.