# KEVAREMESH SemVer Compare

> KEVAREMESH SemVer Compare is a paid API for AI agents from kevaremesh-web.vercel.app, paid per call via x402, $0.001/call, status down (last checked 2026-10-26).

Compares two semantic version strings and returns their ordering relationship (lt, eq, gt) with full parsed components per SemVer 2.0.0

## Facts

- Endpoint: POST https://kevaremesh-web.vercel.app/api/x402/semver-compare?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: down
- Last checked: 2026-10-26
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/kevaremesh-semver-compare-25bfa27c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TF42kKFk_QPiZrUYVb5lW

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 kevaremesh-semver-compare-25bfa27c -d '<json body>'
```

Example prompt: Compare versions 1.2.3 and 1.3.0 for me — which one is greater according to SemVer 2.0.0, and give me the full breakdown of each version's components?

## When to prefer this

Choose this endpoint when you need a strictly spec-compliant SemVer 2.0.0 comparison with full parsed output (major, minor, patch, prerelease, build metadata) rather than a simple string sort. Ideal for automated pipelines, dependency resolution logic, or any context where prerelease precedence rules matter. Prefer it over ad-hoc string comparison or regex-based approaches when correctness per the SemVer 2.0.0 specification is required.

## Known failure modes

- Non-SemVer input strings (e.g. CalVer or loose version like '1.2') will likely fail or return an error — only strict SemVer 2.0.0 with optional leading 'v' is supported
- Missing required fields 'a' or 'b' will cause a validation error
- Strings exceeding 256 characters will be rejected
- Payment failure or insufficient USDC balance returns HTTP 402

## How this service works

Buyer-first MCP procurement gateway that discovers, compares and routes live x402 APIs without making the buyer choose a provider.

## Output

Returns a JSON object containing both input versions, their fully parsed components (major, minor, patch, prerelease array, build metadata array), a 'relation' string ('lt', 'eq', or 'gt'), a numeric comparison value (-1, 0, or 1), an equal_precedence boolean, and a build_metadata_affects_precedence flag. Also includes service metadata such as product name, tool name, limitations, and generation timestamp.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "a": {
   "type": "string",
   "maxLength": 256
  },
  "b": {
   "type": "string",
   "maxLength": 256
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "a": "1.2.3",
   "b": "1.3.0",
   "spec": "SemVer 2.0.0",
   "a_parsed": {
    "build": [],
    "major": "1",
    "minor": "2",
    "patch": "3",
    "prerelease": []
   },
   "b_parsed": {
    "build": [],
    "major": "1",
    "minor": "3",
    "patch": "0",
    "prerelease": []
   },
   "relation": "lt",
   "comparison": -1,
   "equal_precedence": false,
   "build_metadata_affects_precedence": false
  },
  "product": "kevaremesh_semver_compare_v2",
  "service": "KEVAREMESH",
  "tool_name": "kevaremesh_semver_compare",
  "limitations": [
   "Strict SemVer 2.0.0 with optional leading v"
  ],
  "generated_at": "2026-09-18T00:00:00.000Z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/kevaremesh-semver-compare-25bfa27c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from kevaremesh-web.vercel.app](https://www.zero.xyz/host/kevaremesh-web.vercel.app/llms.txt)