Public Registry & License Record Parser API

Normalize buyer-supplied public or authorized registry and licence-record URLs into structured JSON with identifiers, status fields, warnings, provenance, and evidence links. Operations, compliance, onboarding, research, and data-integration teams with approved public record URLs. Extract identifiers, statuses, warnings, and original evidence links into a consistent downstream record.

What it does

This Actor normalizes the supported evidence into a default Apify dataset and keeps the original source reference with each buyer-visible result. Its buyer-value event is lookup-result; it uses Apify pay-per-event pricing, so inspect the current Pricing tab and begin with a small validation run.

Supported sources and boundary

• buyer-supplied public or authorized registry and licence record URLs

Only the sources and buyer inputs listed above are supported. The Actor does not bypass login, CAPTCHA, paywalls, robots restrictions, private APIs, or any other access control. It is an independent tool and is not affiliated with the named source platforms or authorities.

Inputs

• startUrls — Required public or buyer-authorized registry-record URLs.
• maxItems — Maximum structured records to write.
• watchlistTerms — Optional identifiers or status terms used to focus supplied records.

Existing saved-task fields remain accepted for backward compatibility. Use Apify's maximum run-charge limit for any live validation run.

Buyer-ready output

• recordId
• identifiers
• status
• warnings
• provenance
• sourceUrl
• unsupportedSourceError
• retrievedAt

Every output preserves source provenance where the input or public source provides it. Unsupported sources return an explicit boundary error instead of an invented record.

First run

{
    "sourceMode": "sample",
    "startUrls": [],
    "maxItems": 1
}

The bundled first-run example is a labelled deterministic demonstration, not proof of current live coverage:

{
    "evidenceType": "authorized_fixture",
    "recordId": "fixture-registry-record-1",
    "status": "observed",
    "sourceUrl": "https://example.org/authorized-registry-fixture"
}

API, dataset, schedules, and webhooks

Use the Apify API or default dataset for programmatic retrieval. Save an input as an Apify task to schedule recurring runs. If the current input schema exposes webhookUrl, it can notify a buyer-controlled endpoint after a completed run; otherwise use Apify webhooks for the task or run.

Common use cases

• Build a source-linked internal review queue.
• Compare repeated signals across a buyer watchlist.
• Export normalized JSON or CSV for an approved downstream workflow.

Limitations and responsible use

This is a parser, not a universal registry lookup. Unsupported sources and access-boundary failures are returned explicitly. It never bypasses login, CAPTCHA, paywalls, robots restrictions, or private access controls.

Support

Include the Actor run ID, the input field names (not secrets), an example source URL when authorized, and the observed output field when contacting Zentra support. Check the current Pricing and API tabs before production-scale runs.