OpenAPI / Swagger Spec Audit avatar

OpenAPI / Swagger Spec Audit

Pricing

$250.00 / 1,000 completed audits

Go to Apify Store
OpenAPI / Swagger Spec Audit

OpenAPI / Swagger Spec Audit

Fetch an OpenAPI or Swagger spec (JSON or YAML) and get a graded A-F verdict: operation inventory, undocumented operations, missing responses and operationIds, security coverage, and duplicate operationIds. Charged only on completed audits.

Pricing

$250.00 / 1,000 completed audits

Rating

0.0

(0)

Developer

Chris Arsenault

Chris Arsenault

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

5 days ago

Last modified

Share

A quality grade for the machine interface. Point it at an OpenAPI or Swagger spec (URL or inline, JSON or YAML) and get an A-F verdict with the specifics: how many operations, how many are undocumented, which lack responses or operationIds, what security schemes exist and how many operations skip them, and any duplicate operationIds that break code generation.

What you get

Summary plus one row per operation:

{
"spec_type": "openapi", "spec_version": "3.0.4",
"title": "Swagger Petstore", "grade": "A", "operations": 19,
"undocumented_operations": 0, "security_schemes": ["petstore_auth", "api_key"],
"unsecured_operations": 10,
"fixes": ["10 operation(s) have no security applied."]
}
{ "method": "POST", "path": "/pet", "operationId": "addPet",
"summary": "Add a new pet to the store", "problems": [] }

Use cases

  • API teams: run in CI against your published spec; fail the build when documentation or security coverage regresses.
  • Agents and integrators evaluating an API: know before you build whether the contract is complete, secured, and code-gen friendly.
  • Consultants: an instant, evidence-backed quality read on a client's API surface.

Honesty notes

  • Validates structure and hygiene against the OpenAPI/Swagger shape; it is a completeness and quality audit, not a live conformance test against a running server.
  • YAML and JSON specs are both accepted; a document that is neither, or has no openapi/swagger field, is rejected free.
  • Fetching a spec is one polite GET; billing is per completed audit.

Built by 1450 Enterprises, alongside the MCP Server Probe and MCP Server Diff — the same "inventory a machine interface" idea, applied to REST.