# Localization Resource Integrity Analyzer

> Localization Resource Integrity Analyzer is a paid API for AI agents from mcp-factory.bowling-anthony.workers.dev, paid per call via x402, $0.03/call, status unknown (last checked 2026-09-15).

Validates localization files for missing keys, extra keys, and placeholder mismatches across multiple locales compared to a source locale

## Facts

- Endpoint: POST https://mcp-factory.bowling-anthony.workers.dev/localization-resource-integrity/analyze
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/localization-resource-integrity-analyzer-ee2fc084
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ewEEzgjjVKvxKAHWUksTg

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-resource-integrity-analyzer-ee2fc084 -d '<json body>'
```

Example prompt: Can you check my localization files for missing translation keys and broken placeholders? Here are my source English strings and the French and Spanish translations — I need to know which locales are failing and exactly what's wrong with each one.

## When to prefer this

Use this endpoint when you need automated, per-call validation of i18n/l10n resource files at $0.03 USDC per check — ideal for CI/CD pipelines, pre-release QA gates, or on-demand audits where you need a structured report of missing keys, extra keys, and placeholder integrity issues across multiple target locales simultaneously.

## Known failure modes

- Malformed or empty input locale data returns an error response
- Missing source locale causes analysis to fail with no baseline for comparison
- Payment failure via x402 results in 402 response before analysis runs
- Unsupported locale format or encoding may cause parsing errors
- Placeholder syntax that doesn't match expected patterns may produce false positives

## How this service works

Customer-input analysis tools with per-call x402 v2 USDC payments on Base. Discovery and examples are free.

## Output

Returns a JSON object with a per-locale breakdown (passed boolean, missing_keys array, extra_keys array, issues array with key/code/actual/expected), a source_issues array, and a summary object containing total locales checked, passing locales count, total source keys, and total issue count.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "scope": "resource_structure_and_placeholders_only",
  "locales": [
   {
    "issues": [],
    "locale": "fr",
    "passed": true,
    "extra_keys": [],
    "missing_keys": []
   },
   {
    "issues": [
     {
      "key": "cart.items_count",
      "code": "missing_placeholder",
      "actual": "suffix=0",
      "expected": "suffix=1"
     }
    ],
    "locale": "es",
    "passed": false,
    "extra_keys": [],
    "missing_keys": [
     "checkout.total"
    ]
   }
  ],
  "summary": {
   "issues": 2,
   "locales": 2,
   "source_keys": 3,
   "passing_locales": 1
  },
  "source_issues": []
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/localization-resource-integrity-analyzer-ee2fc084/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mcp-factory.bowling-anthony.workers.dev](https://www.zero.xyz/host/mcp-factory.bowling-anthony.workers.dev/llms.txt)