# Localization Coverage Two-Measure Correlation and Secondary-Measure Weighted Mean

> Localization Coverage Two-Measure Correlation and Secondary-Measure Weighted Mean 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).

Computes Pearson correlation between source_strings and translated_strings, plus a weighted mean of a selected secondary measure, for up to 200 localization coverage records across game areas.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-game-18-181?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/localization-coverage-two-measure-correlation-and-secondary-measure-1bb1cf85
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8qzBt4drxG6BNwGYxHHsm

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 localization-coverage-two-measure-correlation-and-secondary-measure-1bb1cf85 -d '<json body>'
```

Example prompt: Can you run a two-measure correlation and weighted mean analysis on these localization coverage records — I have 4 rows with game areas group-a and group-b, source_strings counts of 10, 20, 15, 30 and translated_strings of 1, 2, 3, 4 across dates 2026-10-01 to 2026-10-04, using source_strings as the secondary field?

## When to prefer this

Choose this endpoint when you need both a correlation coefficient and a weighted mean computed together on localization coverage data (source_strings vs translated_strings) in a single paid call. Prefer it over generic stats tools when your data is already structured as game-area localization records and you want two bundled analytical outputs at low cost ($0.01 USDC). Not suitable for live translation lookups, prediction, or external enrichment.

## Known failure modes

- Fewer than 1 row supplied — minimum row count not met
- More than 200 rows supplied — exceeds maximum batch size
- Missing required fields (row_id, game_area, date, source_strings, translated_strings) — validation error
- Invalid date format (must match YYYY-MM-DD pattern) — schema rejection
- Null values in both measure columns may produce undefined correlation
- row_id exceeds 80 character limit — rejected
- Insufficient numeric variance for correlation computation — result may be NaN or undefined

## How this service works

Localization coverage — Two-measure correlation + Secondary-measure weighted mean: Two-measure correlation + Secondary-measure weighted mean for supplied localization coverage records (source_strings, translated_strings). 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

Returns two analytical reports: (1) a Pearson correlation coefficient between source_strings and translated_strings across the supplied rows, and (2) a weighted mean of the selected secondary measure (source_strings or translated_strings). Both reports are computed locally on the supplied data with no external lookups.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "row_id",
     "game_area",
     "date",
     "source_strings",
     "translated_strings"
    ],
    "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
     },
     "source_strings": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "translated_strings": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "date": "2026-10-01",
     "row_id": "row-1",
     "game_area": "group-a",
     "source_strings": 10,
     "translated_strings": 1
    },
    {
     "date": "2026-10-02",
     "row_id": "row-2",
     "game_area": "group-b",
     "source_strings": 20,
     "translated_strings": 2
    },
    {
     "date": "2026-10-03",
     "row_id": "row-3",
     "game_area": "group-a",
     "source_strings": 15,
     "translated_strings": 3
    },
    {
     "date": "2026-10-04",
     "row_id": "row-4",
     "game_area": "group-b",
     "source_strings": 30,
     "translated_strings": 4
    }
   ],
   "maxItems": 200,
   "minItems": 1
  },
  "field": {
   "enum": [
    "source_strings",
    "translated_strings"
   ],
   "type": "string",
   "default": "source_strings"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/localization-coverage-two-measure-correlation-and-secondary-measure-1bb1cf85/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)