Format Directory
Formats
Browse the current single-format support surface, compare parser and generator readiness, and understand where each format is already credible.
This page should help a developer judge single-format readiness before they even think about a specific conversion pair.
Formats surfaced
14
Parser-ready formats
14
Generator-ready formats
14
Each format should answer one practical question: how trustworthy is it today as an input parser, an output generator, or both?
JSONJSON
Strong parser, no current generator, best for fast inference.
BetaParser support
✓SupportedGenerator support
✓Supported
JSON
Strong parser, no current generator, best for fast inference.
Parser support
✓SupportedGenerator support
✓SupportedJSON is strongest as a lightweight source format for sample-driven inference and quick exploratory runs.
Working well
Fast sample ingestion
Good fit for exploratory typing
Clear path into TypeScript inference
Current limits
JSON is not a current output target in the public Playground flow.
Sample coverage depends entirely on the representativeness of the input payload.
JSON inference is intentionally conservative and is not a universal schema inference engine.
Mixed-type handling depends on parser inference options rather than one always-on widening rule.
tuple-inference-modes
record-inference-modes
JSON SchemaJSON Schema
Bidirectional support today, but advanced schema semantics still need review.
BetaParser support
✓SupportedGenerator support
✓Supported
JSON Schema
Bidirectional support today, but advanced schema semantics still need review.
Parser support
✓SupportedGenerator support
✓SupportedJSON Schema is already a real bidirectional integration surface, but some advanced constructs still need careful diagnostic review.
Working well
Real parser and generator surface
Useful contract format for interchange
Works well with current TypeScript-facing flows
Current limits
Highly dynamic schema patterns may degrade into broader output.
Some semantics still require reading diagnostics to understand loss.
JSON Schema support is limited to the current IR-aligned Draft 2020-12 subset.
Validation-heavy and document-system features such as external references remain unsupported.
Object-only allOf can be merged; references, non-object compositions, not, and conditional schemas remain outside the current JSON Schema parser subset.
constraint-round-trip-through-shared-ir
Related conversions
OpenAPIOpenAPI
Bidirectional API-schema surface with component entry selection on parse.
BetaParser support
✓SupportedGenerator support
✓Supported
OpenAPI
Bidirectional API-schema surface with component entry selection on parse.
Parser support
✓SupportedGenerator support
✓SupportedOpenAPI is supported as a schema-oriented parser and generator. The parser reads components.schemas and selects one component as the Shape IR root; it does not process the full API surface.
Working well
Parses OpenAPI component schemas
Generates schema-oriented OpenAPI 3.1 documents
Reuses the shared Shape IR pipeline
Current limits
Generation emits a canonical OpenAPI 3.1 schema document and does not recreate paths or operations.
Documents with multiple component schemas require selecting an entry when parsing.
Paths, operations, parameters, security, callbacks, webhooks, and external references are outside the current scope.
OpenAPI support is currently limited to extracting schemas from components.schemas rather than processing the full API document.
OpenAPI generation emits only a canonical 3.1 schema document and does not recreate source metadata or API operations.
Paths, operations, request and response bodies, parameters, headers, security, callbacks, and webhooks are outside the current parser boundary.
Only local references to components.schemas are supported; external and URL-based references are unsupported.
Object-only allOf compositions can be merged into shared IR; conflicting or non-object compositions remain unsupported.
full-document-processing
allOf-composition
Related conversions
TypeScriptTypeScript
Strongest current authoring format with good schema-generation pairing.
BetaParser support
✓SupportedGenerator support
✓Supported
TypeScript
Strongest current authoring format with good schema-generation pairing.
Parser support
✓SupportedGenerator support
✓SupportedTypeScript is currently the clearest developer-facing source format and one of the easiest ways to understand the toolkit's value quickly.
Working well
Strongest current authoring experience
Good fit for typed model review
Pairs well with JSON Schema generation
Current limits
Advanced TypeScript semantics can collapse into simpler downstream shapes.
Generator-side output is only as precise as the currently supported schema model.
TypeScript support is limited to schema-oriented declarations rather than the full language.
Single-file parsing is the current boundary, so imported or cross-file type resolution is unsupported.
Function types, conditional types, mapped types, and intersection types are outside the current supported subset.
TypeScript generation widens integer semantics to number and does not preserve constraint families directly.
implicit-entry-selection
enum-lowering-within-schema-subset
Related conversions
Start with a format overview, review its parser, generator, and related routes, then verify the result in the shared Playground.