Device Identity
Each profClaw instance generates a unique Ed25519 key pair on first run (src/auth/device-identity.ts). The public key serves as the device’s identity for attestations and pairing.
GET /api/devices/identity
Get the current device’s public identity.200
POST /api/devices/attest
Create a signed attestation for the current device.200
POST /api/devices/verify
Verify an attestation from another device.Pairing Codes
Pairing codes let a new device (phone, second computer) connect to profClaw without password entry.POST /api/devices/pairing/request
Request a pairing code from the new device side.200
POST /api/devices/pairing/approve
Approve a pending pairing request (from the already-trusted device).POST /api/devices/pairing/reject
Reject a pairing request.GET /api/devices/pairing/status/:requestId
Check if a pairing request has been approved.200
GET /api/devices/pairing/pending
List all pending pairing requests (admin only).QR Pairing
For mobile/desktop onboarding without typing codes:GET /api/devices/pairing/qr
Generate a QR code for the pairing flow.200
GET /api/devices/pairing/status/:requestId until approved.
Cleanup
Related
- Authentication API - Session and OAuth-based authentication
- Security Device Pairing - How device pairing works and security model
- profclaw device - Manage paired devices from the CLI
- Security Overview - Auth modes and trust management