OpenAPI Spec Analyzer | KushoAI

Upload OpenAPI specification

Accepted formats: .yaml, .yml, .json.

iYour spec is not stored by KushoAI. It is used only during this session to analyze the spec and generate the readiness score.

Choose file

No file selected

Analyze spec<br>Clear

Select an OpenAPI YAML or JSON file to begin.

What the report includes

Readiness

A single score for how ready your API surface is for automated test generation, with a rating you can track as the spec improves and report against.

Gaps

Every place the spec lacks the examples, schemas, auth detail, error responses, and constraints that tests depend on, with the effect on coverage spelled out.

Endpoints

A readiness score for every operation, so you can see exactly which routes are well covered and which carry risk.

Exports

The full report in JSON or Markdown, ready to share with your team or attach to a quality review.

Summary<br>iA top-level view of whether the spec has enough structure, examples, constraints, errors, auth detail, and documentation for automated test generation.

A top-level view of how ready the specification is for automated test generation, beyond basic OpenAPI validity. This is the number to track as the spec improves.

Upload a specification to generate the readiness dashboard.

Readiness score iA 0-100 weighted aggregate score returned by the analyzer API, representing how ready the OpenAPI spec is for high-quality automated API test generation.

0/100

Not analyzed

Categories iIndependent scoring dimensions used to explain which parts of the spec help or limit generated tests. Higher-weight categories have more influence on the overall score.

Independent scoring areas inspected by the analyzer.

Endpoints iOperations from the uploaded spec that were analyzed individually for test-generation readiness.

Endpoint-level readiness records in the report.

Next step

See what KushoAI can generate from this spec.

Try KushoAI

Download JSON report<br>Download Markdown report

What is driving the score<br>iThe highest-impact gaps behind the current score, framed around coverage risk rather than implementation detail.

The first few gaps usually explain most of the lost readiness. Fix these before working through lower-impact cleanup.

Prioritized Fixes<br>iA remediation list ranked by the coverage you stand to gain. Work top to bottom to raise readiness in the order that returns the most.

Ranked by estimated readiness gain. Gains are directional and should be treated as planning guidance, not strictly additive commitments.

FixImpact iEstimated relative importance of the improvement for generated test quality.Current Coverage iHow much of the relevant spec area currently contains the required information.Est. Gain iEstimated score gain if this gap is addressed well across the spec.

No prioritized fixes yet.

Category Scores<br>iCategory scores break overall readiness into the specific signals test generators depend on, so you can see which parts of the spec are strong and which limit coverage.

A compact view of the scored dimensions behind the overall readiness number.

Weightage rationale: schema quality, constraints, examples, and error handling carry more weight because they most directly determine whether generated tests can create valid payloads, boundary cases, negative cases, and useful assertions.

Endpoint Readiness<br>iA per-operation view of readiness issues, useful for finding exactly which API routes need better schemas, examples, responses, or metadata.

A readiness score for every operation in the spec. Use it to find the specific routes that need better schemas, examples, error responses, or metadata before they can be tested well.

EndpointMethodScore iA 0-100 readiness score for the individual operation, based on the information available for that endpoint.Top Issues

No endpoint readiness data yet.

How to Read This

The overall score is a weighted aggregate across the scored categories. It measures whether the spec carries enough structure, examples, constraints, error responses, auth detail, and documentation to generate meaningful automated tests. It is not a measure of OpenAPI compliance; a spec can be valid and still score low here.

Details

&times;