> ## Documentation Index
> Fetch the complete documentation index at: https://docs.quiva.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Set your own personal profile

> Writes **the caller's own** profile and nothing else — the storage subject is derived from the bearer token, so no body field can redirect the write at another person. There is no role gate, because this is a person's own data about themselves.

The body is the profile object itself — fields at the top level, never wrapped in a `personal_profile` key. Every field is optional and is trimmed before storage, so a body whose fields are all empty (or all whitespace) clears the profile: the handler then stores an absent `personal_profile` key rather than `{}`, so a fresh user is not permanently blocked from a default seed. Each field is capped at **1000 characters**, counted in runes, and the whole document at **3000** summed across every field. A cap is refused by name at the write, never silently truncated.

The write is a read-modify-write over the whole stored document, so keys this endpoint does not model survive. A failed read is therefore a 502, never a write. Subject: `microstrate.hub.put.coworker-personal-profile`.



## OpenAPI

````yaml /api-reference/endpoint/abbie/openapi.json put /hub/coworker/personal-profile
openapi: 3.1.0
info:
  title: Abbie API (beta)
  version: 1.0.0
  description: >
    **Beta.** This API is in beta: operations and fields may change without a
    deprecation period. Do not depend on undocumented fields. It covers the
    subset of Abbie's API used by the Quiva coworker MCP server: skills, todos,
    memory, profile, corrections, environment and models.


    HTTP surface of hub-service for Abbie/Coworker configuration, agent rapport
    & context, chat-session sharing, and MCP registration.


    ## Transport and response envelope


    Every operation here is a gateway mapping onto a Bellerophon/kraken subject
    of the form `microstrate.hub.<method>.<endpoint-slug>` (see
    `hub-service/service/service.go` and `docs/abbie-gateway-mappings.md`).
    Handlers reply on the mesh with an envelope `{"status_code": <int>, "body":
    <object>}`; the gateway unwraps it, so `status_code` becomes the HTTP status
    and `body` becomes the HTTP response body. **The schemas below describe the
    unwrapped `body`.**


    Errors are always `{"error": "<message>"}` with the matching HTTP status.


    ## Parameter conventions


    The gateway forwards URL parameters to the handler as request headers:


    - `x-param-query-<name>` — a query-string parameter (`?name=value`)

    - `x-param-<name>` — a path parameter


    Every parameter documented as `in: query` or `in: path` below corresponds to
    one of those headers, and the header suffix is named in each parameter's
    description where it is not obvious.


    ## Authentication


    All operations require the caller's bearer token; the account id, user id
    and user public key are always taken from the JWT and never from the URL or
    body. Endpoints that additionally require an account **admin** role are
    marked in their description — a failed role lookup answers **502**, never
    403 and never a pass.


    ## Two path notes


    - `PATCH /hub/agent-session-visibility/{session_id}` — the handler reads the
    path parameter as `x-param-session_id`, matching its sibling `PATCH
    /hub/agent-session/{session_id}`.

    - `GET|POST|PUT /hub/agent/user-context/{id}` — the handler requires the
    **agent id** as `x-param-id`; the frontend calls
    `/hub/agent/user-context/<agentId>`.
servers:
  - url: https://api.quiva.ai
    description: Production API server
security:
  - bearerAuth: []
  - apiKeyAuth: []
tags:
  - name: Skills
  - name: Todos
  - name: Memory
  - name: Profile and personality
  - name: Corrections
  - name: Environment
  - name: Models
paths:
  /hub/coworker/personal-profile:
    put:
      tags:
        - Profile and personality
      summary: Set your own personal profile
      description: >-
        Writes **the caller's own** profile and nothing else — the storage
        subject is derived from the bearer token, so no body field can redirect
        the write at another person. There is no role gate, because this is a
        person's own data about themselves.


        The body is the profile object itself — fields at the top level, never
        wrapped in a `personal_profile` key. Every field is optional and is
        trimmed before storage, so a body whose fields are all empty (or all
        whitespace) clears the profile: the handler then stores an absent
        `personal_profile` key rather than `{}`, so a fresh user is not
        permanently blocked from a default seed. Each field is capped at **1000
        characters**, counted in runes, and the whole document at **3000**
        summed across every field. A cap is refused by name at the write, never
        silently truncated.


        The write is a read-modify-write over the whole stored document, so keys
        this endpoint does not model survive. A failed read is therefore a 502,
        never a write. Subject: `microstrate.hub.put.coworker-personal-profile`.
      operationId: putCoworkerPersonalProfile
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CoworkerPersonalProfile'
      responses:
        '200':
          description: The personal profile as stored
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CoworkerPersonalProfileResponse'
        '400':
          description: >-
            A field or the whole document over its cap, or the write could not
            be published
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '502':
          $ref: '#/components/responses/UpstreamError'
components:
  schemas:
    CoworkerPersonalProfile:
      type: object
      description: >-
        The FROZEN wire shape (docs/abbie-surface-routing-plan.md §1b). Three
        prose fields, deliberately NOT the eight structured rapport keys —
        nothing here duplicates `role`, `preferred_formality`,
        `preferred_length`, `preferred_name`, `preferred_tone`,
        `expertise_level`, `interests` or `language`. Every field is optional;
        absent and `""` mean the same and there is no null. Caps are counted in
        runes and enforced at the write; the whole object is additionally capped
        at 3000 runes summed across every field.
      properties:
        about_me:
          type: string
          maxLength: 1000
          description: Role, context, what you work on
          example: I run vendor onboarding for the north-west region.
        how_i_work:
          type: string
          maxLength: 1000
          description: Working style, accessibility needs, how you want answers
          example: I'm dyslexic — keep paragraphs short and lead with the answer.
        constraints:
          type: string
          maxLength: 1000
          description: Your own always/never rules
          example: Never draft anything to a client without showing me first.
    CoworkerPersonalProfileResponse:
      allOf:
        - $ref: '#/components/schemas/CoworkerPersonalProfile'
        - type: object
          properties:
            is_default:
              type: boolean
              description: >-
                True when every field is empty, so the profile block renders
                nothing at all
    Error:
      type: object
      description: The unwrapped error body. The HTTP status carries the code.
      properties:
        error:
          type: string
      required:
        - error
  responses:
    Unauthorized:
      description: No account (or user) identity in the auth context
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    UpstreamError:
      description: >-
        A backend read or write failed — deliberately not degraded to an empty
        or default answer
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
    apiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.