Use case · Export controls
The denied party won't spell it the way the list does.

Denied-party lists record names as enforcement wrote them down. The purchase order arrives spelled the way a procurement agent wants it read. The gap between the two is the compliance risk.

4+US lists to clear before shipping: Entity List, DPL, SDN, Unverified.BIS / OFAC screening set
Strictliability standard: not knowing the buyer was listed is not a defense.US export enforcement
1 callto score the PO name against every recorded variant of a listed party.Onoma /v1/match
Where the check runs

At vendor onboarding, and on every order after.

Trade compliance screens customers, vendors, freight forwarders, and end users against denied-party lists. Intermediaries and transshipment fronts count on the name check being shallow.

Today

Exact match against evasive names.

  • Listed parties resurface as near-identical shell entities.
  • Transliteration differences between list and paperwork read as different companies.
  • Corporate suffix noise (Ltd, LLC, GmbH) defeats naive matching both ways.
  • Screening logs show "no hit" with no way to prove the check was real.
With Onoma

A check that survives an audit.

  • Cross-script, suffix-aware scoring closes the transliteration gap.
  • Calibrated scores make the escalation rule a written policy, not a feeling.
  • Evidence per score becomes the audit trail for every clearance.
  • Batch endpoint re-screens the vendor master on every list update.
In the flow

Clear the order with evidence attached.

  • Vendor-master re-screens on every list revision.
  • Corporate-name aware: suffixes and holding-structure noise handled.
  • Evidence output doubles as the compliance record.
  • Deterministic scoring: the same check gives the same answer in the audit.
$ curl https://onoma.kineticpartners.org/api/v1/match \
  -H "Authorization: Bearer sk_live_..." \
  -d '{ "a": "Meridian Holdings Ltd.",
        "b": "MERIDIAN HOLDING LIMITED" }'

{ "score": 0.96,
  "verdict": "match",
  "evidence": {
    "script_pair": "latin",
    "normalized": { "a": "meridian holdings",
                    "b": "meridian holding" } } }
Access

Ship with a screen you can defend.

Request access See how it works