> For the complete documentation index, see [llms.txt](https://help.screena.ai/resources/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.screena.ai/resources/faq/name-matching.md).

# Name Matching

{% content-ref url="/pages/727OVbfKRBZ72ZLFByHN" %}
[Does Screena provide rules-based and/or fuzzy matching capabilities?](/resources/faq/name-matching/does-screena-provide-rules-based-and-or-fuzzy-matching-capabilities.md)
{% endcontent-ref %}

{% content-ref url="/pages/1rJJ2iXHal0xibHznO6x" %}
[Does Screena have any machine learning or AI capabilities?](/resources/faq/name-matching/does-screena-have-any-machine-learning-or-ai-capabilities.md)
{% endcontent-ref %}

{% content-ref url="/pages/St36Xcef326cBaoIV9aa" %}
[What are name cultures and how does Screena handle them?](/resources/faq/name-matching/what-are-name-cultures-and-how-does-screena-handle-them.md)
{% endcontent-ref %}

{% content-ref url="/pages/AhdgXGxefhmUQ9WG2dHL" %}
[How does Screena handle different scripts, diacritics, and transliteration?](/resources/faq/name-matching/how-does-screena-handle-different-scripts-diacritics-and-transliteration.md)
{% endcontent-ref %}

{% content-ref url="/pages/hV4fmp0plStFB3t99viG" %}
[How does Screena handle common names?](/resources/faq/name-matching/how-does-screena-handle-common-names.md)
{% endcontent-ref %}

{% content-ref url="/pages/bEufZtbIa9r5MkPJNtFZ" %}
[How does Screena handle inaccurate data?](/resources/faq/name-matching/how-does-screena-handle-inaccurate-data.md)
{% endcontent-ref %}

{% content-ref url="/pages/jD7A5xz3Jruvrs4SaOvQ" %}
[What methods does Screena use to reduce false positives?](/resources/faq/name-matching/what-methods-does-screena-use-to-reduce-false-positives.md)
{% endcontent-ref %}

{% content-ref url="/pages/yo748ZzNeg3L5v8Mfy7j" %}
[What is the percentage of false positives reduced with the methods used by Screena?](/resources/faq/name-matching/what-is-the-percentage-of-false-positives-reduced-with-the-methods-used-by-screena.md)
{% endcontent-ref %}

{% content-ref url="/pages/o48EE9umvKyvhTsbD9EP" %}
[How does whitelisting work?](/resources/faq/name-matching/how-does-whitelisting-work.md)
{% endcontent-ref %}

{% content-ref url="/pages/HkRhlwNazHvthWxOI53o" %}
[What differentiates pairwise name-matching between Screena One and Screena Plus?](/resources/faq/name-matching/what-differentiates-pairwise-name-matching-between-screena-one-and-screena-plus.md)
{% endcontent-ref %}

{% content-ref url="/pages/xiaW6ZBtOicK4KlqMsbM" %}
[How does secondary attributes-matching work?](/resources/faq/name-matching/how-does-secondary-attributes-matching-work.md)
{% endcontent-ref %}

{% content-ref url="/pages/YYYKR0I2Tb9rYk5XUTvd" %}
[Can Screena match beyond names and allow firms to blacklist identifiers or locations?](/resources/faq/name-matching/can-screena-match-beyond-names-and-allow-firms-to-blacklist-identifiers-or-locations.md)
{% endcontent-ref %}

{% content-ref url="/pages/fPRfJT7YyQdcF87m7zS9" %}
[What is the difference between 'matchingNames' in screening responses and 'names' in 'targetData'?](/resources/faq/name-matching/what-is-the-difference-between-matchingnames-in-screening-responses-and-names-in-targetdata.md)
{% endcontent-ref %}


---

# 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://help.screena.ai/resources/faq/name-matching.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.