---
title: "Get an end user's verification"
method: GET
path: "/api/end_users/{end_user_heron_id}/verification"
tags: ["EndUsers"]
---

# Get an end user's verification

`GET /api/end_users/{end_user_heron_id}/verification`

## Request

- Base URL: `https://app.herondata.io`
- URL: `https://app.herondata.io/api/end_users/{end_user_heron_id}/verification`
- Auth: API key in header `x-api-key`

Returns a field-by-field verification of a submission's subjects — the business and its
owners — against every independent source that ran a KYB check for the submission.

For each field, the response gives a `state`, the independent sources consulted, and the
value each returned. States are:

- `verified` — the merchant stated this value and an independent source agrees
- `conflict` — the merchant stated this value and an independent source disagrees
- `not_verified` — no independent source confirmed it
- `blank` — no value was provided on the submission

## Path parameters

- `end_user_heron_id` string, required

## Response `200`

OK

- VerificationResponseSchema
  - `business` BusinessVerification
    - `billing_address` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `business_address` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `business_email` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `business_phone` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `dba` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `display_name` string, nullable: The name a reader shows the subject under.
    - `ein` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `entity_type` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `facebook` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `industry` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `instagram` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `key` string: The details response key for this subject's row, so a reader can open it.
    - `legal_name` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `linkedin` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `standing` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `started_on` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `state_of_incorporation` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `status` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `status_raw` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `subject_type` 'owner' | 'business'
    - `website` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
  - `owners` OwnerVerification[]: Every person the deal's sources put at a share of the company. Ordered by the largest share stated, then the newest application form, then the order they appear on it. An owner stated through the API counts as older than any application form. The ones a form declared come before the ones only a source found.
    - `credit_scores` CreditScoreCheck[]: One check per scoring model, in the order `fico`, `vantagescore`, `unknown`, on the latest score of that model. Sources are compared within one model only. Empty when no source stated a score.
      - `chosen_by` unknown
      - `chosen_score` ChosenCreditScore
        - `bureau` 'equifax' | 'experian' | 'transunion' | 'unknown': The bureau that produced the score; `unknown` when the source did not identify one.
        - `score` integer: The numeric score the source reported.
        - `score_model` 'fico' | 'vantagescore' | 'unknown': The scoring model family; `unknown` when the source did not name one.
        - `score_model_raw` string, nullable: The scoring model as the source named it; null when the source did not identify one.
        - `score_version_raw` string, nullable: The scoring model version as the source stated it, such as `8`; null when it gave none.
        - `scored_on` string, date, nullable: The date the score was calculated, in ISO 8601 format; null when the source did not report one.
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `date_of_birth` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `declared` boolean: False for a person the sources tie to a share of the company the deal never declared them at.
    - `display_name` string, nullable: The name a reader shows the subject under.
    - `driving_licence` DrivingLicence
      - `agreement_score` number, nullable: How far the front and barcode readings agree, from 0 to 1; null when only one side was read.
      - `evidence_level` 'signed_and_corroborated' | 'signed' | 'corroborated' | 'barcode_only' | 'scan_only' | 'unresolved' | 'suspect': How far the document itself can be trusted, from how its sides were read and the barcode signature: signed_and_corroborated, signed, corroborated, barcode_only, scan_only, unresolved or suspect.
      - `expired` boolean: Whether the expiry date has passed.
      - `expires_on` string, date, nullable: The licence expiry date in ISO 8601 format; null when the parse gave none.
      - `flags` string[]: Codes for how the front and barcode readings differed, e.g. names_swapped; an ambiguous licence also carries unresolved_tie.
      - `issued_on` string, date, nullable: The licence issue date in ISO 8601 format; null when the parse gave none.
      - `number` string: The licence number as the document states it.
      - `pairing_status` 'paired' | 'partial_match' | 'ambiguous' | 'front_only' | 'back_only': How the licence's front and barcode readings matched: paired, partial_match, front_only, back_only or ambiguous. An ambiguous reading stays a licence of its own.
      - `signature_outcome` string, nullable: Whether the barcode's issuer signature checked out: valid, invalid, unsigned, not_supported or malformed; null when no barcode was read.
      - `state` string, nullable: The issuing state's two-letter code; null when the parse gave none or it named no single state.
    - `email` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `home_address` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `home_phone` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `key` string: The details response key for this subject's row, so a reader can open it.
    - `linkedin` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `mobile_phone` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `name` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `ownership_percentage` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `position` integer: Their place in the list, which is what `Owner 1` means. Not an identity: owners are ordered by how well attested each is, so a re-run can move someone.
    - `relationship` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `ssn` FieldCheck
      - `chosen_by` unknown
      - `label` string: The field as a reader reads it, such as `Legal business name`.
      - `source_to_verify` unknown
      - `sources` SourceVerification[]: One line per source, in the order this field prefers them.
        - `source` 'tin' | 'sos' | 'court' | 'background_check' | 'web_presence' | 'web_search' | 'bank_statement' | 'void_check' | 'pnl_statement' | 'tax_return' | 'driving_licence' | 'xactus' | 'industry_prediction' | 'generic_industry_prediction' | 'industry_prediction_v2' | 'datamerch' | 'business_profile_search' | 'api' | 'manual' | 'broker_submission' | 'crm' | 'application' | 'email': The source this line speaks for.
        - `source_inputs` object, nullable: What this source was searched on, keyed by the field name in that source's own spelling, such as `ein` and `legal_name` for the IRS or `name` and `state` for the registry. Null where the source was sent nothing, which is every line the deal stated itself: those are the input. **A key present with a null value means the field was sent and its value is not printed; a key absent means the field was not sent.** The two are different answers, and the reason this is a map rather than fixed columns: a background check is searched on an SSN that must never be echoed back, so its key carries no value. Not the same as `value`, which is what the source returned.
        - `value` string, nullable: The one value this source is read on, as it wrote it: the one that met the field's `value` where it states one, and its own leading answer where it does not. Null when it stated nothing, which `verification_status` then explains.
        - `verification_status` 'agree' | 'disagree' | 'stated' | 'silent' | 'not_run' | 'cannot' | 'not_compared': `agree` and `disagree` are this source read against what the deal claimed, not against `value`. `stated` marks the claim itself, which is compared against nothing: the application on every field it can state, and otherwise the first source this field prefers that spoke. `not_compared` marks a source's value on a field that is not verified, listed and compared against nothing. `silent` means the source ran and returned no value for this field, `not_run` that no run of it reached the deal, and `cannot` that this source states no such field at all.
      - `state` 'verified' | 'conflict' | 'not_verified' | 'blank': `verified` when a source independent of the deal confirms what it claimed, `conflict` when any source contradicts it, the deal's own other channels included. `not_verified` means nothing independent confirmed it: nothing else spoke to the claim, or only another channel of the deal restated it, or the deal claimed nothing to check. `blank` means nobody stated a value at all.
      - `value` string, nullable: The best answer the sources hold: the value of the first one this field prefers that stated anything. Not what the deal claimed, which `state` reports on instead, so a field can show a registry's value and read `conflict`. Null when no source stated the field.
    - `subject_type` 'owner' | 'business'

## Other responses

- `404`: End user not found, or verification is not enabled for this account

## Changes

- **2026-11-03** `bd8008e49534`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/herondata/apis/heron-data-api/changes/api/end_users/:end_user_heron_id/verification/get.md)

---

[API](https://skmtc.dev/herondata/apis/heron-data-api.md) - [All operations](https://skmtc.dev/herondata/apis/heron-data-api/llms.txt) - [OpenAPI document](https://skmtc.dev/herondata/apis/heron-data-api/revisions/1ec936e17fef?raw)
