Semver Evaluate

Use to compare strict Semantic Versioning versions and evaluate npm-compatible version ranges before choosing a package. Prerelease matching is excluded by default unless the range explicitly allows it.

standards · Operation ID: semver-evaluate

Choose this operation when

Compare strict versions and check npm-compatible ranges.

Outside this profile

Looking up package releases, vulnerabilities, or non-SemVer version systems.

Exact release references

Static JSON contract · Markdown reference · Fixed example response

Complete input schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "version": {
      "type": "string",
      "maxLength": 256
    },
    "against": {
      "type": "string",
      "maxLength": 256
    },
    "range": {
      "type": "string",
      "maxLength": 1024
    },
    "includePrerelease": {
      "default": false,
      "type": "boolean"
    }
  },
  "required": [
    "version",
    "against"
  ],
  "additionalProperties": false
}

Complete output-envelope schema

{
  "type": "object",
  "required": [
    "operation",
    "version",
    "result",
    "provenance"
  ],
  "properties": {
    "operation": {
      "const": "semver-evaluate",
      "type": "string"
    },
    "version": {
      "const": "0.29.0",
      "type": "string"
    },
    "result": {
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "type": "object",
      "properties": {
        "version": {
          "type": "string"
        },
        "against": {
          "type": "string"
        },
        "comparison": {
          "type": "integer",
          "minimum": -1,
          "maximum": 1
        },
        "satisfies": {
          "type": [
            "boolean",
            "null"
          ]
        },
        "prerelease": {
          "type": "array",
          "items": {
            "type": [
              "string",
              "number"
            ]
          }
        }
      },
      "required": [
        "version",
        "against",
        "comparison",
        "satisfies",
        "prerelease"
      ],
      "additionalProperties": false
    },
    "provenance": {
      "type": "object",
      "required": [
        "inputSha256",
        "outputSha256",
        "deterministic",
        "externalRequests"
      ],
      "properties": {
        "inputSha256": {
          "type": "string",
          "pattern": "^[a-f0-9]{64}$"
        },
        "outputSha256": {
          "type": "string",
          "pattern": "^[a-f0-9]{64}$"
        },
        "deterministic": {
          "const": true
        },
        "externalRequests": {
          "const": 0
        }
      }
    }
  },
  "additionalProperties": false
}

Fixed example

One accepted fixed example, not a custom-input trial. No operation runs when this static page is requested.

Example input

{
  "version": "2.3.1",
  "against": "2.2.0",
  "range": "^2.0.0"
}

Example response

{
  "operation": "semver-evaluate",
  "version": "0.29.0",
  "result": {
    "version": "2.3.1",
    "against": "2.2.0",
    "comparison": 1,
    "satisfies": true,
    "prerelease": []
  },
  "provenance": {
    "inputSha256": "6344dd6d2cf1f4675e8f6d45100b01973e77537f2032c3c1a9b76cc85ae23e1a",
    "outputSha256": "5976f73e251f9e706bc064e66edb7ad1e151142e4187fa32b3b175e7ee92ed3c",
    "deterministic": true,
    "externalRequests": 0
  }
}

Bounds and precision

JavaScript IEEE-754 numbers; use strings for large integer IDs/exact decimals where the schema accepts strings. No lossless numeric parsing.

{
  "global": {
    "requestBytes": 131072,
    "responseBytes": 524288,
    "jsonDepth": 32,
    "jsonNodes": 20000,
    "requestsPerMinute": 60,
    "paidAttemptsPerMinute": 20,
    "idempotencyHours": 24
  },
  "operation": {
    "requestBytes": 131072,
    "responseBytes": 524288,
    "jsonDepth": 32
  }
}

Complete schemas, descriptions and cross-field validation may impose additional limits.

Proposed price and protocol definitions

{
  "unit": "one successful operation call",
  "proposedNominalUsd": "0.003",
  "sixDecimalTokenBaseUnits": "3000",
  "subscription": false,
  "includesPayerWalletOrNetworkFees": false,
  "liveQuoteVerified": false,
  "condition": "Actual SDK challenge is authoritative only within the caller's explicit authorization; configured six-decimal token peg is an operator assertion, not a conversion guarantee."
}

Protocol definitions: x402, mpp. MPP uses Tempo charge. Paid MCP execution is unsupported. All runtime readiness is not evaluated in this build.

API path templates, not endpoints on this documentation host

{
  "x402": "/v1/x402/semver-evaluate",
  "mpp": "/v1/mpp/semver-evaluate"
}

Required headers

{
  "Content-Type": "application/json",
  "Idempotency-Key": "random 16–128 character operation identifier"
}

Actual SDK challenge amount, asset, network, recipient and wallet costs must pass independent authorization. Preserve identical key, body, protocol and credential on retries; on PAYMENT_UNCERTAIN stop and reconcile.

Execution profile and provider conditions

{
  "deterministic": true,
  "externalRequests": 0,
  "maxExternalRequests": 0,
  "resultSnapshotPersisted": false,
  "fixedExampleIsIllustrativeSnapshot": false,
  "requiresPayment": true,
  "supportsMcpExecution": false
}

Deterministic supplied-input operation with no external requests or stored request/result bodies. Payment infrastructure retains payment metadata and hashes.

Failure handling

HTTP 400: Malformed JSON, missing/invalid idempotency key, or payment identifier mismatch Correct the request before payment
HTTP 402: Payment challenge or rejected payment Use official protocol SDK; inspect payment outcome before another payment
HTTP 409: Idempotency conflict, duplicate proof, or PAYMENT_UNCERTAIN Keep original key, body, and proof; reconcile uncertainty with operator; never blindly repay
HTTP 413: Input or generated output too large Reduce input; no payment attempted for validation failure
HTTP 415: Unsupported media type or compression Send uncompressed application/json
HTTP 422: Schema or service-specific semantic validation failure Correct input using returned error code; no payment attempted
HTTP 429: Request/payment-attempt rate exceeded Wait for rate limit window; preserve existing payment identity
HTTP 503: Payment configuration/provider/state unavailable, or live DNS preparation failed before settlement Check readiness; DNS preparation failures may retry the identical key/body/credential only; uncertainty requires reconciliation

Declared requirements

Before any paid call, refresh the live operation contract and POST the complete bounded budgeted plan to the separate API's /preflight. Unknown requirements block selection; compatible preflight is not permission to spend.