{✓}OpenAPI CheckBY TASKCRAFTAPI reference0.01 USDC / request
SPECIFICATION CHECKS · OPENAPI 3.0 + 3.1

Find the broken contract.
Before your client does.

Check operation IDs, local references, response definitions and security declarations. Get precise document paths and a structured report.

01 / DOCUMENTJSON OR YAML

Public GitHub raw files or SwaggerHub. Up to 1 MB. External references are reported, never fetched.

This button does not pay. An x402 client authorizes a custom report. Client integration guide

One focused pass

  • Duplicate operation identifiers
  • Broken local references
  • Incomplete response definitions
  • Unknown security schemes
  • Missing required path parameters
02 / REPORTBROKEN EXAMPLE
—errors in selected checks
OPENAPI 3.x
Loading the built-in example…

Checks cover top-level path operations and local references. This is not a full specification or security audit.

FOR AGENTS & AUTOMATION

Request a report over HTTP.

The endpoint uses x402 v2: inspect the payment requirements, authorize 0.01 USDC on Base in your own client, then receive JSON.

OpenAPI specification · Agent quickstart

Same authorization, same report: a retry returns the saved result. A pending payment returns 202; keep the original authorization and do not pay again.

GET /api/checkapplication/json
curl -i "$SITE/api/check?url=$SPEC_URL"

HTTP/1.1 402 Payment Required
PAYMENT-REQUIRED: <x402 v2 requirements>

Your signing key stays in your own payment client. The server uses only the merchant receiving address.