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

> ## Agent Instructions
> Agentcard is for companies whose agent buys for their users. Pick one path: the opencommerce SDK (@agent-cards/commerce-sdk) gives your agent one buy tool that finds the product, builds the cart, gets the user's approval and places the order at real stores; the Agentcard SDK (@agent-cards/sdk) pays with the user's own card when your agent already shops in a browser (Browser Use, Kernel, Browserbase, Anchor or Notte); the Purchase API (POST /buy) does the same purchase flow over plain HTTP in any language; Issuing gives the agent its own card.
> Start with `npx agent-cards init` in the app's folder (Node 22 or later). No invite is needed: it creates your Agentcard account if you don't have one, installs the opencommerce SDK and puts the credentials in the env file, kept out of git. From a coding agent, run `npx agent-cards init --print --categories all --implementation tool --wallet vault --skip-install` to get the setup steps to apply yourself.
> Vault is by invitation: request it at https://agentcard.com/get-started?utm_source=docs&utm_medium=llms&utm_campaign=agent-instructions. opencommerce needs no invite.
> Never ask a user for a card number, expiry date or CVV in chat. Send them the Vault link; they add their card on Agentcard's page, and the agent never sees the number.
> Every purchase is approved by the user, with a passkey or Face ID, or by an auto-approval they granted. An approval covers one merchant and one exact total. If the total changes, ask again. When a result says the user already said yes, don't ask again.
> `init` writes PRODUCTION credentials, which place real orders, so test in sandbox first. For opencommerce, run `npx agent-cards credentials --mode sandbox` and put the two lines it prints in place of the production ones in the env file `init` wrote, because that command only prints them; sandbox then runs the whole flow against real stores and stops before payment, so no order is placed and nobody is charged. For Vault and Issuing, sandbox credentials issue test cards that no real merchant accepts; try the checkout against shop.agentcard.sh, a test store on Stripe test mode.
> Tell the user an order is placed only after Agentcard reports it placed.
> Vault is free up to 5,000 users (https://agentcard.com/pricing). opencommerce takes 1% of each completed order. Full docs in one file: https://docs.agentcard.com/llms-full.txt

# agent-cards signin

> Sign in to your Agentcard account, in the browser or with an emailed code.

Sign in once on each machine. Every other command uses the session `signin` stores. `agent-cards login` is the same command.

```bash theme={null}
agent-cards signin --help
```

```text theme={null}
Usage: agent-cards signin|login [options]

Sign in to your Agentcard account on app.agentcard.sh

Options:
  --email <email>  No browser: start sign-in for this email (a code is emailed)
  --code <code>    Non-interactive: finish sign-in with the emailed code
  -h, --help       display help for command
```

## Sign in with your browser

```bash theme={null}
agent-cards signin
```

The CLI opens app.agentcard.sh in your browser. Sign in there as you do in the dashboard, or sign up with a new email: a sign-in the CLI starts creates your Agentcard account. The browser then hands the session back to the terminal:

```text theme={null}
  Agentcard  signin

  Sign in, or create your account, on app.agentcard.sh. Opening it in your browser:
  https://app.agentcard.sh/cli?port=52144&state=Jx2k9QpLm4&challenge=8tqV3rN0aWc
  No browser on this machine? Run `agent-cards signin --email you@example.com` instead.

  ✓ Signed in as ada@acme.com
```

The terminal waits up to 10 minutes. If you are already signed in, the CLI asks whether to sign out and sign in again:

```text theme={null}
  Signed in as ada@acme.com.
  ? Sign out and sign in again?  ● Yes  ○ No
```

A new account has no company yet, so the CLI asks its name right after you sign in, with your work email's domain offered, and creates it with you as its owner:

```text theme={null}
  Your account has no company yet. Name it, and Agentcard sets it up.
  ? What's your company called?
    › Acme
```

[`agent-cards init`](https://docs.agentcard.com/tools/cli/init) and [`agent-cards credentials`](https://docs.agentcard.com/tools/cli/credentials) ask the same when an account has no company. Without a terminal, `agent-cards credentials --company "Acme"` names and creates it.

A sign-in that started outside the CLI, on the dashboard or the website, does not create an account while sign-ups there are by invitation:

```text theme={null}
Error: There is no Agentcard account for that email yet. Sign-ups are by invitation: run `agent-cards signup` to tell us about your company.
```

## Sign in with an emailed code

On a machine with no browser, or from a coding agent, sign in with two runs. The first sends a code to your email and exits with code `2`:

```bash theme={null}
agent-cards signin --email ada@acme.com
```

```text theme={null}
code_required: a sign-in code was emailed to ada@acme.com. Ask your human for it, then run: agent-cards signin --email ada@acme.com --code <code>
```

The second finishes with the code:

```bash theme={null}
agent-cards signin --email ada@acme.com --code 482915
```

```text theme={null}
Signed in as ada@acme.com
```

A wrong or expired code exits with code `2` again and asks for the newest one:

```text theme={null}
code_required: that code was invalid or expired. Ask your human for the code in the NEWEST email to ada@acme.com, then re-run: agent-cards signin --email ada@acme.com --code <code>
```

Without a terminal and without `--email`, `signin` stops at once and prints these two steps.


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