> 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/docs/v2.1/enablement-services/enablement-services-getting-started/attesting-to-tradelines-by-category.md).

# How to Attest Different Tradeline Categories

A tradeline can fall into multiple categories. For each applicable category, the following requirements must be met. The category can be determined by using the [Me](/docs/v2.1/enablement-services/enablement_gql_ref.md#query-me) query, under tradelines > edges > node > category.

## Rent

* Primary Residence Confirmation - the rental property must be confirmed to be the consumer's primary residence by including the `isPrimaryAddress` field in the `rent` agreement, set to `true`
* No Mortgage Confirmation - consumer confirms they do not have an active mortgage by including the `hasOtherMortgageOrRent` field in the `rent` agreement, set to `false`.
* Lease Start Date - required for Metro2 reporting. Included in the `input` via the `leaseStartDate` field.

{% code title="GraphQL" %}

```graphql
mutation OpenRentTradeline {
  openRentTradeline(
    id: "0195dd14-2c8f-7ec3-8b0e-7db586a75df5"
    details: {
      isPrimaryAddress: true
      hasOtherMortgageOrRent: true
      leaseStartDate: "2025-02-20"
    }
  ) {
    tradeline {
      id
      status
      details {
        ... on RentTradelineDetails {
          isPrimaryAddress
          hasOtherMortgageOrRent
          leaseStartDate
        }
      }
    }
  }
}
```

{% endcode %}

## Utility

* Utility Type - consumer selects the type of utility, set via the `UtilityType` property. See [Utility Type](/docs/v2.1/enablement-services/enablement_gql_ref.md#definition-utilitytype) for possible values.
* Primary Residence Confirmation - the rental property must be confirmed to be the consumer's primary residence with including the `isPrimaryAddress` field in the `rent` agreement

{% code title="GraphQL" %}

```graphql
mutation OpenUtilityTradeline {
  openUtilityTradeline(
    id: "808b1fe0-8015-4df5-8bed-89d4acf68213"
    details: { isPrimaryAddress: true, utilityTypes: [WATER] }
  ) {
    tradeline {
      id
      status
      details {
        ... on UtilityTradelineDetails {
          utilityTypes
          isPrimaryAddress
        }
      }
    }
  }
}
```

{% endcode %}

## Telco

* Service Phone Number - the phone number linked to the telecom bill. Set the `servicePhone` field in the mutation to the phone number.

{% code title="GraphQL" %}

```graphql
mutation OpenTelcoTradeline {
  openTelcoTradeline(
    id: "808b1fe0-8015-4df5-8bed-89d4acf68213"
    details: { servicePhone: "+12345678909" }
  ) {
    tradeline {
      id
      status
      details {
        ... on TelcoTradelineDetails {
          servicePhone
        }
      }
    }
  }
}
```

{% endcode %}


---

# 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/docs/v2.1/enablement-services/enablement-services-getting-started/attesting-to-tradelines-by-category.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.