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

# Overview

> Every verification scope, grouped by category, with the inputs each needs.

A scope is a single kind of check, run by putting its slug in the request path: `POST /v1/{scope}`. The request body is that scope's inputs. This section lists every scope, grouped by category, with the fields each one takes.

<CardGroup cols={2}>
  <Card title="KYC" icon="id-card" href="/scopes/kyc">
    Individual identity: NIN, BVN, voter's card, passport, bank account, phone.
  </Card>

  <Card title="KYB" icon="building" href="/scopes/kyb">
    Business verification: company search, tax ID, TIN.
  </Card>

  <Card title="Vision" icon="face-viewfinder" href="/scopes/vision">
    Face comparison, face detection, document reading.
  </Card>

  <Card title="AML" icon="shield-halved" href="/scopes/aml">
    Adverse media, PEPs, and sanctions screening.
  </Card>
</CardGroup>

## Reading these pages

For each scope you get its **slug** (what goes in the path), its **inputs** (the body fields), and the **fields it returns**.

<Note>
  The exact fields a scope returns depend on the provider configured for your organization, so the result fields listed are the common ones you can expect, not a frozen schema. Always read the `result` object by key rather than by position, and tolerate a missing optional field.
</Note>

## A note on availability

Listing a scope here does not mean it is active for your organization. Each scope must be [activated](/concepts/scopes-and-activation) before you can run it, and your API key must be allowed to run it. An inactive or disallowed scope returns `403`.