# Localization Placeholder Parity (`immemorial_sarinda/localization-placeholder-parity`) Actor

Check two flat JSON translation catalogs for missing or extra resource keys and mismatched named placeholders. Get one complete deterministic report. Supports a strict named-placeholder profile; checks structure, not translation quality. No external translation or AI service.

- **URL**: https://apify.com/immemorial_sarinda/localization-placeholder-parity.md
- **Developed by:** [Picknotes](https://apify.com/immemorial_sarinda) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$100.00 / 1,000 completed reports

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Localization Placeholder Parity

Check two flat JSON translation catalogs for missing or extra resource keys and mismatched named placeholders. This tool checks structure, not translation quality or meaning.

### Quick start

Run the synthetic example with:

```json
{"useDemo":true}
```

The demo reports `issues`: `invite` is missing the `team` placeholder, `removed` is a missing key, and `extra` is an extra key. Literal doubled braces are not placeholders. To check your own catalogs:

```json
{"useDemo":false,"authorizedNonpersonalNonconfidentialData":true,"placeholderProfile":"python-format-named/1","sourceCatalogJson":"{\"greeting\":\"Hello {name}\"}","targetCatalogJson":"{\"greeting\":\"Bonjour {name}\"}"}
```

The two catalog fields contain JSON text, not nested objects. Omit all three own-input fields in demo mode. Empty catalogs are supported. Duplicate keys, malformed JSON and unsupported syntax reject the whole request.

### Supported syntax and limits

Only `python-format-named/1` is supported: `{NAME}`, where NAME uses ASCII letters, digits and underscores, begins with a letter or underscore, and has at most 64 characters. `{{` and `}}` are literal braces. No ICU, positional fields, conversions, format specifications, attribute/index access or nested replacements are supported. No alternate placeholder language is detected. Placeholder sets are compared case-sensitively; repeated-occurrence count differences alone are informational.

Each catalog is limited to 1,048,576 UTF-8 bytes and 1,000 keys, with at most 128 code points per key, 8,192 code points per message and 128 placeholder occurrences per message. Catalogs must be flat objects containing string values. Decoded key/message UTF-8 totals also cannot exceed 1,048,576 bytes per catalog. Maximum output is 2,000 rows and 2,097,152 report bytes. Limits apply together; an oversized report is rejected without truncation. The outer request is limited to 4,500,000 bytes. Unicode is preserved without normalization; raw JSON surrogate escapes are rejected.

### Results and pricing

A completed report is delivered as one dataset item. Its `reportJson` string contains the complete canonical report, including one final newline; `reportSha256` and `reportBytes` identify those exact bytes. `status` is `ok` or `issues`, and rows cover every key in the source/target union. Missing keys and placeholder mismatches are complete findings and qualify as completed reports.

The intended price is USD 0.10 per completed report in one dataset item, including complete reports with issues. Check the Actor's live pricing before running. A receipt records completion intent and consistency, not proof of payment settlement. Rejected requests do not attempt a completion event, but platform usage costs may still apply. There is one append attempt and no automatic retry. If delivery is uncertain, check the existing run and dataset before rerunning to avoid possible duplicate charges.

### Data handling

Submit only authorized nonpersonal, nonconfidential data. Apify stores INPUT before execution. Reports retain resource keys, placeholder names, counts and hashes; raw message prose is not included. This is not a secret scanner or anonymizer. Platform storage and access settings apply; there is no private-storage, automatic-deletion or retention guarantee from this tool. No external translation or AI service is used.

# Actor input Schema

## `authorizedNonpersonalNonconfidentialData` (type: `boolean`):

Confirm you are authorized to submit these nonpersonal, nonconfidential catalogs. Required as true for own-input mode.

## `placeholderProfile` (type: `string`):

Own mode only. Leave absent in demo. Runtime enforces exact profile and UTF-8 byte limits.

## `sourceCatalogJson` (type: `string`):

Own mode only. Leave absent in demo. Runtime enforces exact profile and UTF-8 byte limits.

## `targetCatalogJson` (type: `string`):

Own mode only. Leave absent in demo. Runtime enforces exact profile and UTF-8 byte limits.

## `useDemo` (type: `boolean`):

Use the included synthetic catalogs. Omit all own-input fields in demo mode.

## Actor input object example

```json
{
  "authorizedNonpersonalNonconfidentialData": false,
  "useDemo": true
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "useDemo": true
};

// Run the Actor and wait for it to finish
const run = await client.actor("immemorial_sarinda/localization-placeholder-parity").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "useDemo": True }

# Run the Actor and wait for it to finish
run = client.actor("immemorial_sarinda/localization-placeholder-parity").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "useDemo": true
}' |
apify call immemorial_sarinda/localization-placeholder-parity --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,immemorial_sarinda/localization-placeholder-parity"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/ytINrZf0H3FhbjohZ/builds/FUtRaTS7AabIrJtiA/openapi.json