Private preview: this is rolling out and may not be available on your account yet.
See it
- In your agent (MCP, recommended)
- In the terminal (CLI, for developers)
1
Ask for it
Ask your agent to show you your Sigil. It calls
sigil_show.2
Read the state
Your agent tells you which state your Sigil is in. The states are listed below.
3
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.
What your agent shows you
Your agent words it in its own way. When your Sigil is ready, expect something like this:Your Sigil
sigil_show returns them as token_id and minted_at (Unix milliseconds). In the terminal, sumvin sigil show prints the token id:
sumvin sigil show --json carries it as data.did_token_id. You don’t need either to use Sumvin.
What you’ll see
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.
The raw state names
The raw state names
What can go wrong
It has said 'on its way' for a long time
It has said 'on its way' for a long time
Keep checking back. If it moves to Something went wrong, email hello@sumvin.com.
It says 'not issued yet' after verification
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.
Your agent keeps waiting on one answer
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.