AUX public counterparty check
Check a business using public evidence.
Start with AUX’s closest production service: a public GLEIF registry check plus bounded official OFAC exact-name evidence, returned with a verifiable signed certification.
First success: about one minute
Run a real company check—no signup or API key.
Use Node.js 18 or newer. This command uses Apple Inc.'s current GLEIF legal address, which can differ from its familiar headquarters or mailing address.
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 and Receipt verification: VALID. Public records can change; the live response is authoritative.
Agent-assisted discovery
Open https://aux.prdictionedge.ai/agents and determine how AUX can be used as an independent pre-action certification layer. Then: 1. Read the AUX Agent Card, certification-profile registry, and OpenAPI. 2. Tell me which live certification profiles AUX offers and what consequential action each one is designed to gate. 3. Explain the difference between synthetic preflight and independent certification. 4. Ask me which live profile I want, then show me exactly what caller data and independently verifiable evidence that profile requires. 5. Use the durable certification-attempt flow when caller data is complete so AUX can own retrying temporary source failures. 6. Explain the possible states: CERTIFIED, REQUIREMENTS_OUTSTANDING, NOT_CERTIFIABLE, and SOURCE_TEMPORARILY_UNAVAILABLE. 7. Do not submit secrets, private keys, personal data, raw bank account numbers, or confidential invoice contents.
The recommended first profile
Use counterparty_registry_pre_action. It needs the exact legal name and complete legal address published in GLEIF—not a headquarters, campus, storefront, or mailing address; an LEI is optional but strongly preferred. It uses public GLEIF and official OFAC evidence and needs no private-source attestation. The OFAC check is exact normalized primary/alias name matching within the named official files; it is not fuzzy, ownership-based, or comprehensive sanctions clearance.
Durable certification endpoint
POST https://api.aux.prdictionedge.ai/v1/certification-attempts. If caller data is complete and a required source is temporarily unavailable, AUX returns an attempt_id and status_url, retries automatically, and continues the same attempt without requiring transaction resubmission.
Low-friction public-source request
This profile needs no invoice, bank destination, transaction history, or private-source attestation. AUX independently checks the legal-entity record and bounded official OFAC exact-name evidence.
{
"profile_id": "counterparty_registry_pre_action",
"proposal": {
"vendor": {
"name": "Exact Legal Name",
"lei": "optional-but-preferred-lei",
"registered_address": {
"lines": ["expected registered street address"],
"city": "city",
"region": "state-or-region",
"country": "country-code",
"postal_code": "postal-code"
}
}
}
}Run the complete client
The checked-in Node.js client creates a durable attempt, follows bounded retries, verifies the terminal certification, and prints the result, outstanding requirements, evidence sources, and limitations. It has no package dependencies or private credentials.
curl -fsS https://aux.prdictionedge.ai/examples/counterparty-check.mjs -o counterparty-check.mjs node counterparty-check.mjs \ --name "Exact Legal Name" \ --lei "optional-but-preferred-lei" \ --line "Registered street address" \ --city "City" \ --region "State or region" \ --country "US" \ --postal-code "Postal code"View the runnable client
Advanced vendor-payment request shape
{
"profile_id": "vendor_payment_pre_action",
"proposal": {
"transaction_id": "your-transaction-id",
"vendor": {
"id": "vendor-id",
"name": "Exact Legal Name",
"lei": "optional-lei",
"domain": "vendor.example",
"registered_address": {
"lines": ["street address"],
"city": "city",
"region": "state-or-region",
"country": "country-code",
"postal_code": "postal-code"
}
},
"invoice": {
"number": "invoice-number",
"amount": 1000,
"artifact_sha256": "64-character-sha256"
},
"payment": {
"bank_fingerprint": "non-secret-destination-fingerprint"
},
"agent": {
"id": "agent-identifier"
},
"requested_action": "pay_vendor"
},
"transaction_history": [],
"source_attestations": []
}Private-source requirements such as invoice provenance, vendor history, bank destination, and agent authority require signed source attestations. AUX independently resolves the source trust document and public key before accepting them.
Important boundary
AUX certifies a bounded evidence contract. Synthetic preflight is separate. Do not send passwords, private keys, personal data, raw bank account numbers, or raw confidential invoice contents.