Build a web or mobile client

Auth, envelopes, and the main /v1/api routes for dashboards and apps.

Build a web or mobile client

Use this when wiring a dashboard or native app to the Account API.

How integrations work

Connect over HTTP. There is no drop-in “battery” or in-process plugin for partners yet.

Future pack marketplaces would still go through CapGate allowlists — not arbitrary code inside the API.

Bases

• Development: https://devospi.daaysorn.com
• Production: https://ospi.daaysorn.com
• Prefix: /v1/api

Interactive docs: /v1/api-reference. Machine-readable: /v1/docs-json.

Sign in once

1. POST /v1/api/auth/sign/up/email or POST /v1/api/auth/sign/in/email
2. Store data.token and data.refreshToken
3. Call APIs with Authorization: Bearer <token>
4. Refresh with POST /v1/api/auth/session/refresh before access expires

Do not call /v1/api/auth/get-session. Use GET /v1/api/user/profile for the signed-in user.

Mobile captcha skip (when captcha is on): send x-client-platform plus x-captcha-mobile-skip. Do not rely on User-Agent alone.

Sensitive changes

Phones, names, PIN, and personal AI API keys need a step-up grant (x-step-up-token from /v1/api/user/step-up/*).

AI models alone: PATCH /v1/api/user/ai-settings without step-up. Fields include chatModel, agiModel, and optimizeFor (cost | balance | intelligence). Setting cencoriApiKey needs step-up.

Product surfaces

Assistant turns (chat / ask / agent)

1. POST /v1/api/agi/runs — keep capToken (shown once). Optional goal / tasks.
2. POST /v1/api/agi/runs/:runId/step with message, capToken, optional mode (auto | chat | agent).
3. Branch on phase:
   • chat / ask — show reply (and optional thinking)
   • planned — show agentPlan.moves, then call /step again to act
   • acting — if action.status is awaiting_confirm, approve or deny the interrupt; otherwise continue /step
   • done — finished
4. Every response includes routing (intent, complexity, model, optimizeFor) — show which model ran.
5. Also handle:
   • skillsUsed — chips for Life OS skills loaded this turn
   • subagents — parallel child runs (spawn via POST …/subagents)
   • bootstrap — missing capability proposal; approve/deny like other interrupts (skill_install / capability_proposal)

See Queue work for the personal assistant for task edit/reorder, skills, subagents, and confirm flows.

For agents

Load the project skill daayos-client (.cursor/skills/daayos-client or .claude/skills/daayos-client), or use MCP & Ask AI.