Check version compatibility API

Order dotted numeric versions and compare the supplied schemas. A version number alone is not treated as compatible. The payload is checked against the later schema.

The Check version compatibility operation is part of the API Integration Intelligence API on BRAINIAC.software. Order dotted numeric versions and compare the supplied schemas. A version number alone is not treated as compatible. The payload is checked against the later schema. It is exposed as POST /api/v1/integration/version-compatibility-check and priced at $0.04 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Schemas, examples, and payloads supplied in the request. Limitations: No external API is called and no user-supplied code is executed. Validation covers a documented JSON Schema subset. It is not a full draft certification. Mappings are proposed only for paths or field names that exist on both sides. A breaking change is labeled only when the caller sets side to request or response. Transforms are limited to rename, copy, pick, omit, cast, and default. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Generate a JSON schema, Validate a payload, Normalize an API response, Transform a payload. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.04 USDC
/api/v1/integration/version-compatibility-check

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/integration/version-compatibility-check" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "side": "response",
  "fromVersion": "1.2.0",
  "toVersion": "1.3.0",
  "before": {
    "type": "object",
    "properties": {
      "id": {
        "type": "string"
      },
      "total": {
        "type": "number"
      }
    },
    "required": [
      "id"
    ],
    "additionalProperties": true
  },
  "after": {
    "type": "object",
    "properties": {
      "id": {
        "type": "string"
      },
      "total": {
        "type": "integer"
      }
    },
    "required": [
      "id",
      "total"
    ],
    "additionalProperties": true
  },
  "payload": {
    "id": "ord_1",
    "total": 12.5
  }
}
JSON

An unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.

FAQ

  • Do I need an API key? No. Pay the listed USDC amount with x402.
  • What network? Base (eip155:8453), USDC.
  • Is this an official determination? No. Results are for human review against the cited sources.

Related APIs

API Integration Intelligence APIFull docsHow it works