Real public-evidence example

Verify a business counterparty before an agent acts.

This example checks Apple Inc. using its current GLEIF legal-entity record and AUX's bounded official OFAC exact-name evidence. It requires no account, API key, payment, or package installation.

Run the complete check

Use Node.js 18 or newer. Copy the command exactly:

curl -fsS https://aux.prdictionedge.ai/examples/counterparty-check.mjs -o counterparty-check.mjs
node counterparty-check.mjs \
  --name "Apple Inc." \
  --lei "HWUPKR0MPOU8FGXBT394" \
  --line "C/O C T Corporation System" \
  --line "330 N. Brand Blvd" \
  --line "Suite 700" \
  --city "Glendale" \
  --region "US-CA" \
  --country "US" \
  --postal-code "91203"

Expected successful conclusion: CERTIFIED with Receipt verification: VALID. Public records can change, so the live result—not this page—is authoritative.

Why the address looks unfamiliar

The current profile binds the submitted company to the legal address in GLEIF, not a familiar headquarters, campus, mailing, or storefront address. The command uses the legal address in Apple's public GLEIF record.

Inspect the source GLEIF record

What AUX proves

  • The submitted legal identity and address match a current GLEIF record.
  • The submitted name has no exact normalized primary or alias match in the official OFAC files used by AUX.
  • The resulting bounded certification receipt has a valid AUX signature.

Limits

This is bounded evidence, not legal or sanctions-compliance advice. OFAC coverage is exact normalized name matching within the named primary and alias files; it is not fuzzy, ownership-based, or comprehensive clearance. AUX does not execute the downstream action.