# Build Artifacts — String Normalisation + Two-Measure Correlation

> Build Artifacts — String Normalisation + Two-Measure Correlation is a paid API for AI agents from market.datapackvibe.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-26).

Normalises string fields and computes two-measure correlation analysis on build artifact records (artifact_mb, build_seconds) for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-game-14-033?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-26
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/build-artifacts-string-normalisation-two-measure-correlation-33051b90
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zuHTVeUwxrSuUV0NSyhFi

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 build-artifacts-string-normalisation-two-measure-correlation-33051b90 -d '<json body>'
```

Example prompt: Can you normalize the game area labels and compute the correlation between artifact size and build duration for these build records: row-1 on 2026-10-01 in group-a with 10 MB and 1 second, row-2 on 2026-10-02 in group-b with 20 MB and 2 seconds, row-3 on 2026-10-03 in group-a with 15 MB and 3 seconds, and row-4 on 2026-10-04 in group-b with 30 MB and 4 seconds?

## When to prefer this

Choose this endpoint when you have up to 200 build artifact records with numeric size (MB) and duration (seconds) fields and need both string normalisation of categorical labels and a statistical two-measure correlation between those numeric fields in a single call. It is well-suited for CI/CD or game build pipeline analysis where you want clean labels and a quantified relationship between artifact size and build time without external data lookups or predictions.

## Known failure modes

- Fewer than 1 row submitted returns a validation error
- More than 200 rows submitted exceeds the row limit and is rejected
- Null values in artifact_mb or build_seconds may reduce correlation reliability
- Malformed date strings not matching YYYY-MM-DD pattern fail schema validation
- row_id missing or empty causes required field validation failure
- Insufficient variance in either metric produces a degenerate or undefined correlation coefficient

## How this service works

Build artifacts — String normalisation + Two-measure correlation: String normalisation + Two-measure correlation for supplied build artifacts records (artifact_mb, build_seconds). Up to 200 rows; 2 independent reports using shared local analytical engines. No live lookup, prediction, professional assessment or external action. 0.01 USDC includes 2 supplied-data reports for up to 200 rows.

## Output

Two analytical reports for the submitted build artifact rows: (1) a string normalisation report cleaning and standardising the game_area and other string fields, and (2) a two-measure correlation report quantifying the statistical relationship between artifact_mb and build_seconds across up to 200 supplied rows. No external lookups or predictions are made; all analysis is performed locally on the submitted data.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "row_id",
     "game_area",
     "date",
     "artifact_mb",
     "build_seconds"
    ],
    "properties": {
     "date": {
      "type": "string",
      "default": "",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "maxLength": 10
     },
     "row_id": {
      "type": "string",
      "default": "",
      "maxLength": 80,
      "minLength": 1
     },
     "game_area": {
      "type": "string",
      "default": "",
      "maxLength": 80
     },
     "artifact_mb": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "build_seconds": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "date": "2026-10-01",
     "row_id": "row-1",
     "game_area": "group-a",
     "artifact_mb": 10,
     "build_seconds": 1
    },
    {
     "date": "2026-10-02",
     "row_id": "row-2",
     "game_area": "group-b",
     "artifact_mb": 20,
     "build_seconds": 2
    },
    {
     "date": "2026-10-03",
     "row_id": "row-3",
     "game_area": "group-a",
     "artifact_mb": 15,
     "build_seconds": 3
    },
    {
     "date": "2026-10-04",
     "row_id": "row-4",
     "game_area": "group-b",
     "artifact_mb": 30,
     "build_seconds": 4
    }
   ],
   "maxItems": 200,
   "minItems": 1
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/build-artifacts-string-normalisation-two-measure-correlation-33051b90/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from market.datapackvibe.com](https://www.zero.xyz/host/market.datapackvibe.com/llms.txt)