# Sindri Semver Compare

> Sindri Semver Compare is a paid API for AI agents from x402.outpimp.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Compares two semantic version strings and returns whether versionA is greater than, less than, or equal to versionB using standard semver rules.

## Facts

- Endpoint: POST https://x402.outpimp.com/semverCompare
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sindri-semver-compare-736b87a1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_b9ZAvEhyIhBcZ2ZEIlrxL

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 sindri-semver-compare-736b87a1 -d '<json body>'
```

Example prompt: Which semver version is greater — 2.11.0 or 2.9.3?

## When to prefer this

Use this endpoint when you need a quick, authoritative semver comparison without implementing semver parsing logic yourself — ideal for CI/CD pipelines, dependency checkers, or any agent workflow that needs to determine version ordering between exactly two semver strings in real time.

## Known failure modes

- Malformed version string (e.g. missing patch segment or non-numeric parts) returns an error or unexpected result
- Pre-release labels (e.g. 1.0.0-alpha) may not be handled if the API only supports core semver
- Empty or null version strings cause a validation error
- Build metadata suffixes may be ignored or cause parsing errors

## How this service works

Compares two semantic version strings and reports which is greater, lesser, or equal, using the standard semver comparison rules.

## Output

Returns a comparison result indicating whether versionA is greater than, less than, or equal to versionB according to standard semantic versioning (major.minor.patch) precedence rules.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "versionA": {
   "type": "string",
   "description": "First semantic version, e.g. \"1.2.3\"."
  },
  "versionB": {
   "type": "string",
   "description": "Second semantic version, e.g. \"1.2.4\"."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/sindri-semver-compare-736b87a1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.outpimp.com](https://www.zero.xyz/host/x402.outpimp.com/llms.txt)