# CycloneDX VEX Explicit Integer Release Status Intersection

> CycloneDX VEX Explicit Integer Release Status Intersection is a paid API for AI agents from detect.halowerk.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-11-01).

Resolves affected/unaffected/unknown VEX status for integer-versioned product releases and detects contradictions between data and claim entries.

## Facts

- Endpoint: POST https://detect.halowerk.com/v1/F-TD2000-DOCUMENTS-01/cyclonedx-vex-explicit-integer-release-status-intersection?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/cyclonedx-vex-explicit-integer-release-status-intersection-4cf8025c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Ax6BtDgNJSqP5yDo2_Tfp

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 cyclonedx-vex-explicit-integer-release-status-intersection-4cf8025c -d '<json body>'
```

Example prompt: Check whether product 'acme-core' at integer release version 42 is affected, unaffected, or unknown based on these VEX ranges — affected from 10 to 50, unaffected from 40 to 60 — and flag any contradictions between those ranges and our existing claim that version 42 is unaffected.

## When to prefer this

Use this endpoint when you need to resolve vulnerability exposure status for software products that use integer (not semver) versioning and need explicit contradiction detection between VEX data ranges and claim assertions. Ideal for CycloneDX VEX workflows where overlapping affected/unaffected ranges must be surfaced before publication or triage decisions. Prefer this over generic SBOM tools when the version scheme is strictly integer and claim/data cross-validation is required.

## Known failure modes

- Version integer out of range (0–1,000,000 bounds exceeded) → schema validation error
- Products array empty (minItems:1 violated) → request rejected
- Affects version range where min > max → logical contradiction may be flagged or rejected
- Too many products or affects entries (maxItems:64 exceeded) → schema validation error
- Claim references a product ref not present in products array → unresolvable cross-reference
- Malformed ref strings exceeding maxLength:64 → schema validation error

## How this service works

Resolve affected/unaffected/unknown status for supplied integer product releases and expose overlapping contradictions.

## Output

Returns the resolved VEX status (affected, unaffected, or unknown) for each supplied product and integer version, along with any detected contradictions where status ranges overlap or claims conflict with the underlying data.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "artifact": {
   "type": "object",
   "required": [
    "vexStatus"
   ],
   "properties": {
    "vexStatus": {
     "type": "object",
     "required": [
      "data",
      "claim"
     ],
     "properties": {
      "data": {
       "type": "object",
       "required": [
        "products",
        "affects"
       ],
       "properties": {
        "affects": {
         "type": "array",
         "items": {
          "type": "object",
          "required": [
           "ref",
           "versions"
          ],
          "properties": {
           "ref": {
            "type": "string",
            "maxLength": 64
           },
           "versions": {
            "type": "array",
            "items": {
             "type": "object",
             "required": [
              "min",
              "max",
              "status"
             ],
             "properties": {
              "max": {
               "type": "integer",
               "maximum": 1000000,
               "minimum": 0
              },
              "min": {
               "type": "integer",
               "maximum": 1000000,
               "minimum": 0
              },
              "status": {
               "enum": [
                "affected",
                "unaffected",
                "unknown"
               ]
              }
             },
             "additionalProperties": false
            },
            "maxItems": 32,
            "minItems": 0
           }
          },
          "additionalProperties": false
         },
         "maxItems": 64,
         "minItems": 0
        },
        "products": {
         "type": "array",
         "items": {
          "type": "object",
          "required": [
           "ref",
           "version"
          ],
          "properties": {
           "ref": {
            "type": "string",
            "maxLength": 64
           },
           "version": {
            "type": "integer",
            "maximum": 1000000,
            "minimum": 0
           }
          },
          "additionalProperties": false
         },
         "maxItems": 64,
         "minItems": 1
        }
       },
       "additionalProperties": false
      },
      "claim": {
       "anyOf": [
        {
         "type": "null"
        },
        {
         "type": "object",
         "required": [
          "products"
         ],
         "properties": {
          "products": {
           "type": "array",
           "items": {
        
… (truncated)
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cyclonedx-vex-explicit-integer-release-status-intersection-4cf8025c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from detect.halowerk.com](https://www.zero.xyz/host/detect.halowerk.com/llms.txt)