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

# Accept Terms

> Record the patient's acceptance of Arlo's Terms of Service and Privacy
Policy and complete onboarding (account status becomes ONBOARDED).

This is a distinct consent step, separate from updating patient info —
call it only after the user has explicitly agreed to the Terms of
Service and Privacy Policy. All required profile fields (firstName,
lastName, birthDate, gender, country, province — and phone for US
patients) must already be saved via PATCH /api/profile/patient,
otherwise this returns an onboardingIncomplete error listing the
missing fields.




## OpenAPI

````yaml POST /api/profile/accept-terms
openapi: 3.1.0
info:
  title: Arlo Health MCP Server
  version: 1.0.0
  description: >
    Healthcare infrastructure for AI agents. Everything an agent needs

    to act in healthcare for its user.


    ## Overview


    This server exposes two interfaces:

    - **MCP** (Model Context Protocol) over streamable HTTP at `/` for AI agents

    - **REST API** at `/api/*` for bots, skills, and direct HTTP clients


    Both interfaces use the same tool handlers and authentication.


    ## Authentication


    OAuth 2.1 with PKCE. All `/api/*` endpoints require a Bearer token.


    Discovery endpoints (no auth required):

    - `/.well-known/oauth-protected-resource`

    - `/.well-known/oauth-authorization-server`

    - `/.well-known/mcp.json` (MCP Server Card)


    ## Service Regions


    Available in Ontario, Canada (`CA-ON`) and California, United States
    (`US-CA`).
  contact:
    name: Arlo Health
    url: https://arlohealth.ai
  license:
    name: Proprietary
    url: https://arlohealth.ai/tos
servers:
  - url: https://mcp.arlohealth.ai
    description: Production MCP Server
security:
  - oauth2:
      - openid
      - profile
      - email
      - offline_access
tags:
  - name: Discovery
    description: MCP and OAuth discovery endpoints (no auth required)
  - name: Profile
    description: User profile and patient information
  - name: Consultations
    description: Healthcare consultation management
  - name: Messaging
    description: Conversation messaging and media
  - name: Prescriptions
    description: Prescription and pharmacy management
  - name: Payment
    description: Billing and pay-per-use payment management
  - name: Webhooks
    description: Webhook registration and status
paths:
  /api/profile/accept-terms:
    post:
      tags:
        - Profile
      summary: Accept terms and finish onboarding
      description: |
        Record the patient's acceptance of Arlo's Terms of Service and Privacy
        Policy and complete onboarding (account status becomes ONBOARDED).

        This is a distinct consent step, separate from updating patient info —
        call it only after the user has explicitly agreed to the Terms of
        Service and Privacy Policy. All required profile fields (firstName,
        lastName, birthDate, gender, country, province — and phone for US
        patients) must already be saved via PATCH /api/profile/patient,
        otherwise this returns an onboardingIncomplete error listing the
        missing fields.
      operationId: acceptTerms
      responses:
        '200':
          description: Terms accepted, onboarding complete
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                  onboardingComplete:
                    type: boolean
                  status:
                    type: string
                    enum:
                      - ONBOARDED
                  billingMode:
                    type: string
                    enum:
                      - NONE
                      - PAY_AS_YOU_GO
                      - SUBSCRIPTION
                      - LEGACY
                  paymentStatus:
                    type: string
                    enum:
                      - PENDING
                      - ACTIVE
                      - FAILED
                      - CANCELLED
                      - ACTIVE_UNTIL_EXPIRY
                  nextStep:
                    type: string
                    enum:
                      - create_payment_setup
                      - ready
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
components:
  responses:
    BadRequest:
      description: Invalid request
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    Unauthorized:
      description: Missing or invalid authentication
      content:
        application/json:
          schema:
            type: object
            properties:
              error:
                type: string
              needsAuth:
                type: boolean
  schemas:
    Error:
      type: object
      description: Error response
      properties:
        error:
          type: string
          description: Error code
        reason:
          type: string
          description: Human-readable explanation
        code:
          type: string
          description: Detailed error code
  securitySchemes:
    oauth2:
      type: oauth2
      description: OAuth 2.1 with PKCE
      flows:
        authorizationCode:
          authorizationUrl: /oauth/authorize
          tokenUrl: /oauth/token
          scopes:
            openid: OpenID Connect
            profile: User profile
            email: Email address
            offline_access: Refresh tokens

````