RUScan

// API KEYS

API keys

A key is what ties scans to their owner: plan quota, history and reports all hang off it. Two kinds, both free, both created in your account.

KIND 1

apk_live_…

apk_live_… travels as a Bearer token. One secret, minimal moving parts. Fits manual calls and simple pipelines.

KIND 2

apk_mcp_… + secret

A pair: an apk_mcp_… id and a secret. Every request is signed with HMAC-SHA256, a timestamp and a one-time nonce; the secret never travels. The CLI, the MCP server and the GitHub Action all use this.

STORAGE

Masking and the one-time reveal

In the key table the id is masked as apk_mcp_aeca••••8591 with a show toggle. The secret appears once at creation and is never stored: only a hash survives. Close the tab without saving it and the only fix is a new key.

LEAKS

If a key leaks

A leaked key: revoke it in the account (instant) and issue a new one. Old scans stay in history. A leaked v2 secret means the same thing: revoke the whole pair.

NAMES

Why label them

Key names (ci-github, macbook, cursor) exist so that a month later you still know what each pair belongs to.

Create a key in your account →