Counterparty and business due diligence investigations

Sweat AI is an AI-native BPO for banks and fintechs, and Check is the investigation product behind our work, available on its own at check.getsweat.ai. You name a business and state what must be established. Check plans the research, gathers evidence from registries, sanctions lists, the business's own website, public reporting and any documents you authorize, and publishes an evidence packet: cited findings, the limits of each source, and the questions it could not answer.

Use it for counterparty and partner due diligence, enhanced due diligence on a business applicant, or a focused factual question about a company. When you want analysts to run the queue for you, the same evidence format underpins our managed KYB review.

When a business needs an investigation

Routine KYB answers routine questions. Some situations need more:

• A new counterparty or partner. A supplier, a payment partner, a reseller or an acquisition target, where you need to know who is behind the business and whether the public record supports what they tell you.
• Enhanced due diligence. A higher-risk business applicant, where your policy calls for a deeper look at ownership, activity and reputation.
• A specific question. "Is this the same company that was sued in 2023?" or "Who are the directors of this entity's parent?" Check supports a focused-research scope for bounded factual questions that do not ask for an onboarding recommendation.
• Partner readiness. A business preparing to work with a particular payments or banking provider, where you need to see which of that provider's requirements the evidence already supports; see stablecoin and crypto.

Scope: what Check can reach

What follows is what Check may use, as stated in its published contract. Coverage is what the engine can dispatch on a run, not a promise about what a particular run found. Each packet records which sources were actually reached.

Check treats the legal name and domains you provide as claims to test against the evidence.

Output: the evidence packet

Each investigation publishes a structured packet:

• Findings, each with supporting citations. A claim without a citation is not included.
• Sources, each with its URL, capture time and content hash, addressed to the stable location of the record.
• Screening records, per list: capture date, content hash, rows read, matches and completeness. A list that could not be read is recorded as partial or not run, with the reason.
• Gaps: what could not be established, and why. A source that was reached and held no record is recorded differently from a source that could not be reached.
• Entities: the resolved ownership and relationship graph, with unresolved nodes labelled.
• An optional assessment: a typed recommendation (approve, approve with conditions, escalate, pause pending documents, decline or not assessed), an overall risk level and a one-sentence reason. It is a recommendation your team can override. It is never a decision.

Allegations are kept apart from findings: a dismissed charge is reported as dismissed. The packet can be downloaded as a self-contained HTML file with the report text, excerpts, hashes and capture times, and printed or saved as PDF.

For a walk-through of how findings, limitations and a request list read in practice, see the illustrative sample KYB review.

What an investigation does not establish

Being clear about limits is part of the product.

• It is not a clearance. A ready status means the packet has no recorded open gaps. It does not mean the subject is acceptable.
• It is not independently reviewed. Packets are published after automated schema, evidence and source checks. Publication does not include a separate independent review, and the packet records that.
• A zero-match screen is an observation. "No match on the lists we read" is not the same as "unsanctioned", and it does not replace your own screening obligations.
• Absence of evidence is not evidence of absence. If a source was unreachable, the packet says so.
• Public findings do not complete identity checks. Protected identity verification, ownership attestations and tax-identifier verification need the applicant or your own tools.
• Provider mappings are not approvals. Check can read a published packet against a named provider's onboarding requirements and mark each as satisfied, partial, missing or discrepant. That is an evidence assessment. It does not submit anything, and it is not the provider's decision.
• It is not for consumer decisions. Output is not a consumer report under the FCRA and must not be used for consumer credit, insurance, employment, housing or tenancy decisions (Terms).

How a check runs

1. You state the objective. What must be established, the subject's name, jurisdiction, registration number and website where known, and any documents you authorize.
2. Check plans and investigates. It gathers evidence within the limits you set: a cost ceiling and a wall-clock limit. The default profile runs for up to five minutes; a deep profile runs for up to 29 minutes.
3. It asks when it is blocked. If it needs an answer or a record only you have, it pauses and says what is missing. You answer and it continues with the evidence already gathered.
4. It publishes the packet. You, or your reviewer, read the evidence and record a decision: approve, decline, escalate or request documents. Only a signed-in person on your team can record a human decision.
5. You can recheck later. A recheck runs the case again against current records.

For developers and AI agents

Check has an API for applications and agents. The contract is written to be read by an agent: check.getsweat.ai/ai. It covers creating a check with an idempotency key, polling or receiving signed callbacks, answering a blocking question, reading the packet, and the meaning of every status and failure code. It also documents a synchronous document check that tells an onboarding form, at upload, whether a file is the right document for its slot.

Start a check, or have us run them

Sign up at check.getsweat.ai to run investigations yourself, or read the agent contract to connect it to your own systems. If you would rather hand the whole queue to a team that works it 24/7 and hands back reviewed packets, talk to us about KYB review. How the managed service runs end to end is on how it works.