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

# Resend

> Store and use your Resend API key with authsome. Local encrypted vault, proxy injection, no key in the agent's environment.

Resend uses a long-lived API key. Authsome stores the key encrypted in the local vault, injects it at request time through the proxy, and keeps it out of shell history, process listings, and environment dumps.

## At a glance

|                    |                                                            |
| ------------------ | ---------------------------------------------------------- |
| Provider name      | `resend`                                                   |
| Display name       | Resend                                                     |
| Auth type          | API key                                                    |
| Header             | `Authorization: Bearer <key>`                              |
| Proxy host         | `api.resend.com`                                           |
| Env var            | `RESEND_API_KEY`                                           |
| Where to get a key | [https://resend.com/api-keys](https://resend.com/api-keys) |

## Get a key

Create an API key in the Resend dashboard at [https://resend.com/api-keys](https://resend.com/api-keys).

## Log in

```bash theme={null}
authsome login resend
```

A local browser form opens at `http://127.0.0.1:7998`. Paste the key into the masked input and submit.

On a headless machine without a graphical session, authsome falls back to masked terminal input via `getpass`. The browser bridge is skipped automatically when no display is available.

Verify:

```bash theme={null}
authsome get resend --field status
# → connected
```

## Use the key

Run the agent under the proxy (recommended).

<CodeGroup>
  ```bash Proxy (recommended) theme={null}
  authsome run -- python my_agent.py
  ```

  ```bash Environment theme={null}
  eval "$(authsome export resend --format env)"
  echo $RESEND_API_KEY
  ```
</CodeGroup>

Under the proxy, authsome sets `RESEND_API_KEY=authsome-proxy-managed` in the child's environment and injects the real key into outbound requests to `api.resend.com`. The child process never sees the actual value.

## Multiple keys

Pass `--connection <name>` on `login` and on every read command to keep two or more accounts on the same provider side by side. See [Multiple connections per provider](/guides/multiple-connections) for the full pattern.

```bash theme={null}
authsome login resend --connection personal
authsome login resend --connection team
```

## Rotate or remove the key

```bash theme={null}
authsome login resend --force          # rotate
authsome logout resend                  # remove local credential
authsome remove resend                  # remove all local state for the provider
```

API-key providers have no revocation endpoint, so `revoke` and `remove` are equivalent for Resend.

## Override the bundled definition

```bash theme={null}
authsome inspect resend > ~/.authsome/providers/resend.json
# edit fields
authsome list   # source now shows "custom" for resend
```

## What's next

<Columns cols={2}>
  <Card title="Run agents with the proxy" icon="shield-halved" href="/guides/run-agents-with-proxy">
    Keep the key out of the agent's environment entirely.
  </Card>

  <Card title="Multiple connections per provider" icon="users" href="/guides/multiple-connections">
    Keep two or more keys on the same provider side by side.
  </Card>

  <Card title="API-key providers" icon="key" href="/integrations/api-key/index">
    All bundled API-key providers.
  </Card>
</Columns>