# Localization Coverage Record Quality Audit and String Normalisation

> Localization Coverage Record Quality Audit and String Normalisation 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-25).

Performs a dual-report quality audit and string normalisation on up to 200 localization coverage records containing source and translated string counts.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-game-18-001?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-25
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/localization-coverage-record-quality-audit-and-string-normalisation-461ae2aa
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Qi5XaZyy9-6rvPgKHkgBQ

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-record-quality-audit-and-string-normalisation-461ae2aa -d '<json body>'
```

Example prompt: Can you run a quality audit and string normalisation on my localization coverage data for the following game areas — I have up to 200 rows with source_strings and translated_strings counts by date, like row-1 for group-a on 2026-10-01 with 10 source strings and 1 translated string, and I need both reports?

## When to prefer this

Choose this endpoint when you need a fast, low-cost dual-report quality audit and string normalisation specifically for localization coverage data (source vs translated string counts) organised by game area and date, with no need for live external data, predictions, or professional assessment. Best suited for game development teams running local data hygiene checks on up to 200 rows at $0.01 per call.

## Known failure modes

- More than 200 rows submitted — request rejected due to maxItems limit
- Missing required fields (row_id, game_area, date, source_strings, translated_strings) cause validation errors
- Invalid date format (not YYYY-MM-DD pattern) triggers schema rejection
- source_strings or translated_strings values outside the allowed numeric range cause errors
- Empty rows array (minItems:1 not met) returns an error

## How this service works

Localization coverage — Record quality audit + String normalisation: Record quality audit + String normalisation 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

Two independent analytical reports: (1) a record quality audit flagging data issues across the supplied localization coverage rows, and (2) a string normalisation report standardising the source_strings and translated_strings values — all computed locally from the supplied data, with no external lookups or predictions.

## 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
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/localization-coverage-record-quality-audit-and-string-normalisation-461ae2aa/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)