> 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.md).

# Credit Data Concepts

## Overview

Credit Reports are the foundation of consumer credit data. An individual's report contains various types of data including personal identifying information such as name, address, social security number, and date of birth. It also includes account information such as the type of credit accounts held, credit limit, outstanding balance, and payment history. Public records information such as bankruptcies, foreclosures, and tax liens are also included. Additionally, credit inquiries made by lenders and other financial institutions are listed in the report. This data in this report is used to calculate credit attributes and model scores.

## Credit Report Data

#### Personal Information

* Name
* Former Names
* Current Address
* Previous Addresses
* Social Security Number
* Date of Birth
* Employer

#### Credit Account Data

* Creditor
* Data opened
* Type of credit
* Credit limit
* Current balance
* Payment history

#### Public Records

* Bankruptcies
* Collections
* Repossessions
* Foreclosures

#### Inquiries

* Soft
* Hard

## Additional Credit Data

In addition to the basic report, there are three other categories of credit data available for use:

* [Attributes](/data-access/credit-reports/attributes.md)
* [Indicators](/data-access/credit-reports/indicators.md)
* [Model Scores](/data-access/credit-reports/model-scores.md)


---

# 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.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.