# DMAI GEDCOM Transfer Audit (`dmai/dmai-gedcom-transfer-audit`) Actor Conservative same-version GEDCOM individual-record comparison with hashed report values. No merge or platform certification. - **URL**: https://apify.com/dmai/dmai-gedcom-transfer-audit.md - **Developed by:** [Eric Gordon](https://apify.com/dmai) (community) - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $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 ## DMAI GEDCOM Transfer Discrepancy Audit Compare two authorized exports from the same genealogy file-transfer process. Same-version GEDCOM 5.5.1 or 7.x UTF-8 text is supported. Individuals match by exact XREF first, then by a unique name + birth-date + birth-place fingerprint. Ambiguous and unmatched records remain explicitly unresolved; they are not labeled lost. The report returns one-way record and value hashes plus field labels and counts. It does not echo names, dates, places, notes, sources or raw lines, and performs no merge, family-tree truth judgment, living-person inference or platform certification. Limits: 4 MiB and 100,000 lines per input; 30,000 level-zero records. Unsupported encodings, malformed inputs and version mismatches stop comparison with an explicit report. Oversized input produces a buyer-readable refusal report. Delivery: open the Output tab or Storage to retrieve the REPORT JSON record. One completed report is also written to the dataset. Pricing: $0.10 per completed report, including buyer-readable refusal reports, plus a $0.00005 Actor-start event per GB of memory (minimum one event). Platform usage is included. The minimum permitted buyer run budget is $0.10005. Privacy: original input remains in the private run INPUT store. Hashing output does not remove or encrypt retained input. Supply only data you are authorized to process. Support: preserve the run ID and use a redacted synthetic example when reporting a reproducible defect. Billing/refund requests follow Apify's platform process. No custom genealogy reconciliation or manual file handling is included. # Actor input Schema ## `previousGedcomText` (type: `string`): Authorized original export, UTF-8 text, at most 4 MiB. Comparison requires the same supported GEDCOM version. Prefilled content is a synthetic demonstration; replace it with your authorized file before a real job. ## `currentGedcomText` (type: `string`): Authorized destination export, UTF-8 text, at most 4 MiB. Private values are hashed in the report. Prefilled content is a synthetic demonstration; replace it with your authorized file before a real job. ## Actor input object example ```json { "previousGedcomText": "0 HEAD\n1 SOUR DMAI-SYNTHETIC-QA\n1 GEDC\n2 VERS 7.0\n1 CHAR UTF-8\n0 @I1@ INDI\n1 NAME Example /Person/\n1 BIRT\n2 DATE 1 JAN 1900\n2 PLAC Synthetic Example Town\n0 TRLR\n", "currentGedcomText": "0 HEAD\n1 SOUR DMAI-SYNTHETIC-QA\n1 GEDC\n2 VERS 7.0\n1 CHAR UTF-8\n0 @I1@ INDI\n1 NAME Example /Person/\n1 BIRT\n2 DATE 1 JAN 1900\n2 PLAC Synthetic Example Town\n0 TRLR\n" } ``` # Actor output Schema ## `dataset` (type: `string`): No description ## `report` (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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "previousGedcomText": `0 HEAD 1 SOUR DMAI-SYNTHETIC-QA 1 GEDC 2 VERS 7.0 1 CHAR UTF-8 0 @I1@ INDI 1 NAME Example /Person/ 1 BIRT 2 DATE 1 JAN 1900 2 PLAC Synthetic Example Town 0 TRLR`, "currentGedcomText": `0 HEAD 1 SOUR DMAI-SYNTHETIC-QA 1 GEDC 2 VERS 7.0 1 CHAR UTF-8 0 @I1@ INDI 1 NAME Example /Person/ 1 BIRT 2 DATE 1 JAN 1900 2 PLAC Synthetic Example Town 0 TRLR` }; // Run the Actor and wait for it to finish const run = await client.actor("dmai/dmai-gedcom-transfer-audit").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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "previousGedcomText": """0 HEAD 1 SOUR DMAI-SYNTHETIC-QA 1 GEDC 2 VERS 7.0 1 CHAR UTF-8 0 @I1@ INDI 1 NAME Example /Person/ 1 BIRT 2 DATE 1 JAN 1900 2 PLAC Synthetic Example Town 0 TRLR """, "currentGedcomText": """0 HEAD 1 SOUR DMAI-SYNTHETIC-QA 1 GEDC 2 VERS 7.0 1 CHAR UTF-8 0 @I1@ INDI 1 NAME Example /Person/ 1 BIRT 2 DATE 1 JAN 1900 2 PLAC Synthetic Example Town 0 TRLR """, } # Run the Actor and wait for it to finish run = client.actor("dmai/dmai-gedcom-transfer-audit").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 '{ "previousGedcomText": "0 HEAD\\n1 SOUR DMAI-SYNTHETIC-QA\\n1 GEDC\\n2 VERS 7.0\\n1 CHAR UTF-8\\n0 @I1@ INDI\\n1 NAME Example /Person/\\n1 BIRT\\n2 DATE 1 JAN 1900\\n2 PLAC Synthetic Example Town\\n0 TRLR\\n", "currentGedcomText": "0 HEAD\\n1 SOUR DMAI-SYNTHETIC-QA\\n1 GEDC\\n2 VERS 7.0\\n1 CHAR UTF-8\\n0 @I1@ INDI\\n1 NAME Example /Person/\\n1 BIRT\\n2 DATE 1 JAN 1900\\n2 PLAC Synthetic Example Town\\n0 TRLR\\n" }' | apify call dmai/dmai-gedcom-transfer-audit --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,dmai/dmai-gedcom-transfer-audit" } } } ``` 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 ` 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/XPUYAxgMz5S0QObFu/builds/UeFUdyFKTsah1jBjN/openapi.json