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

# Teach an agent a fact about a contact

> Manually store a fact an agent should remember about a contact, so its retrieval layer treats it exactly like an auto-extracted memory. Supply `contact_id` and the free-text `fact`; control characters are stripped and a per-tenant facts-per-contact cap is enforced (a 409 is returned when the contact is already at the cap or has opted out). Requires an operator role (owner, admin, or developer).



## OpenAPI

````yaml /openapi.yaml post /api/v1/agents/{agentId}/memory
openapi: 3.1.0
info:
  title: Devotel CPaaS API
  description: Orbit by Devotel — Communications Platform as a Service API
  version: 1.0.0
  contact:
    name: Devotel
    url: https://devotel.io
    email: support@devotel.io
  license:
    name: Proprietary
servers:
  - url: https://api.orbit.devotel.io
    description: Production
security:
  - Bearer: []
  - ApiKey: []
tags:
  - name: Messages
    description: >-
      Send and manage messages across all channels (SMS, WhatsApp, RCS, Email,
      Viber, etc.)
  - name: Fax
    description: >-
      List and track fax (MMS/T.38) transmissions on Telnyx-backed fax numbers
      (sending flows through the Messaging API)
  - name: Agents
    description: AI agent creation, configuration, and execution
  - name: Voice
    description: Voice calls, IVR, conferencing, and SIP trunking
  - name: OnCall
    description: On-call rotations and escalation policy planning for incident alerting
  - name: Webhooks
    description: Webhook endpoint management and delivery logs
  - name: Numbers
    description: Phone number search, provisioning, and configuration
  - name: Brand Identity
    description: >-
      Unified cross-channel brand trust posture (10DLC, toll-free, WhatsApp,
      RCS, branded calling, number KYC)
  - name: Contacts
    description: Contact management, segmentation, and lifecycle tracking
  - name: Campaigns
    description: Marketing campaign orchestration and analytics
  - name: Flows
    description: Automation flow builder and execution engine
  - name: Templates
    description: Message template management and approval workflows
  - name: Settings
    description: Organization, channel, and user preference settings
  - name: Verify
    description: OTP generation and verification across channels
  - name: Push
    description: Push notification delivery via FCM and APNs
  - name: Integrations
    description: Third-party service connections and OAuth management
  - name: CDP
    description: >-
      Customer Data Platform — activation surface (CRM object sync, streaming
      destinations, ad-audience activation)
  - name: Files
    description: >-
      Server-to-server media upload, listing, retrieval, and deletion
      (signed-URL backed)
  - name: Commerce
    description: >-
      Omnichannel conversational-commerce — persistent cart + checkout state
      machine, channel-agnostic hosted pay-by-link, native WhatsApp checkout,
      and AP2-style agent payment mandates.
  - name: Sync
    description: >-
      Real-time shared-state primitive (Twilio Sync parity) — Documents, Maps,
      Lists, and ephemeral Streams, with change events relayed over the
      /api/v1/ws/sync WebSocket gateway
paths:
  /api/v1/agents/{agentId}/memory:
    post:
      tags:
        - Agents
      summary: Teach an agent a fact about a contact
      description: >-
        Manually store a fact an agent should remember about a contact, so its
        retrieval layer treats it exactly like an auto-extracted memory. Supply
        `contact_id` and the free-text `fact`; control characters are stripped
        and a per-tenant facts-per-contact cap is enforced (a 409 is returned
        when the contact is already at the cap or has opted out). Requires an
        operator role (owner, admin, or developer).
      parameters:
        - schema:
            type: string
          in: path
          name: agentId
          required: true
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - contact_id
                - fact
              additionalProperties: false
              properties:
                contact_id:
                  type: string
                  minLength: 1
                  maxLength: 200
                  description: Contact the fact is about.
                fact:
                  type: string
                  minLength: 1
                  maxLength: 10000
                  description: The free-text fact body to remember.
                source:
                  type: string
                  enum:
                    - manual
                    - conversation
                  default: manual
                  description: Where the fact originated; drives the dashboard badge.
                importance:
                  type: number
                  minimum: 0
                  maximum: 1
                  description: >-
                    Optional importance weight (0..1). Defaults to 0.9 for
                    manual teaches.
            example:
              contact_id: cont_8xk21p
              fact: Prefers email over phone and only takes calls after 2pm ET.
              source: manual
      responses:
        '201':
          description: The fact was stored.
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: object
                    properties:
                      item:
                        type: object
                        additionalProperties: true
                        description: >-
                          The stored memory item (content PII-masked unless
                          reveal was honoured).
                  meta:
                    $ref: '#/components/schemas/ResponseMeta'
components:
  schemas:
    ResponseMeta:
      type: object
      required:
        - request_id
        - timestamp
      additionalProperties: false
      properties:
        request_id:
          type: string
          description: Unique request identifier (also returned as X-Request-Id header)
        timestamp:
          type: string
          format: date-time
        docs_url:
          type: string
          format: uri
          nullable: true
  securitySchemes:
    Bearer:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: Dashboard JWT token from Clerk
    ApiKey:
      type: apiKey
      name: X-API-Key
      in: header
      description: Server-to-server API key (dv_live_sk_*)

````