eFile Pack — structured CPSC CPC/GCC validation

Give eFile Pack a structured CSV, TSV, JSON or NDJSON certificate dataset. It validates and normalizes the recorded CPC/GCC facts against CPSC’s seven Children’s Product Certificate elements, then provides an internal registry CSV and an itemized rejection report CSV.

Boundaries

• It does not parse OCR, PDF, or image input.
• It does not file anything with CPSC or CBP, create a PGA Message Set, or create an ACE transaction.
• The internal registry CSV is not a shipment-pack export or a filing-ready government submission.
• It cannot verify a lab’s CPSC acceptance, the existence of test reports, or actual product compliance. It validates the structured facts supplied.
• It is not legal advice.

Input

Unknown fields are rejected, including any URL, path, webhook, proxy, or other egress-shaped field. The Actor is offline apart from the Apify platform APIs it uses to store results and issue a charge. Supply the data exactly once:

Field	Type	Default	Notes
datasetText	string	–	bounded inline structured data; mutually exclusive with datasetKey
datasetKey	string	–	a plain record name in this run’s own key-value store; not a URL or path
format	auto | csv | tsv | json | ndjson	auto	structured input format
includeIncomplete	boolean	false	include records with error findings in the internal registry CSV
failOn	error | warning | never	error	findings threshold for exit code 1
maxRows	integer	50000	hard maximum 500000

Inline data is bounded to 1 MiB. For a larger input, first place the existing structured data in the same run’s key-value store and set datasetKey to its flat record name. eFile Pack never follows a URL or a filesystem path.

Output

Exactly one bounded efilepack/actor-result/1 result is written identically to the default dataset and the OUTPUT key-value record on handled success and handled failure. Raw certificate and contact facts are not duplicated in that JSON; it contains summary counts, findings, and CSV artifact references with SHA-256 digests.

Record	Contents
internal-registry.csv	normalized internal registry CSV; complete records only unless includeIncomplete is true
rejection-report.csv	per-element validation findings

Exit code	Meaning
0	handled result stored; no tripped policy or runtime/input error
1	findings at or above failOn; result and available CSVs are still stored
2	missing, invalid, oversized, or unknown input field
3	runtime or storage failure

Pricing recommendation — not configured or billed

This is a repository recommendation only. No Apify Console monetization is configured, no user has been billed, and this document does not claim otherwise. If this private Actor is ever monetized, the sole proposed per-run event is:

Event	Recommended price	Charged when
certificate-validation-report	$0.18	exactly once after a successful validation result plus its internal registry/rejection CSV records are stored in both dataset and OUTPUT

The recommendation is deliberately one per-run event, not $0.18 per SKU and not a $1.50 “shipment-pack export”: this implementation delivers structured data validation plus an internal registry/rejection report, not a shipment pack, filing, or transaction. Invalid input, findings/policy failures, runtime or storage failures, retries, and resurrects are not charged. An idempotency key is sent for the only possible platform charge, and ACTOR_MAX_TOTAL_CHARGE_USD is checked before it is sent. A charge failure never alters the stored result or its exit code.

Privacy and safety

There are no secret input fields. Platform credentials, when the platform supplies them, are used only by the storage/charging boundary and are never written to a dataset item, OUTPUT, a CSV artifact, or a log. The container runs unprivileged and bounds inline bytes, rows, and JSON depth.