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

# Sign up for services

> Create service accounts with your agent's email and save their credentials.

Your agent can use its email to sign up for a service, read the verification
message, and save an API key. It needs a browser or access to the service's
API to fill out forms and follow links.

First check that you can [read the agent's email](/email). If Claude Code,
Pi, or Hermes will handle signup, [connect that client](/setup) and give it
the browser or API access it needs. Use the same Artil agent throughout.

## 1. Find the agent's address

Check the active agent and its email address:

```bash theme={null}
artil auth status
```

Use the address shown in status. To switch agents, follow
[authentication](/authentication).

## 2. Sign up with that address

Enter the address in the service's signup form or API request. Fill in the
required account details and request the verification email.

Complete any consent, CAPTCHA, or additional authentication the service requires.

## 3. Read the verification email

List the inbox, then read the matching message using its ID:

```bash theme={null}
artil email list --limit 10
artil email read "mail:<message-id>"
```

Check that the message matches your signup and any link points to the service
you chose. Enter the code in the signup form or open the verification link.
Finish verification and check that you can open the new account.

If the message has not arrived, list the inbox again after the service sends
it. See [email](/email) for message commands and
[automatic delivery](/automatic-messages) for receiving message notifications.

## 4. Keep the service's credentials

If the service issues an API key, store it as an agent secret.
Members who can access a workspace agent can reveal its secrets, so use a
credential meant for those users. In a terminal, this command prompts for the
value without showing what you type:

```bash theme={null}
artil secrets set SERVICE_API_KEY
```

If another command produces the key, pipe its output into
`artil secrets set SERVICE_API_KEY`. For JSON input, use `--json-path .token`
to read a field named `token`. Add `--json` for JSON output; this also disables
the prompt, so you must supply or pipe the value. See [secrets](/secrets) for
details.

Run `artil secrets list` and check that it includes `SERVICE_API_KEY`.
The list shows names and update times, keeping values hidden.

## 5. Use the account

Link a client or file only if it should receive **all** of this agent's secrets.
For Claude Code, the link uses user-level configuration across projects:

```bash theme={null}
artil secrets link claude-code
```

Start a new Claude Code session if this is its first secret link.
`artil init` already links the local client it connects. Hermes and
project `.env` files are also supported; see [secrets](/secrets) for setup and
refresh instructions.

Use the saved key to make a request to the service. Check that the request
succeeds, and keep the key out of the output.

<Card title="Keep credentials up to date" href="/secrets">
  Choose another destination, refresh a changed key, or unlink and revoke access.
</Card>

## Keep using the account

Login links, account alerts, and password-reset emails arrive in the same
inbox. After changing a password or API key, update the secret stored in Artil.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.