C↗ Contract Lens

OPENAPI CHANGE REVIEW · NANO PAYMENTS

What changed.
What could break.

Send two OpenAPI 3 documents. Get a structured comparison of routes, required inputs, response contracts and security declarations.

0.01 XNOOne document pair. No account.

A report you can act on

Example output
LevelLocationChange
BreakingDELETE /projects/{id}Operation removed
ReviewGET /projects → 200Response contract changed
AddedPOST /exportsOperation added

THREE REQUESTS TO A RESULT

Quote. Pay. Compare.

  1. POST JSON with before and after documents to /v1/audit. A valid request returns HTTP 402 with a unique Nano address and quote token.
  2. Send exactly 0.01 XNO to that address using your wallet. Keep the send block hash.
  3. Repeat the same JSON with X-Quote-Id, X-Quote-Token, and X-Nano-Payment. A confirmed payment unlocks the report.

Each quote is tied to one exact request body. Its token also permits retries of that same paid report. A payment cannot unlock another quote.

1 / REQUEST A QUOTE

curl -X POST "$BASE/v1/audit" \
  -H 'Content-Type: application/json' \
  --data-binary @change.json

change.json

{
  "before": {
    "openapi": "3.0.3",
    "paths": { "/health": { "get": {
      "responses": { "200": {} }
    } } }
  },
  "after": {
    "openapi": "3.0.3",
    "paths": {}
  }
}

Prepay for repeated comparisons.

The same 0.01 XNO rate applies to prepaid packs: 100 calls for 1 XNO, 1,000 for 10 XNO, 1,500 for 15 XNO or 2,500 for 25 XNO. POST {"calls":1000} to /v1/credits for a dedicated invoice. A confirmed payment activates the pack.

Use the private quote token as a Bearer token, the quote ID as X-Credit-Id, and a unique Idempotency-Key on each audit. Reuse the same key and exact body on retries to avoid another debit. Credits do not expire and cannot be withdrawn as a wallet balance. Full activation, balance and retry instructions are in the API documentation.

Structural review, with clear limits.

This is a deterministic comparison, not a complete OpenAPI validator or a proof of backward compatibility. Schema, media-type and security changes are flagged for review. Local references are compared; remote references are never fetched. Documentation-only edits are ignored.

JSON only, up to 128 KiB for the pair and 200 operations per document. No uploaded files or external API calls on your behalf. Request bodies and reports are not saved. Quote and request-key hashes, credit usage and payment receipts are retained for billing and safe retries.