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

device-authorization/api-methods

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

Device code endpoint - POST /device/code

Endpoint to request device and user codes. Request type: client_id (string, required), scope (string, optional, space-separated list of requested scopes), user_id (string, optional, pre-bind the device code to a specific user). Response includes user_code, verification_uri, and verification_uri_complete.

Device token endpoint - POST /device/token

Endpoint to poll for access token. Request type: grant_type (string, required, must be 'urn:ietf:params:oauth:grant-type:device_code'), device_code (string, required, the device code from initial request), client_id (string, required, the OAuth client identifier).

Device code verification - GET /device

Endpoint to validate a user code. The verification request claims the pending device code for the calling session. Users must be authenticated when calling this endpoint because the verification step binds the pending device code to that session. Only the same session can later approve or deny the code.

Device approval endpoint - POST /device/approve

Endpoint to approve device authorization. Requires authentication. Request parameter: userCode (string, required, the user code to approve).

Device denial endpoint - POST /device/deny

Endpoint to deny device authorization. Requires authentication. Request parameter: userCode (string, required, the user code to deny).

Device Authorization client methods

Client methods added by deviceAuthorizationClient plugin: device() (verify user code validity), device.code() (request device and user codes), device.token() (poll for access token), device.approve() (approve device, requires authentication), device.deny() (deny device, requires authentication).

Give your agent this brain