Build with Emily.

1. 1

   First conversations

   Emily starts learning what matters to the people using your app. Only information that passes her three checks becomes a memory.

2. 2

   Over weeks and months

   Conversations build on each other. Emily recalls earlier decisions and context without your app resending them.

3. 3

   At any time

   People can open a memory and ask Emily why she holds it, what it connects to and how confident she is.

How the pieces fit

Want to offer Emily to your own customers under your brand? See white label. Where your interface runs, for example on a developer's laptop while you build or on your own server in production, is agreed when we issue your access. Sign-in always goes through Robson.

Browser interface → your per-user backend → Emily HTTPS API
                         │
                         └─ stores this person's Emily SDK tokens

Person's browser → Emily sign-in and approval page (Robson)

1. Connect an account (device approval with PKCE)

Your backend creates a PKCE verifier and S256 challenge, starts a device request, and shows the person the verification link. They approve on Emily's hosted page; your backend polls for the tokens.

POST /auth/sdk/device
Content-Type: application/json

{
  "code_challenge": "{BASE64URL_SHA256_OF_VERIFIER}",
  "code_challenge_method": "S256",
  "device_name": "Example Companion Web"
}

→ device_code, user_code, expires_in,
  interval, verification_uri,
  verification_uri_complete

POST /auth/sdk/device/token
Content-Type: application/json

{
  "device_code": "{DEVICE_CODE}",
  "code_verifier": "{ORIGINAL_PKCE_VERIFIER}"
}

→ access_token, refresh_token, token_type,
  expires_in, expires_at, issuer,
  user { id, email, name }

While the person has not answered, polling returns authorization_pending; on slow_down, wait the returned interval. Stop on denial or expiry, and respect Retry-After. After the exchange, call GET /auth/status and check its user_id matches the token response before binding the connection to your app session.

2. Select the personal Emily

List targets with GET /api/sdk/clones and select only the one entry whose target_kind is account_self and whose clone_id matches account_id. Confirm it with POST /api/sdk/clones/resolve. Keep clone_id as an opaque string; never convert it to a number.

3. Send a message and stream the reply

POST /chat/v3
Authorization: Bearer {ACCESS_TOKEN}
Content-Type: application/json
Accept: text/event-stream

{
  "message": "Hello Emily",
  "session_id": "{SESSION_ID}",
  "client_turn_id": "{CLIENT_TURN_ID}",
  "clone_id": "{ACCOUNT_SELF_CLONE_ID}",
  "history_scope": "continuity"
}

Endpoints