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

# See your Sigil

> Your Sigil is your verified identity; once it is ready, every agent you connect carries proof that a real person stands behind it.

export const waitlists = {
  earlyAccess: "https://sumvin.com/?interest=early_access&utm_source=docs&utm_medium=banner&utm_campaign=early_access#waitlist",
  payments: "https://sumvin.com/?interest=payments&utm_source=docs&utm_medium=banner&utm_campaign=payments#waitlist",
  openBanking: "https://sumvin.com/?interest=open_banking&utm_source=docs&utm_medium=banner&utm_campaign=open_banking#waitlist",
  developers: "https://sumvin.com/developers?interest=cli,agent_plugin&utm_source=docs&utm_medium=banner&utm_campaign=developers#access",
  verifiers: "https://sumvin.com/developers?interest=verifiers&utm_source=docs&utm_medium=banner&utm_campaign=verifiers#access"
};

<Note>
  **Private preview:** this is rolling out and may not be available on your account yet.{waitlists.earlyAccess ? <> <a href={waitlists.earlyAccess}>Request early access →</a></> : null}
</Note>

Your Sigil is your verified identity. Once it is ready, every agent you connect carries proof that a real, verified person stands behind it.

You don't request a Sigil. It is issued to you after [verification](/get-started/first/verify) is approved. This step is where you see it.

## See it

<Tabs>
  <Tab title="In your agent (MCP, recommended)">
    <Steps>
      <Step title="Ask for it">
        Ask your agent to show you your Sigil. It calls `sigil_show`.
      </Step>

      <Step title="Read the state">
        Your agent tells you which state your Sigil is in. The states are listed below.
      </Step>

      <Step title="If it's on its way, ask again later">
        Nothing is pushed to your agent when your Sigil is ready. If it's on its way, ask again shortly; your agent reads the latest state each time.
      </Step>
    </Steps>
  </Tab>

  <Tab title="In the terminal (CLI, for developers)">
    <Steps>
      <Step title="Show it">
        ```bash theme={"theme":{"light":"vitesse-light","dark":"vitesse-dark"}}
        sumvin sigil show
        ```

        When verification is approved, `sumvin kyc status --wait` also prints a line about your Sigil. `sumvin sigil show` gives the full picture.
      </Step>

      <Step title="Read the state">
        The first line names the state:

        ```text theme={"theme":{"light":"vitesse-light","dark":"vitesse-dark"}}
        State: minted
        ```

        For agents and scripts, `sumvin sigil show --json` returns the same answer with the state in `data.state`.
      </Step>
    </Steps>
  </Tab>
</Tabs>

## What your agent shows you

Your agent words it in its own way. When your Sigil is ready, expect something like this:

```text Your Sigil theme={"theme":{"light":"vitesse-light","dark":"vitesse-dark"}}
Your Sigil is ready.

  Sigil          Ready
  Token id       12345
  Issued         1 September 2026, 09:30 UTC
  Verified by    Phone number and identity document
  Stands for     You, a verified person
  Carried by     This agent, and any other agent you connect

From now on, anything I do through Sumvin carries proof that a
verified person stands behind it, and that I act for you.
```

The token id and issue time are your Sigil's public record. When your Sigil is ready, `sigil_show` returns them as `token_id` and `minted_at` (Unix milliseconds). In the terminal, `sumvin sigil show` prints the token id:

```text theme={"theme":{"light":"vitesse-light","dark":"vitesse-dark"}}
State: minted
Sigil minted — token 12345.
Mint status: completed
```

`sumvin sigil show --json` carries it as `data.did_token_id`. You don't need either to use Sumvin.

## What you'll see

| State | What it means | What to do |
| - | - | - |
| **Ready** | Your Sigil exists. | Nothing. Go on to [your first Stamped Mandate](/get-started/first/stamped-mandate). |
| **On its way** | Your Sigil is being issued now. | Check again shortly. |
| **Not issued yet** | You're verified, and your Sigil hasn't been issued. This is a normal answer. | Check again later. |
| **Something went wrong** | Issuing your Sigil didn't succeed, and it won't fix itself. | Email [hello@sumvin.com](mailto:hello@sumvin.com). Asking again won't change it. |
| **Couldn't be read** | Sumvin couldn't read your account right now. This says nothing either way. | Try again. |

If you haven't finished verification, the terminal shows `not_verified` and points you to `sumvin kyc start`. Your agent reports **Not issued yet** in that case, so ask it to check your setup as well. Either way, go back to [Verify](/get-started/first/verify).

<Accordion title="The raw state names">
  | Plain state | From your agent (`sigil_show`) | In the terminal (`sumvin sigil show`) |
  | - | - | - |
  | Ready | `minted` | `minted` |
  | On its way | `mint_in_flight` | `in_flight` |
  | Not issued yet | `mint_not_started` | `not_started` |
  | Something went wrong | `mint_failed` | `failed` |
  | Couldn't be read | `lookup_unavailable` | exits with an error |
  | Not verified yet | `mint_not_started` (your agent can confirm with `onboarding_status`) | `not_verified` |
  | Not recognised by this CLI version | not applicable | `unknown`: upgrade the CLI |
</Accordion>

## What can go wrong

<AccordionGroup>
  <Accordion title="It has said 'on its way' for a long time">
    Keep checking back. If it moves to **Something went wrong**, email [hello@sumvin.com](mailto:hello@sumvin.com).
  </Accordion>

  <Accordion title="It says 'not issued yet' after verification">
    This is an ordinary answer, not a fault. Being verified and having a Sigil are separate facts, and issuing can follow verification. Check again later.
  </Accordion>

  <Accordion title="Your agent keeps waiting on one answer">
    Each check is a fresh read. If your agent treats the first answer as final, ask it to check again.
  </Accordion>
</AccordionGroup>

<Tip>**Try asking your agent:** "Show me my Sigil."</Tip>


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