The agent sends the business name and address to Enigma's /kyb endpoint, which queries over 100 million registrations across all 52 US jurisdictions. Enigma returns the best-matching legal entity with registration details, confidence score, industry classification, and active status. The agent evaluates the match threshold and reports the result during the conversation.

Yes. The agent uses Enigma's Screening Verification endpoint to run watchlist checks against OFAC and other sanctions databases. You define search parameters and the agent submits them mid-conversation. Flagged entities are reported immediately, and clean results allow onboarding to proceed without delay.

Tars requires your Enigma API key, which authenticates requests to both the KYB and Screening endpoints. You generate this key from your Enigma account dashboard. No additional OAuth setup is needed, and you can rotate the key at any time without disrupting the integration.

No. Tars queries Enigma in real time during conversations. Business registration data, watchlist results, and confidence scores are fetched live and used only to respond within the current session. No copies of Enigma verification responses are persisted on Tars servers.

The match_threshold is a confidence score between 0 and 1 that controls how closely a business must match Enigma's records to be returned as a result. A threshold of 0.8 requires a strong match, reducing false positives. A lower threshold returns more potential matches for manual review. You can configure this per your risk tolerance.

Currently, Enigma's KYB dataset covers US businesses exclusively, drawing from official state records across all 50 states, DC, and Puerto Rico. However, the sanctions screening endpoint can screen any entity name against global OFAC watchlists regardless of geography.

Enigma's dashboard requires your team to log in, enter business details, and review results. Tars embeds this directly into the onboarding conversation. The business provides their details, the agent runs the check, and the result comes back before the conversation ends. Verification becomes part of your customer experience, not a back-office step.

Yes. If Enigma returns no match above the configured threshold, the agent informs the applicant that additional documentation may be required and can escalate to a human compliance reviewer. You can customize the no-match workflow to collect alternative business identifiers like EIN or DBA names for a retry.