> For the complete documentation index, see [llms.txt](https://doc.youverify.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.youverify.co/guides-and-solutions/guides.md).

# Guides

Task-oriented walkthroughs ("how do I…"). Guides are how-to; audience and value live in the Overview, so there is no separate use-case catalogue to keep in sync.

<table data-view="cards"><thead><tr><th></th></tr></thead><tbody><tr><td><h4>Onboard an individual</h4><p>Add the individual, run KYC (<mark style="color:$primary;"><code>/identity</code></mark>) with SDK liveness/document capture, AML-screen for the score; an onboarding agent approves or escalates.</p></td></tr><tr><td><h4>Onboard a business + UBOs</h4><p>Premium KYB (<mark style="color:$primary;"><code>/company</code></mark>) pulls the registry record and UBOs; promote owners or send data requests; AML-screen business and owners.</p></td></tr><tr><td><h4>Onboard by email (PSP / downstream)</h4><p>Add a merchant/fintech as a downstream entity (<mark style="color:$primary;"><code>parentId</code></mark>); model the PSP hierarchy; sub-merchant-level screening meets Visa/Mastercard obligations. <a href="/pages/gP1SlXDX7Uvtxg0C41Rv">Open →</a></p></td></tr><tr><td><h4>Create a case from signals &#x26; events</h4><p>Pull a signal and its events, open a case on the entity, use Vyra's AI summary, work the 360 evidence.</p></td></tr><tr><td><h4>Create &#x26; publish an AI Agent workflow</h4><p>The general pattern: build from a template, configure checks, score/band rules and escalation, test in sandbox, publish.</p></td></tr><tr><td><h4>Create &#x26; publish a Fraud Trap AI model</h4><p>Start from a fraud scenario, fine-tune against your data to cut false positives, publish and attach to a workflow.</p></td></tr><tr><td><h4>AI workflow to monitor transactions</h4><p>Publish a Transaction Monitoring agent: stream transactions, run Fraud Trap models, raise signals/alerts and escalate.</p></td></tr><tr><td><h4>AI workflow to detect onboarding fraud</h4><p>Publish an Onboarding agent: identity + liveness/deepfake + document + scoring; auto-approve clean, block fraud, escalate the rest.</p></td></tr><tr><td><h4>AI workflow to screen transactions</h4><p>Publish a Transaction Screening agent: sanctions/PEP/watchlist/rules before completion; allow / hold / block inline.</p></td></tr><tr><td><h4>Investigate &#x26; escalate alerts</h4><p>From an alert, open/attach a case, decide on the 360 evidence, escalate to a reviewer, SAR or entity restriction.</p></td></tr><tr><td><h4>Go event-driven (webhooks)</h4><p>Register endpoints, subscribe to event families, verify signatures, return 2xx fast, process async.</p></td></tr><tr><td><h4>Migrate from legacy APIs</h4><p>Replace standalone reports with Add Entity + checks; move KYT to AI workflows; switch polling to webhooks.</p></td></tr></tbody></table>

> Need something beyond these? For tailored or complex scenarios, [contact our experts](https://www.youverify.co/en/company/contact-us).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.youverify.co/guides-and-solutions/guides.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
