Home Choose the tool for the job in front of you

Choose the tool for the job in front of you

Generate rows when you need new example data. Convert a document when you already have the values. Infer a type when you need to describe the shape, then review what the sample cannot tell you.

I need new test data

If a complete file is enough, download sample CSV, sample JSON, employee data or sales data. Sample files are synthetic; they are not observations of actual people or businesses.

I already have a CSV, JSON or Excel file

These tools transform values you supply; they do not create missing business rules or validate your destination database. Check each tool's supported input shape, file limits and preview before downloading.

I need to inspect a document or describe its shape

Use the JSON formatter for readable JSON, JSON to YAML or YAML to JSON for document conversion, and JSON to XML or XML to JSON when the destination needs XML.

For application types, choose JSON to TypeScript, JSON to Zod, JSON to Pydantic, JSON to JSON Schema or CSV to TypeScript. Inference describes the supplied sample, not every value your API might return. Add absent fields, domain constraints and validation rules explicitly.

I need a reusable local workflow

The source-checkout CLI guide shows local file generation; the MCP guide explains assistant integration and its privacy boundary. Neither assumes registry publication. Save the schema and seed with the engine revision and use fixed dates for repeatable runs.

Browser generation and conversion run locally. Optional account features sync saved workspace data, and optional analytics have their own consent choice. The privacy and methodology page explains those boundaries. Contact the maintainer through the public GitHub profile for source or permission questions.

Last updated