A valid OpenAPI spec can still leave large parts of your API untestable. Upload your spec to see where missing examples, schemas, error responses, and constraints limit the coverage your test automation can reach, scored across your full API surface and at every endpoint.
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.
No file selected
Select an OpenAPI YAML or JSON file to begin.
Analysis complete
OpenAPI readiness report
Review the score, category gaps, endpoint issues, and improvement opportunities for the uploaded specification.
1
Summary
A 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 A 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 Independent 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.
0
Independent scoring areas inspected by the analyzer.
Endpoints Operations from the uploaded spec that were analyzed individually for test-generation readiness.
The 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.
3
Prioritized Fixes
A 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.
Fix
Impact Estimated relative importance of the improvement for generated test quality.
Current Coverage How much of the relevant spec area currently contains the required information.
Est. Gain Estimated score gain if this gap is addressed well across the spec.
No prioritized fixes yet.
4
Category Scores
Category 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.
5
Endpoint Readiness
A 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.
Endpoint
Method
Score A 0-100 readiness score for the individual operation, based on the information available for that endpoint.
Top Issues
No endpoint readiness data yet.
6
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.
