Your own inbox.
One API path.

Call POST /v1/agent-signups

Use a stable, unique idempotency key. The operator email must belong to the responsible human and must not be the inbox you are creating.

curl -sS -X POST https://api.reverbin.com/v1/agent-signups \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: <stable-unique-key>' \
  -d '{
    "requester_email": "operator@example.com",
    "agent_name": "<agent-name>",
    "agent_use_case": "<what-this-agent-needs-email-for>",
    "preferred_inbox_name": "<desired-local-part>"
  }'

Capture the one-time credentials privately

Save the returned API key and inbox identifiers directly into your secret store or protected environment. Do not include the key in logs, chat, reports, or tool output.

REVERBIN_BASE_URL=https://api.reverbin.com
REVERBIN_API_KEY=<one-time-api-key>
REVERBIN_INBOX_ID=<inbox-id>
REVERBIN_INBOX_EMAIL=<inbox-address>

Submit POST /v1/agent-signups/verify

Reverbin emails a six-digit OTP to the operator. Until verification, the API key can read its inbox and send only to that operator address. Ask the operator for the code through your existing trusted channel, then verify it.

curl -sS -X POST https://api.reverbin.com/v1/agent-signups/verify \
  -H "Authorization: Bearer ${REVERBIN_API_KEY}" \
  -H 'Content-Type: application/json' \
  -d '{"otp_code":"<six-digit-code>"}'

Read the inbox through the API

After verification, use the same API key. Confirm authenticated access with GET /v1/inboxes/{id}/threads.

curl -sS "${REVERBIN_BASE_URL}/v1/inboxes/${REVERBIN_INBOX_ID}/threads" \
  -H "Authorization: Bearer ${REVERBIN_API_KEY}"

Return only the safe outcome

Report only the inbox address. Never report the API key, credential response, OTP, or secret-manager contents.