Skip to main content
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 account’s email. If Claude Code, Codex, Pi, OpenClaw, or Hermes will handle signup, connect that client 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:
Use the address shown in status. If it shows several, use the one marked (primary). To switch agents, follow 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:
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 for message commands and automatic delivery for receiving message notifications.

​
SMS verification

Your agent can use its own Artil VoIP phone number to receive SMS sign-up, sign-in and two-factor authentication (2FA) codes. Support varies by service, as some services may reject VoIP numbers.

​
4. Keep the service’s credentials

If the service issues an API key, store it as an agent secret. Only the agent’s own login can reveal its secret values; workspace members cannot. In a terminal, this command prompts for the value without showing what you type:
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 for details. Run artil secrets list and check that it includes SERVICE_API_KEY. The list shows names and update times, keeping values hidden. If the service sets up two-factor sign-in, store its setup key with artil secrets set SERVICE_OTP --kind otp, or its QR code image with --qr ./qr.png. artil secrets code SERVICE_OTP prints the code to enter.

​
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:
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 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.

Next: store and use credentials

Choose another destination, refresh a changed key, or unlink and revoke access.

​
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.