> For the complete documentation index, see [llms.txt](https://docs.rainbird.ai/rainbird/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rainbird.ai/rainbird/getting-started/use-cases/fraud-identification.md).

# Fraud identification

**Use case:** This tool can identify different types of credit card fraud based on account activity and transactional behaviour.

**End-user:** Fraud case handlers.

**Solution:** a Rainbird agent was deployed that case handlers could use to ask about an account or transaction. The Rainbird Knowledge Map was connected to a datasource to retrieve the relevant account or transaction data, resulting in the case handler not being asked to provide the data themselves. 

**Expertise:** Replicates the expertise and decision making ability of fraud case handlers at financial companies.

**Data:** Data is stored in the Knowledge Map, with case-specific data being stored and retrieved from a datasource at runtime.

<figure><img src="/files/By6IIBzQqE7ZjA6dSHgl" alt="" width="331"><figcaption></figcaption></figure>


---

# 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://docs.rainbird.ai/rainbird/getting-started/use-cases/fraud-identification.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.