# Jorjar Jorjar is a personal assistant. Authorized agents can submit tasks and read their own results through the versioned HTTP API. Use the API instead of automating the dashboard when it covers your task. - [Automation guide](/support#automation) - [Token management: Your workspace → Automation tokens](/dashboard) - [OpenAPI 3.1 specification](/openapi.json) - [Features](/support#features) - [Privacy](/privacy) An owner signs in and explicitly creates an expiring automation token. Send it only in the Authorization: Bearer header to the same Jorjar origin. A token permits task creation (a task can change anything the owner could ask for in chat, such as what happens when an AI account hits a limit), reading only its own tasks, and reading or changing the assistant's own profile picture; it is not an account-administration or vault-export credential. Do not ask for the owner's Jorjar password. POST /api/v1/tasks with {"id":"","prompt":""}. Keep the ID and exact prompt across retries. Read Location and Retry-After, then GET /api/v1/tasks/{id}. A 202 is acceptance, not completion. A succeeded reply may still describe a human-only blocker; inspect its answer. Follow-ups using the same token share its conversation. Token expiry/revocation rejects future calls and stops accepted work at checked execution boundaries; completed external effects cannot be undone. The assistant's picture: GET /api/v1/assistant/avatar returns {"type","version","data":""} (404 when none). PUT /api/v1/assistant/avatar with {"data":""} changes it everywhere at once: Jorjar's web chat, Slack replies and emails, and the owner's Telegram bot photo in the background. It returns {"version"}; the same picture again keeps the same version. Steps waiting on the owner: GET /api/v1/handovers lists sign-ins Jorjar could not finish by itself (MFA, a captcha, a hand-off to another sign-in provider such as Microsoft) and tasks paused for the owner, each with needs_you {reason, headline, message, provider, control: waiting|watching|controlling}. POST /api/v1/handovers/{id}/done hands a step back: Jorjar checks the page, records the outcome (signed_in, changed, unchanged) and resumes the paused task; 409 while the owner holds control in the take-over view. Take-over links are never returned to tokens. Respect 429 and Retry-After. Account-wide limits: 120 requests/minute, 10 new tasks/minute, 500 new tasks/day; 64 KiB task bodies (pictures up to 1 MiB) and 16000-character prompts. No automated challenge is required on authenticated API routes. Private pages and APIs are not public crawling surfaces.