DMAI Localization JSON Integrity Check
Pricing
from $100.00 / 1,000 completed integrity reports
DMAI Localization JSON Integrity Check
Compare source and target localization JSON for missing or extra keys, value-type changes, and brace-placeholder mismatches. Returns a machine-readable defect report. No translation-quality scoring or rewriting.
Pricing
from $100.00 / 1,000 completed integrity reports
Rating
0.0
(0)
Developer
Eric Gordon
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
17 days ago
Last modified
Categories
Share
Catch structural defects before a localization release. Paste source and target JSON text and receive one machine-readable report automatically.
What it checks
- Missing and extra JSON paths, including nested objects and array indices.
- Value type changes, including boolean versus number.
- Counts of simple
{identifier}placeholders in corresponding strings, including repeated placeholders.
It does not judge translation quality or rewrite either input. ICU MessageFormat and doubled-brace syntax are rejected. Arrays are compared by index. Placeholder names start with a letter or underscore and may then contain letters, digits, underscores, dots, or hyphens. Other placeholder conventions are outside scope.
Input
sourceJson and targetJson are JSON text strings containing root objects. Paste into the form or send them in a JSON API request. No remote URLs or additional fields are accepted.
Limits per document: 2 MiB of UTF-8 JSON text, 5,000 string values, 20,000 nodes, depth 64, and JSON pointer length 1,024 characters. Duplicate object keys and non-finite numbers are rejected.
Example source: {"welcome":"Hello {name}","save":"Save"}
Example target: {"welcome":"Bonjour {user}","extra":"Extra"}
This pair returns three defects: missing /save, extra /extra, and a placeholder mismatch at /welcome.
Output and delivery
A completed run writes the JSON report to the REPORT record in its default key-value store and exactly one copy to its default dataset. Access REPORT in Storage or use the Report JSON output URL. The dataset API also exposes the report. Fields: schemaVersion, status, summary, issues, truncated, and scope. summary contains total issue counts by kind, node counts and string counts. Each issue has a kind and RFC 6901 JSON-pointer path; type and placeholder mismatches include their compared metadata. Original string values are not included in the report. Input remains in your Apify run storage according to platform retention; this tool is not a zero-retention service.
The first 5,000 defects are listed deterministically. summary.issueCount covers all detected defects and truncated tells you if details were capped. A no_issues_found result means only that the declared checks found no defects.
Price
Proposed launch price: $0.10 per completed report, plus the disclosed $0.00005 Actor-start event per GB of memory (minimum one event). The Store pricing panel is authoritative once monetization is activated. Invalid or unsupported input fails without writing a report; a start charge may still apply.
Status and troubleshooting
Run status is available in Apify Console and the API. Invalid input produces a short failure reason. Fix that reason and submit a new run. Inspect truncated before using results for release decisions. A detected defect is a successful report, not a failed run. Billing questions and refund requests follow Apify's billing/support process; refunds are not promised automatically. Platform issues can be reported using the Actor Issues tab. Maintenance and exception handling remain publisher responsibilities.
