Schema completeness
Find missing schema types, descriptions, examples, and property details that make a contract harder to understand and use.
Analyze an OpenAPI definition for schema gaps, missing documentation, and other contract issues. OpenAPI Blueprint groups actionable suggestions so your team knows what to improve and where to start.
Use a URL, upload a JSON or YAML file, or paste your spec.
OpenAPI scan summary
Orders API
OpenAPI 3.1 · 24 paths · 38 operations
12
suggestions
9
5
3
Example documentation findings
Order schema is missing a description
Schema · Order
Property 'status' has no example
Schema · Order.status
GET /orders is missing a summary
Operation · GET /orders
Illustrative preview. Findings depend on the specification you analyze.
Review the contract
The analyzer checks the structure and documentation in your OpenAPI spec, then groups suggestions into focused categories.
Find missing schema types, descriptions, examples, and property details that make a contract harder to understand and use.
Surface operations without summaries, descriptions, tags, parameter guidance, or clear response details.
Review grouped suggestions across security, API design, versioning, compliance, performance, and governance.
OpenAPI Blueprint provides findings and improvement guidance. Your team decides how to update the contract; the analyzer does not silently rewrite your specification.
A straightforward review
Use the findings to make your API contract easier to maintain and more useful for developers, integrators, and downstream tools.
Enter a live spec URL, upload a JSON or YAML file, or paste the specification into the analyzer.
See the paths, operations, schemas, and grouped findings detected in the document.
Use the suggestions to fill schema gaps, clarify operations, and make the contract more useful to its consumers.