Skip to content
Daaysorn
Esc
navigateopen⌘Jpreview
On this page

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.

You are building Use
App or partner connector /v1/api/* with Bearer tokens
Coding agent for that app Project skill daayos-client + MCP & Ask AI
Runtime assistant inside the OS CapToken + task queue + MCP tool invoke

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. Setting cencoriApiKey needs step-up.

Product surfaces

Need Start here
Mail /v1/api/mail/*
Saved links /v1/api/keeps
Money /v1/api/wallet
Calendar /v1/api/schedule/events
Assistant /v1/api/agi/runs then task queue + /step
Tools /v1/api/mcp/tools/invoke with the CapToken from spawn

AGI task queue

  1. POST /v1/api/agi/runs — keep capToken (shown once). Optional tasks: [{ message }].
  2. POST /v1/api/agi/runs/:runId/tasks — enqueue more work.
  3. PATCH .../tasks/:taskId — edit while queued.
  4. POST .../tasks/reorder — pass every queued id in the new order.
  5. POST .../tasks/:taskId/cancel — drop a queued item.
  6. POST .../step — classifies intent (chat vs ask vs agent). Replies directly for conversation/Q&A (phase: chat), or runs the next queued task (phase: planned or acting). Clients can inspect the routing property to see the intent, complexity, and model used.

For agents

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

Was this page helpful?