Interactive converter
JSON Schema to OpenAI strict tool compiler
Convert JSON Schema to an OpenAI strict function tool with recursive required and additionalProperties repairs.
This conversion closes every object, makes previously optional fields nullable, expands required arrays, and reports unsupported vocabulary before emitting the tool wrapper.
Read the schema and its provider wrapper as one contract. APITC distinguishes target requirements from portable JSON Schema, applies mechanical repairs only when intent is recoverable, and identifies transformations that can change meaning.
Diagnostic procedure
Repair the schema, then recompile.
- 01
Paste a schema or wrapper
APITC auto-detects raw JSON Schema and common provider wrappers.
- 02
Review diagnostics
Errors block correctness; fixes are deterministic; warnings flag meaning that may change.
- 03
Copy compiled JSON
Use the output tab or download a target-specific JSON file.
{"type":"object","properties":{"query":{"type":"string"},"limit":{"type":"integer"}},"required":["query"]}{"type":"function","name":"compiled_tool","parameters":{"type":"object","properties":{"query":{"type":"string"},"limit":{"type":["integer","null"]}},"required":["query","limit"],"additionalProperties":false},"strict":true}$.inputSchemaClose this objectOpenAI strict requires additionalProperties: false on every object.
$.inputSchemaRequired array is incompleteStrict mode requires every property in required. APITC will make limit nullable.
No account · no upload · no endpoint calledOpen the full tool schema compiler and operating notes →
FAQ
Before you ship
Does APITC upload my schema?
No. Parsing, diagnostics, and compilation run in your browser tab.
Is the compiled result guaranteed to preserve meaning?
Safe repairs are deterministic. When OpenAI cannot express a source constraint, APITC labels the transform as lossy instead of hiding it.
Protocol behavior checked against the OpenAI function calling guide. Recheck your pinned provider/API version before production deployment.