> ## 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.

# Delete an assistant

> Deletes an assistant by {id} (or subject in the body). Genuinely removes it — a second delete returns 404 and it disappears from the list — but a subsequent GET returns a hollow config rather than 404 (see GetAgentResponse).



## OpenAPI

````yaml /api-reference/endpoint/assistants/openapi.json delete /hub/agent/{id}
openapi: 3.0.0
info:
  title: Quiva Assistants API
  x-gateway-name: API Gateway
  description: >-
    API for managing Quiva Assistants. Every endpoint requires either a Bearer
    JWT or an API key — the gateway resolves an API key into the user/account
    context these endpoints read. A restricted API key must explicitly allow the
    /hub/agent* paths it's used against, or requests are rejected before they
    reach this API.
  version: 0.1.1
  contact:
    name: quiva.ai Support
servers:
  - url: https://api.quiva.ai
    description: Production API server
security:
  - bearerAuth: []
  - apiKeyAuth: []
paths:
  /hub/agent/{id}:
    parameters:
      - $ref: '#/components/parameters/agentID'
    delete:
      tags:
        - Assistants
      summary: Delete an assistant
      description: >-
        Deletes an assistant by {id} (or subject in the body). Genuinely removes
        it — a second delete returns 404 and it disappears from the list — but a
        subsequent GET returns a hollow config rather than 404 (see
        GetAgentResponse).
      operationId: deleteAgent
      responses:
        '200':
          description: Assistant deleted successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SuccessResponse'
              example:
                message: success
        '400':
          description: Bad request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                InvalidSubject:
                  value:
                    error: invalid subject
components:
  parameters:
    agentID:
      name: id
      in: path
      description: Assistant id - hash of the original assistant definition
      required: true
      schema:
        type: string
      example: 8f5568aa-c88c-32d7-adfb-8565d367fb24
  schemas:
    SuccessResponse:
      type: object
      properties:
        message:
          type: string
          description: Success message
    ErrorResponse:
      type: object
      properties:
        error:
          type: string
          description: Error message
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: JWT Authorization header using the Bearer scheme.
    apiKeyAuth:
      type: apiKey
      in: header
      name: X-Api-Key
      description: API key authentication via X-Api-Key header.

````