Crypto Counterparty KYB

What it runs

1. 1
   Sanctions Check

   Source: Dilisense consolidated (OFAC SDN, EU FSF, UN SC, UK Sanctions List, CH SECO, BIS, World Bank, EBRD, ADB + 125 national sanctions/debarment lists; full attribution at https://dilisense.com/en/sources/sanction-sources)

2. 2
   Domain Reputation

   Source: Threat intelligence feeds (multi-source scoring)

3. 3
   SSL Certificate Check

   Source: TLS handshake (X.509 certificate from target server)

4. 4
   WHOIS Lookup

   Source: WHOIS protocol (ICANN-accredited registrar databases)

5. 5
   Email Deliverability Check

   Source: DNS protocol (SPF, DKIM, DMARC record verification) + blacklist check

The answer returns every step’s result, so your agent can show or check each one.

Inputs

How to call it

# Needs an API key. The whole check is charged once, at the listed price.
curl -X POST https://api.strale.io/v1/solutions/crypto-counterparty-kyb/execute \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "inputs": {
      "entity_name": "Circle Internet Financial",
      "entity_website": "https://circle.com"
    },
    "max_price_cents": 180
  }'

# No account. The first request answers 402 with the price in USDC;
# an x402 client pays it from your wallet and repeats the request.
curl -i -X POST https://api.strale.io/x402/v2/solutions/crypto-counterparty-kyb \
  -H 'Content-Type: application/json' \
  -d '{
    "entity_name": "Circle Internet Financial",
    "entity_website": "https://circle.com"
  }'

The bundle’s published example input.

Limitations

• Sanctions lists updated daily from OFAC, EU, and UN sources — newly sanctioned entities may take up to 24 hours to appear

  From step: Sanctions Check

  What to do instead: For same-day compliance, subscribe to OFAC's RSS feed and cross-reference against today's additions

• Name matching uses fuzzy logic — common names may produce false positives. Always verify flagged results

  From step: Sanctions Check

  What to do instead: Filter results by match confidence score and verify flagged entities against the primary sanctions list PDF

• Reputation scores aggregate multiple blocklists — a single listing may not indicate actual malicious activity

  From step: Domain Reputation

  What to do instead: Check which specific blocklist flagged the domain in the response details and verify the listing reason before blocking

• Blocklist data refreshed daily — recently resolved issues may still show negative reputation for 24-48 hours

  From step: Domain Reputation

  What to do instead: If a domain was recently cleaned, re-check after 48 hours and use the trend direction to assess improvement

• Checks the certificate presented on port 443 only — does not verify non-standard TLS configurations

  From step: SSL Certificate Check

  What to do instead: For services on non-standard ports, use ssl-certificate-chain with the specific hostname:port combination

• Some registrars rate-limit WHOIS queries — bulk lookups may see slower response times

  From step: WHOIS Lookup

  What to do instead: Batch lookups with 1-2 second delays between requests, or use the RDAP protocol endpoint when available

• GDPR-redacted registrations (common for EU domains) show limited registrant information

  From step: WHOIS Lookup

  What to do instead: Use the abuse contact email from the WHOIS response to request registrant details through the registrar's disclosure process

• SMTP verification may be blocked by some mail servers — a 'deliverable' result is not guaranteed delivery

  From step: Email Deliverability Check

  What to do instead: Treat SMTP-verified results as 'likely deliverable' and implement bounce handling in your email pipeline for definitive status