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

# Overview

> Maintain an onchain allowlist of verified wallets for your asset

## Onchain Allowlisting

Allowlisting controls which wallets can hold and transact your asset. After a user passes your checks, you add their wallet through the Predicate API, and Predicate writes it to the allowlist on your asset's contracts. You can also remove wallets and retry any that failed.

Predicate operates the allowlisting role on your contracts, so you don't manage signing keys or onchain infrastructure. The dashboard shows your allowlisted addresses, recent activity, and why any wallet failed to be added.

## How It Fits with Identity

* **With Predicate Identity**: users complete KYC or KYB through [Predicate Identity](https://docs.predicate.io/v2/identity/overview.md), and you allowlist their wallet once they pass.
* **With your own KYC provider**: call the allowlisting API directly after your own checks.

## What the API Does

* Add or remove one wallet, or up to 1,000 in a single request
* Read each wallet's status and the reason for any failure
* Retry wallets that failed
* Allowlist a wallet on every chain your asset is deployed on with one request

Supported chains are Stellar and EVM. Some contract formats can't remove a wallet yet. We confirm this during setup.

See the [Allowlisting API reference](https://predicate-network.notion.site/External-API-Stablecoin-Wallet-Onboarding-b9fa44a4a0be4da68247b0eb49a5380b) for endpoints, request formats, and error codes.

## Get Access

Predicate registers your asset and issues your API key. You then grant Predicate the allowlisting role on your contracts. [Contact us](https://predicate.io/contact) to get started.