> For the complete documentation index, see [llms.txt](https://developers.bloomcredit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.bloomcredit.io/data-access/credit-reports/indicators.md).

# Indicators

## Overview

Indicators are flags that indicate if a consumer falls into certain regulatory buckets that require special handling by users of credit data. Some indicators are returned -- when applicable -- for all orders, while other indicators must be explicitly ordered.

## Available Indicators

#### MLA (`mla`)

The MLA (Military Lending Act) indicator is returned if the consumer is registered as being on active duty in the Department of Defense database. Active duty service members are afforded certain protections, including but not limited to caps on interest rates.

The MLA indicator is only returned if the SKU for the requested report includes that data element.

#### OFAC (`ofac`)

The OFAC (Office of Foreign Asset Control) indicator is returned if the consumer appears on the SDN (Specially Designated Nationals) list, and needs special handling by financial institutions.

The OFAC indicator is only returned if the SKU for the requested report includes that data element.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.bloomcredit.io/data-access/credit-reports/indicators.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.