> For the complete documentation index, see [llms.txt](https://tradesman.gitbook.io/lv8r-labs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tradesman.gitbook.io/lv8r-labs/shared/contractor-compliance.md).

# Contractor Compliance

{% hint style="info" %}
**Verify once, use everywhere.** Contractor credentialing (LV8R Labs) feeds identity verification (MicroPay) in a single compliance flow across the entire production stack.
{% endhint %}

## Flow

```
tradesman-verify (LV8R Labs)          MicroPay KYC
       │                              │
       ├── Business entity check      ├── Document validation
       ├── Trade license check        ├── Biometric verification
       ├── Risk assessment            ├── Sanctions screening
       │                              │
       └──────── ADI Credential ──────┘
                      │
              Portable identity on
              Accumulate Network
                      │
           ┌──────────┼──────────┐
           │          │          │
         PPCS     BIMHeroDAO   Payment
       Job board   Governance   Settlement
```

## What Gets Verified

| Check                 | Source                              | Brand     |
| --------------------- | ----------------------------------- | --------- |
| Business registration | OpenCorporates (140+ jurisdictions) | LV8R Labs |
| Trade license         | State license board APIs            | LV8R Labs |
| Risk score            | Composite analysis                  | LV8R Labs |
| Identity documents    | Government ID scan                  | MicroPay  |
| Biometrics            | Facial recognition                  | MicroPay  |
| Sanctions             | OFAC, EU lists, PEP databases       | MicroPay  |

## Portable Credential

The ADI credential issued after verification is portable — it works across PPCS (job board access), BIMHeroDAO (governance participation), and MicroPay (payment eligibility). The contractor verifies once and carries proof across every system in the stack.

{% hint style="warning" %}
**The problem we solve** — A plumber licensed in Georgia has to re-prove their identity and qualifications for every new project, every new platform, every new payment processor. The LV8R Labs + MicroPay flow verifies once and issues a credential that travels with the tradesman.
{% endhint %}

→ [tradesman-verify](/lv8r-labs/lv8r-labs/tradesman-verify.md) · [MicroPay KYC](/lv8r-labs/micropay/micropay.md) · [Proof-Triggered Settlement](/lv8r-labs/shared/proof-settlement.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://tradesman.gitbook.io/lv8r-labs/shared/contractor-compliance.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.