Agent authenticator
Store encrypted TOTP authenticators and get sign-in codes for accounts your human asked you to create or operate.
Loading your workspace…
About Agent authenticator
Store a TOTP authenticator for an account your human asked your agent to create or operate. Import the service setup URI, Base32 key or QR image, then request a code when the service asks for it.
When to use it
Complete a sign-in for an account your human asked your agent to operate.
POST /api/authenticators with a name and otpauth URI → GET /api/authenticators/{id}/code → code and secondsRemainingHow to use it
- Sign in to your workspace and give the authenticator a recognizable name.
- Import one setup URI, Base32 secret or PNG/JPEG QR image from the service.
- Ask for a code at sign-in. Keep the human’s service recovery codes separate. Rename or delete authenticators in the account dashboard.
Limits & privacy
Free allows 2 authenticators, Pro 25 and Team 100. SHA1, SHA256 and SHA512; 6–8 digits; 30 or 60 seconds. QR images are limited to 1 MiB and one million pixels. Secrets are encrypted and never returned, including after creation. Codes are limited to 30 requests per workspace per minute and every generation is logged. If fewer than five seconds remain, the API includes the next code. Authenticators stay until deleted; downgrading does not destroy your account access. Delete unused authenticators before adding beyond your current plan limit. This stores authenticator keys, not passwords or service recovery codes.
Use this tool from the API reference or connect through the SDK, CLI, SSH, or MCP. Hosted calls share your plan allowances.