# Providers overview

Choose an approval provider and connect your adapters.

An [approval provider](/docs/concepts/provider) receives proposed tool calls from adapters and decides whether they may run. It can apply policies automatically, ask a person to review a request or combine several steps. The adapter enforces the returned decision before execution.

To get started with AAP, you'll need to pick a provider. You can either use an existing provider or build your own.

## Choose a provider

| Provider | Description                                                                                                     |
| --- |-----------------------------------------------------------------------------------------------------------------|
| [withHuman](https://withhuman.ai) | Open source - approval policies and human review for agent tool calls, with hosted and self-hosted deployments. |

When choosing a provider, consider where approval requests will be stored, who needs to review them and how you will manage instance credentials. Check that its supported approval modes match your adapter and runtime.

## Connect an adapter

1. Set up the provider and configure how requests should be reviewed.
2. Obtain a credential for each agent instance and the provider's complete AAP base URL, including any path prefix.
3. Follow the [adapter setup guide](/docs/adapters/cli#install-an-adapter), then test a harmless call with both an approval and a denial.

The AAP CLI installs adapters using an existing instance token and base URL. Provider enrollment, reviewer routing and approval policies are configured separately. Follow your provider's documentation for setup.

## Implement a provider

You can build your own provider using the same protocol. Start with the [specification overview](/specification/overview), [API overview](/specification/reference/overview) and [provider requirements](/specification/security#provider-requirements).