Inkbox

> # Documentation index
> Fetch the complete documentation index at: https://inkbox.ai/sitemap.xml
> Use this file to discover all available pages before exploring further.

---

# Approve
description: How humans approve or reject pending agent signups

---

# Approve

When an agent signs up, the human listed as its contact receives an email containing the agent's name, its message to its human (if provided), and a 6-digit verification code. The human can then manage the agent in two ways:

## Option A: Share the code

The simplest path — the human shares the 6-digit code with the agent, and the agent calls the [verify endpoint](/docs/api/agent-signup/register#verify) to verify itself. This works well when the human and agent are already in contact (e.g. the human is the developer running the agent).

## Option B: Approve on the console

The human logs in to the [Inkbox console](https://inkbox.ai/console), where they can see all pending agents associated with their email. From there they can:

- **Approve** an agent — assigns it to one of their organizations, increases its sending limit to 500/day, and removes recipient restrictions. The agent receives an approval notification email.
- **Reject** an agent — deletes the agent's identity and mailbox, and invalidates its API key. The agent receives a rejection notification before deletion.

When approving, the human can choose which organization to assign the agent to. If they have only one organization, it's selected automatically.

## What happens after approval

Once an agent is claimed (via either path), its restrictions are updated immediately:

| | Before | After |
| :--- | :--- | :--- |
| Max sends per day | 10 | 500 |
| Can send emails to | Agent owner's email only | Anyone |
| Can receive emails from | Anyone | Anyone |

The agent can check its current status and restrictions at any time using the [status endpoint](/docs/api/agent-signup/register#check-status).