Inferring a schema from an example
Paste a JSON document and the generator walks its structure, assigning a type to every value: string, number, integer, boolean, null, array, or object. Nested objects and arrays are inferred recursively, so a deeply nested API response produces a matching nested schema.
Arrays of objects
When an array contains multiple objects, the generator compares their shapes instead of only reading the first item. Properties that appear in every item become required; properties that only appear in some items still show up under properties, just not in the required list. A review array where only some entries include a comment field ends up with comment as optional and user/rating as required.
Mixed-type arrays
An array like [1, 2, 3.5] widens to {"type": "number"} for its items, since a whole number satisfies both integer and number. An array mixing unrelated types, like numbers and strings, produces an anyOf list instead of picking one type arbitrarily.
Required fields toggle
By default, every property found in the sample is marked required, since the sample is the only signal the generator has. Turn off “Mark existing fields as required” when the sample is incomplete and the schema should treat every field as optional instead.