Capability Directory
Conversions
Browse the current transformation routes, compare support states, and decide which path is credible enough to try right now.
Use this snapshot to understand what you can try today and where diagnostics still matter.
Live routes
3
Source formats
3
Documented routes
3
Compare supported routes, partial paths, and the limitations that matter before you run a transformation.
Start from typed source models
TypeScript is currently the clearest source path for round-tripping into a structured schema format.
TypeScript -> JSON Schema
Strongest current route, with good object-shape coverage and some advanced TypeScript caveats.
Alpha✓SupportedTypeScriptJSON Schema
TypeScript -> JSON Schema
Strongest current route, with good object-shape coverage and some advanced TypeScript caveats.
The most mature path today for turning interface-style models into portable schema output.
Working well
Interfaces and object shapes
Primitive fields and arrays
Optional properties
Current limits
Advanced TypeScript semantics still collapse into simpler schema shapes.
Diagnostics should be reviewed for unsupported constructs.
Work back from schema definitions
JSON Schema is already a real integration surface, but some semantics still require close reading of diagnostics.
JSON Schema -> TypeScript
Useful bidirectional schema path today, but advanced schema semantics still need close review.
Alpha✓SupportedJSON SchemaTypeScript
JSON Schema -> TypeScript
Useful bidirectional schema path today, but advanced schema semantics still need close review.
A practical path for turning schema definitions back into TypeScript-facing models.
Working well
Object properties and required fields
Primitive schema types
Basic titles and reusable model names
Current limits
Some schema constructs degrade into broader TypeScript output.
Pattern-driven or highly dynamic schema cases need extra review.
Infer from live payload samples
Raw JSON input is best treated as a fast exploratory path rather than a full contract-preserving workflow.
JSON -> TypeScript
Fast exploratory inference path, but only as representative as the sample payload.
Beta◐PartialJSONTypeScript
JSON -> TypeScript
Fast exploratory inference path, but only as representative as the sample payload.
Useful for quickly inferring a typed model from a representative payload sample.
Working well
Primitive values
Nested objects
Array inference from sample payloads
Current limits
Only the observed sample shape is converted.
Input coverage depends entirely on how representative the sample is.
This is the clearest route to use as the first detailed reference path because it already reflects the strongest current workflow and the cleanest user expectation.
What works well today
Interfaces and object shapes
Primitive fields and arrays
Optional properties
Current caveats
Advanced TypeScript semantics still collapse into simpler schema shapes.
Diagnostics should be reviewed for unsupported constructs.
Choose a documented route, review its support signals, and open the matching Playground flow when you are ready to test it.
Use this route to understand path maturity first, then move into Playground or deeper route-specific guidance.