> ## Documentation Index
> Fetch the complete documentation index at: https://docs.amlok.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Coverage considerations

> Understand source permissions, data completeness, and supported workflow boundaries.

AMLOK normalizes information from connected sources and institution-supplied evidence. The fields returned for a request depend on your enabled integrations, product modules, permissions, market, and available history.

## Check integration and resource coverage

Use the [integration status catalog](https://docs.amlok.io/integrations/status.md) for availability and markets. Review [provider coverage](https://docs.amlok.io/data-model/provider-coverage.md), [resource coverage](https://docs.amlok.io/data-model/resource-coverage.md), and [field mappings](https://docs.amlok.io/data-model/field-mappings.md) for the corresponding data references.

A required field defines a valid resource when that resource exists. It does not guarantee that every connected account supplies every resource or optional field. Inspect `data_status`, `missing_fields`, and the returned coverage period before using a result.

## Match evidence to the workflow

| Evidence | Interpretation |
| - | - |
| Bank transactions | Observed deposits and withdrawals; deposits alone do not establish verified gross income or employment. |
| Accounting records | Coverage follows enabled ledger, reporting, tax, and other modules. Invoice access alone does not imply complete financial statements. |
| Balances | A current balance is one observation. Historical metrics require the appropriate observations or an explicitly defined reconstruction. |
| Inventory and held assets | Establish beneficial ownership before treating trust, consigned, or third-party assets as collateral or liquidity. |
| Registry and lien records | Apply the jurisdiction and search scope. A UCC or PPSA search is not a complete real-property title search or valuation. |
| Derived attributes | Use the required evidence, calculation version, and coverage window. Missing prerequisites produce an unavailable result. |

## Permissions and additional sources

Collection, processing, retention, and onward use must follow source permissions and your agreement. Consumer-reporting, credit-bureau, payroll, tax-authority, and property-title workflows require the appropriate sources and permitted purposes.

AMLOK supplies evidence, assessments, and risk alerts. Your institution owns borrower outreach, repayment follow-up, money movement, filings, and changes to credit terms through its own systems.

## Preserve data quality

Keep missing, partial, stale, and conflicting evidence visible in your application. A failed lookup is not a verified no-hit result. Use [normalization rules](https://docs.amlok.io/data-model/normalization-rules.md) and [response conventions](https://docs.amlok.io/api-reference/response-format.md) to interpret the returned data consistently.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.