new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Better Auth · Plugins · all subjects

two-factor/backup-codes

3 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Generating backup codes endpoint and parameters

POST /two-factor/generate-backup-codes requires session. Parameters: password (string, optional, required for credential accounts unless allowPasswordless is true). When backup codes are generated, old backup codes are deleted and new ones are generated.

Verifying backup code endpoint and parameters

POST /two-factor/verify-backup-code requires headers. Parameters: code (string, required, a backup code to verify), disableSession (boolean, optional, default false, if true session cookie will not be set), trustDevice (boolean, optional, default true, if true device is trusted for 30 days and refreshed on every sign-in). Once a backup code is used, it is removed from database and cannot be used again.

Viewing backup codes endpoint and parameters

POST /two-factor/view-backup-codes is server-only. Parameters: userId (string or null, optional). Should only be called if the user has a fresh session that was just created. Returns backup codes in response.

Give your agent this brain