sumvin sigil

The CLI is for developers. It’s mainly for people building and experimenting on Sumvin. The recommended way to use Sumvin is the MCP connector, or the API if you’re building (docs coming).An agent running in your terminal can approve Stamped Mandates that the CLI signs for you. Never give an unattended agent --yes.

Shows the state of your Sigil — your verified agent identity. This is a read-only group: a Sigil is issued automatically once verification finishes, so there’s nothing to trigger here, only to check.

sumvin sigil show

Needs a signed-in session — see sumvin login. Flags

Flag	Effect
`--json`	Print a result object instead of the formatted view.

The six states

State	Meaning
`not_verified`	You haven’t completed identity verification yet.
`not_started`	You’re verified, but nothing has started yet. This is a normal, common answer — it doesn’t mean anything is wrong.
`in_flight`	Your Sigil is being issued. Check back shortly.
`failed`	Issuing didn’t complete after repeated attempts. This needs support’s attention, not another retry.
`minted`	Your Sigil exists.
`unknown`	This CLI build doesn’t recognise the state your account returned. Update the CLI, or check the Sumvin app.

Example

sumvin sigil show --json

{
  "ok": true,
  "exit_code": 0,
  "command": "sigil show",
  "data": {
    "state": "minted",
    "kyc_status": "approved"
  }
}

data.state is the field to branch on — read it rather than the prose.

Exit codes

0 for any of the six states above, including failed — reading your Sigil’s state is a successful read even when the state itself isn’t good news. 1 if you’re not signed in or the read itself couldn’t complete.

See Sigil for what a Sigil is and why it matters, and sumvin kyc for the verification a Sigil depends on.

MCP server

CLI

Status and errors

The six states

Exit codes

​The six states

​Exit codes

The six states

Exit codes