{"uid":"cap_KkwuU5MfDnF-B32FAxDDX","slug":"localization-coverage-analyzer-record-quality-audit-string-427af5bd","name":"Localization Coverage Analyzer — Record Quality Audit + String Normalisation + Date by Category Pivot","description":"Localization coverage — Record quality audit + String normalisation + Date by category pivot: Record quality audit + String normalisation + Date by category pivot for supplied localization coverage records (source_strings, translated_strings). Up to 200 rows; 3 independent reports using shared local analytical engines. No live lookup, prediction, professional assessment or external action. 0.01 USDC includes 3 supplied-data reports for up to 200 rows.","url":"https://market.datapackvibe.com/x402/assistant-ib26-game-18-206?utm_source=zero.xyz","method":"POST","headers":{},"bodySchema":{"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"}}},"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.01","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.01/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.01","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.01","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_j07MN4dFryBdv-KmTg7Pr","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.01","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Runs three analytical reports on localization coverage data: a record quality audit, string normalisation, and a date-by-category pivot, for up to 200 rows of source/translated string counts.","exampleAgentPrompt":"Can you run a record quality audit, string normalisation, and date-by-category pivot on my localization coverage data? I have rows with game areas like 'ui-menus' and 'dialogue', dates from 2026-10-01 to 2026-10-07, source string counts and translated string counts — up to 50 rows total — and I want the analysis focused on the source_strings field.","exampleUseCases":[{"title":"Game localization gap detection","prompt":"I have localization data for my game with rows for each game area and date, showing how many source strings exist vs how many have been translated. Can you audit the data quality, normalize the string counts, and give me a pivot by date and game area so I can see where translation coverage is lagging? Here are 80 rows covering areas like 'cutscenes', 'ui', and 'tutorial' from October 2026, and I want it focused on translated_strings."},{"title":"Pre-release translation completeness check","prompt":"Before our game ships, I need to check our localization records for quality issues — missing values, duplicates, anything suspicious. Can you run a record quality audit plus a date-by-category pivot on these 120 rows of source and translated string data across game areas like 'combat', 'inventory', and 'main-menu'? Focus the analysis on source_strings."},{"title":"Monthly localization progress summary","prompt":"We track localization coverage weekly across different parts of our game. Can you normalize our string count data and pivot it by date and game area for the month of October 2026? I've got about 150 rows with game areas like 'story', 'settings', and 'hud', and I want the quality audit included too — let's use translated_strings as the primary field."}],"resultDescription":"Returns three independent analytical reports computed locally on the supplied data: (1) a record quality audit flagging missing, null, or malformed values; (2) normalised string data with standardised formatting; and (3) a date-by-category pivot aggregating source or translated string counts by game area over time. No external data is fetched.","failureModes":["Rows array exceeds 200 items — request rejected","Missing required fields (row_id, game_area, date, source_strings, translated_strings) on any row — validation error","Date field does not match YYYY-MM-DD pattern — schema validation failure","Numeric values outside allowed range (-1e12 to 1e12) — validation error","Empty rows array (minItems:1 violated) — request rejected","Invalid field enum value (must be 'source_strings' or 'translated_strings') — validation error"],"whenToPreferThis":"Choose this endpoint when you have up to 200 rows of localization coverage data (source and translated string counts by game area and date) and need three bundled analytical reports — quality audit, normalisation, and date-category pivot — in a single low-cost call ($0.01 USDC). It is a pure local-compute endpoint with no external lookups, so it is fast and deterministic. Prefer it over manual analysis or separate single-report endpoints when you want all three reports at once for game localization QA or progress tracking.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-11-02T18:33:50.711Z","isFirstParty":false,"canonicalSlug":"localization-coverage-analyzer-record-quality-audit-string-427af5bd"}