API Quality Score Checker

Benchmark your OpenAPI 3.0 & Swagger 2.0 specifications with a deterministic 0–100 quality score and actionable fix recommendations.

Analyze Your OpenAPI Spec Now

Paste any OpenAPI or Swagger URL into the APIForge workspace to generate your quality report in seconds.

Open Workbench & Calculate Score →

Scoring Methodology & Criteria

APIForge splits API specification scoring into 7 empirical categories derived from REST design guidelines and OpenAPI standards:

CategoryMax WeightEvaluation Rules
Path Naming20 pointsPenalizes camelCase in paths, underscores, and verb-like segments (/getUsers).
HTTP Verb Usage20 pointsPenalizes GET requests containing request bodies and actions embedded in paths.
Path Structure & Depth15 pointsEvaluates URL segment nesting depth (penalizes paths deeper than 3 segments).
Consistency15 pointsDetects duplicate method/path pairs and mixed singular vs plural collection tokens.
Versioning Prefixes10 pointsChecks for explicit major version segments (e.g., /v1, /v2) across URL paths.
Error Handling Coverage10 pointsVerifies declarations of 4xx and 5xx failure status codes and reusable error schemas.
Operation Documentation10 pointsCalculates percentage of operations with non-empty summaries and descriptions.

Frequently Asked Questions

How is the 0–100 API Quality Score calculated?
APIForge evaluates 7 deterministic criteria: Path Naming (20 pts), HTTP Verb Usage (20 pts), Path Structure & Depth (15 pts), Consistency & Duplicate Checks (15 pts), Versioning Prefixes (10 pts), Error Handling Coverage (10 pts), and Operation Documentation (10 pts).
Does APIForge require sending spec data to an external server?
No. The API scoring engine executes deterministically in your browser without sending your OpenAPI specification or secrets to external LLMs or third-party servers.