# fittings Semver Bump Classifier

> fittings Semver Bump Classifier is a paid API for AI agents from fittings.sh, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-14).

Classifies the semantic version change between two versions (e.g. major, minor, patch) and reports direction and caret-range compatibility.

## Facts

- Endpoint: GET https://fittings.sh/v1/semver/bump-classify
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/fittings-semver-bump-classifier-0a1b9c3e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5fjYytZrV3BNSkKntppsg

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability fittings-semver-bump-classifier-0a1b9c3e
```

Example prompt: Can you classify the semver bump between version 1.2.3 and 2.0.0 — is it major, minor, or patch, and does it stay within a caret range?

## When to prefer this

Choose this endpoint when you need a precise, programmatic classification of the semantic version difference between two version strings — especially when you also need to know caret-range compatibility. Prefer it over manual regex or string comparison when the bump type (major/minor/patch/pre*) and range compatibility must both be known in one call.

## Known failure modes

- Invalid semver strings for 'from' or 'to' result in an error response
- Missing required 'from' or 'to' query parameters return a validation error
- Non-standard version strings (e.g. date-based versions) may not be parseable
- Reversed or equal versions may return 'none' or unexpected direction

## How this service works

Classifies the change between two versions as major, minor, patch, premajor, preminor, prepatch, prerelease or none, with the direction and whether the move stays inside a caret range.

## Output

Returns the bump type (one of: major, minor, patch, premajor, preminor, prepatch, prerelease, or none), the direction of change (upgrade or downgrade), and whether the version move stays within a caret (^) range.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "from",
      "to"
     ],
     "properties": {
      "to": {
       "type": "string",
       "description": "The version being moved to, e.g. 1.3.0"
      },
      "from": {
       "type": "string",
       "description": "The version being moved away from, e.g. 1.2.3"
      }
     }
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/fittings-semver-bump-classifier-0a1b9c3e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from fittings.sh](https://www.zero.xyz/host/fittings.sh/llms.txt)