New API key format

API keys you create from now on have a new, recognisable shape: they start with agm_ and are always 40 characters long.

Why it matters: the old format was easy to confuse with ordinary configuration text, so it was hard to reliably spot a key that had leaked. The new format is distinctive, always the same length, and includes a built-in check code. That means you can now write a simple detection rule — in your own secret scanning setup, pre-commit hooks, CI checks, or log redaction — that reliably finds an agimem key without flagging unrelated text, so you can revoke it before anyone else uses it.

Every key matches agm_ followed by 36 letters and digits, and the last six characters are a check code derived from the rest of the key — so a rule can confirm a match is a real agimem key rather than a lookalike string.

Do I need to do anything?

No. Existing keys keep working exactly as they are. If you'd like the extra protection, delete your current key in the dashboard and generate a new one, then update it in your MCP client or scripts.