Documentation
API Key Format
Every agimem key has a fixed, self-describing shape so leaked keys are easy to detect and revoke.
Anatomy of a key
Keys always start with agm_ and are always 40 characters long, using only letters and digits.
agm_cfNKOwErveDE1mr2jiixPq60AWsmg304cMVS| Part | Length | Description |
|---|---|---|
| agm_ | 4 | Fixed prefix identifying an agimem key |
| body | 30 | Random characters from [0-9A-Za-z] (~178 bits of entropy) |
| checksum | 6 | Base62-encoded CRC-32 of the body |
Writing a detection rule
The format is designed so you can add your own rule to a secret scanner, pre-commit hook, CI check, or log redactor. Match candidates with this pattern:
agm_[0-9A-Za-z]{36}To eliminate false positives, verify the checksum offline: decode the final 6 characters as a base62 integer and compare it with the CRC-32 of the preceding 30 characters. A match is a real agimem key.
Using your key
Pass the key as a bearer token — see the MCP API or REST API reference for details, including the roles a key can have.