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

# Linking Accounts

> Merge two Agentcard accounts, or add a second email or phone to one

If the same person ends up with two Agentcard accounts (one under an old email, one under a phone number), linking joins them into a single account. You prove you control the other identifier with a one-time code, then one of two things happens:

* **The identifier belongs to another Agentcard account**: the two accounts **merge**. Cards, balance, identity verification, and history all end up on one account, and both identifiers sign in to it afterwards.
* **Nothing uses the identifier yet**: it is simply added to your current account as a second email or phone.

## When you need this

* **Identity verification was rejected as a duplicate.** Your documents are already verified on another Agentcard account, so re-submitting them can never succeed. Linking that account is the fix: after the merge your verification carries over, with no new documents needed.
* **You want one account.** You signed up twice (a different email, or email vs. phone) and want your cards, balance, and history in one place.

## How to link

<Tabs>
  <Tab title="Verify page">
    When verification is rejected as a duplicate, the verification page at [app.agentcard.sh/dashboard/verify](https://app.agentcard.sh/dashboard/verify) shows a **Link that account** flow inline: enter the other account's email or phone, then the one-time code it receives.
  </Tab>

  <Tab title="CLI">
    ```bash theme={null}
    agent-cards account link                    # prompts for the other email or phone
    agent-cards account link you@old-email.com  # or pass it directly
    ```

    The `agent-cards kyc` flow prints this command when it hits a duplicate rejection.
  </Tab>

  <Tab title="MCP">
    The `link_account` tool runs the same two steps: call it with `{ type: "email" | "phone", identifier }` to send the code, then again with `{ ticket, code }` to verify it.
  </Tab>
</Tabs>

## Merge semantics

* The **identity-verified account survives**; the other folds into it.
* Cards, cash balance, verification, and history all live on the surviving account. Nothing is lost.
* **Both identifiers sign in** to the merged account, so your current login keeps working.

## If both accounts are verified

A merge between two accounts that have **both** completed identity verification is refused (`both_kyc_approved`). That one is a support case: email [support@agentcard.sh](mailto:support@agentcard.sh).