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

# Point de terminaison compatible OpenAI

> Surface de complétion de discussion OpenAI instantanée : pointez n'importe quel SDK OpenAI vers SecureAI

# Point de terminaison compatible OpenAI

SecureAI expose une surface compatible OpenAI afin que vous puissiez intégrer **n'importe quel SDK OpenAI en modifiant uniquement l'URL de base et la clé API** — aucune modification de code. La pile de sécurité complète SecureAI (authentification par clé API, listes d'autorisation de modèle/index, application de la politique SMLTP + droits, Prompt Shield, PII/DLP, facturation des points et le [moteur de redondance de modèle](/fr/en/api/redundancy)) s'exécute en dessous.

## Point de terminaison

```
POST /api/external/v1/chat/completions
GET  /api/external/v1/models
```

Pointez le `base_url` de votre client OpenAI vers :

```
https://{customer.name}.hiperai.ai/api/external/v1
```

<Info>
  **Zéro-Connaissance uniquement**

  Cette surface ne prend **pas** en charge les RAG/bases de connaissances. Les demandes sont épinglées sur `Zero-Knowledge`. Si vous avez besoin d'une récupération de base de connaissances, utilisez le point de terminaison classique [Chat Completion](/fr/en/api/chat/completions).
</Info>

## Authentification

```bash theme={null}
Authorization: Bearer sk-your-api-key-here
```

## Utilisation d'un SDK OpenAI

\###Python (`openai`)

```python theme={null}
from openai import OpenAI

client = OpenAI(
    api_key="sk-your-api-key-here",
    base_url="https://{customer.name}.hiperai.ai/api/external/v1",
)

resp = client.chat.completions.create(
    model="openai/gpt-5-nano",
    messages=[{"role": "user", "content": "Hello!"}],
    # SecureAI extensions travel via extra_body
    extra_body={
        "smltp_policy": "internal",
        "fallback_models": ["anthropic/claude-sonnet-4"],
    },
)
print(resp.choices[0].message.content)
print(resp.model_extra["secureai"]["served_model"])
```

\###JavaScript (`openai`)

```javascript theme={null}
import OpenAI from 'openai';

const client = new OpenAI({
  apiKey: 'sk-your-api-key-here',
  baseURL: 'https://{customer.name}.hiperai.ai/api/external/v1',
});

const resp = await client.chat.completions.create({
  model: 'openai/gpt-5-nano',
  messages: [{ role: 'user', content: 'Hello!' }],
  // @ts-expect-error — SecureAI extension fields
  smltp_policy: 'internal',
  fallback_models: ['anthropic/claude-sonnet-4'],
});
console.log(resp.choices[0].message.content);
```

## Corps de la demande

Les champs OpenAI standard sont pris en charge. `messages` est requis (il n'y a pas de `prompt` sur cette surface). `max_completion_tokens` est accepté comme alias pour `max_tokens`.

Les paramètres OpenAI suivants sont transmis tels quels au fournisseur :

`tools`, `tool_choice`, `parallel_tool_calls`, `response_format`, `stop`, `top_p`, `frequency_penalty`, `presence_penalty`, `seed`, `logprobs`, `top_logprobs`, `user`.

### Champs d'extension SecureAI

Envoyez-les sous forme de champs de corps supplémentaires (via `extra_body` dans les SDK OpenAI) :

| Champ                        | Descriptif                                                             |
| ---------------------------- | ---------------------------------------------------------------------- |
| `smltp_policy`               | Politique de sécurité SMLTP pour cet appel.                            |
| `prompt_shield`              | `{ enabled?, policy? }` — remplacement du bouclier d'invite par appel. |
| `models` / `fallback_models` | Modèle de chaîne de [redondance](/fr/en/api/redundancy).               |
| `redundancy`                 | `{ timeout_ms, first_token_timeout_ms, on[] }`.                        |
| `user_id`                    | Facturer à un autre utilisateur (admin-gated).                         |

## Réponse

Forme OpenAI standard `chat.completion`, plus un objet d'extension `secureai`.

```json theme={null}
{
  "id": "chatcmpl-1a2b3c...",
  "object": "chat.completion",
  "created": 1705312200,
  "model": "anthropic/claude-sonnet-4",
  "choices": [
    { "index": 0, "message": { "role": "assistant", "content": "Hello!" }, "finish_reason": "stop" }
  ],
  "usage": { "prompt_tokens": 9, "completion_tokens": 3, "total_tokens": 12 },
  "secureai": {
    "served_model": "anthropic/claude-sonnet-4",
    "requested_model": "openai/gpt-5-nano",
    "failover": { "occurred": true, "attempts": [ ... ] },
    "smltp_policy_used": "internal",
    "smltp_policy_source": "request",
    "smltp_policy_hash": "a1b2c3...",
    "prompt_shield_policy": null,
    "smltp_bundle_id": "bnd_..."
  }
}
```

`secureai.smltp_bundle_id` (lorsqu'il est présent) peut être échangé contre un \[reçu] de conformité signé (/fr/en/api/receipts).

### Diffusion

Réglez `stream: true`. Les cadres sont des objets natifs OpenAI `chat.completion.chunk` terminés par `data: [DONE]`. L'extension `secureai` est attachée au **premier** morceau. `choices` (y compris les deltas `tool_calls` et `finish_reason`) traversent intacts.

## Erreurs

Les erreurs de ce gestionnaire utilisent l'enveloppe OpenAI :

```json theme={null}
{ "error": { "message": "you must provide a model parameter", "type": "invalid_request_error", "code": null } }
```

Lorsqu'une chaîne de redondance entière échoue, l'erreur utilise `code: "all_models_failed"` et l'état `429` (toutes les limites de débit) ou `502` (sinon). Les rejets de middleware de sécurité conservent la forme SecureAI `{ "success": false, ... }` ; les deux portent toujours un `message`.

## Connexes

* [Chat Completion](/fr/en/api/chat/completions) — la surface classique (ajoute RAG).
* [Redondance & Failover](/fr/en/api/redundancy)
* [API Prompt Shield](/fr/en/api/threat-defense/prompt-shield)


## OpenAPI

````yaml POST /v1/chat/completions
openapi: 3.0.3
info:
  title: SecureAI External API
  description: >
    SecureAI External API provides AI chat completion and image generation
    capabilities with knowledge base retrieval, 

    security policies, and comprehensive usage tracking. This API is designed
    for external developers 

    and integrations using API key authentication.


    ## Key Features

    - **RAG (Retrieval-Augmented Generation)**: Automatically search knowledge
    bases for relevant context

    - **Multi-Model Support**: OpenAI, Anthropic, Google, Meta, and other AI
    models

    - **Model Redundancy & Failover**: Caller-defined failover chains (primary +
    fallbacks) with per-attempt timeouts

    - **OpenAI-Compatible Endpoint**: Point any OpenAI SDK at `/api/external/v1`
    — no code changes

    - **Image Generation**: Generate and edit images using Google Gemini 2.5
    Flash Image

    - **Speech-to-Speech (S2S)**: Real-time voice conversations using OpenAI
    Realtime API with WebRTC

    - **Security Policies**: SMLTP policy enforcement, per-call Prompt Shield,
    and signed compliance receipts

    - **Usage Tracking**: Comprehensive usage monitoring, self-service quota,
    and rate limiting

    - **Knowledge Base Integration**: Access to personal and shared knowledge
    bases

    - **User Management**: Complete user, group, and role management
    capabilities

    - **Audit Logging**: Comprehensive activity and security audit logs


    ## Authentication

    All endpoints (except health check) require API key authentication using
    Bearer token:

    ```

    Authorization: Bearer sk-your-api-key-here

    ```


    ## Billing and Usage

    By default, API requests are billed to the user account that owns the API
    key. You can specify 

    a different user to bill by including the `user_id` parameter in your
    request. This allows for:

    - Multi-tenant applications with per-user billing

    - Flexible completion limit management

    - Per-user "Usage by Model" settings


    ## Rate Limits

    - Default: 60 requests per minute, 1000 requests per hour

    - Daily limits: 100 requests (configurable)

    - Monthly limits: 10,000 requests (configurable)


    ## Base URL

    ```

    https://secureai.hiperai.ai/api/external

    ```
  version: 1.1.0
  contact:
    name: SecureAI Support
    email: support@secureai.hiperai.ai
  license:
    name: Proprietary
    url: https://secureai.hiperai.ai/terms
servers:
  - url: https://secureai.hiperai.ai/api/external
    description: Production server
  - url: http://localhost:3010/api/external
    description: Development server
security:
  - ApiKeyAuth: []
tags:
  - name: System
    description: System health and status endpoints
  - name: Discovery
    description: Endpoints to discover available models, indexes, and policies
  - name: Chat
    description: AI chat completion endpoints
  - name: User Management
    description: Endpoints for managing user accounts and roles
  - name: Index Management
    description: Endpoints for managing knowledge base indexes
  - name: Group Management
    description: Endpoints for managing user groups
  - name: SMLTP Security
    description: Endpoints for managing SMLTP security policies and audit logs
  - name: Role Management
    description: Endpoints for managing user roles
  - name: Activity Logs
    description: Endpoints for retrieving activity logs
externalDocs:
  description: SecureAI Documentation
  url: https://secureai.hiperai.ai/docs
paths:
  /v1/chat/completions:
    post:
      tags:
        - Chat
      summary: OpenAI-compatible chat completion
      description: >
        Drop-in OpenAI Chat Completions surface. Point any OpenAI SDK's
        `base_url`

        at `/api/external/v1` with a SecureAI API key. Strict OpenAI
        request/response

        shapes (`choices[]`, SSE `data:` frames, `[DONE]`, tool_calls
        passthrough).

        RAG is not available here (pinned to Zero-Knowledge). SecureAI extension

        fields (`smltp_policy`, `prompt_shield`, `models`/`fallback_models`,

        `redundancy`, `user_id`) are accepted as extra body fields and echoed
        back

        in a `secureai` response object.
      operationId: openaiCompatibleChatCompletion
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - model
                - messages
              properties:
                model:
                  type: string
                  example: openai/gpt-5-nano
                messages:
                  type: array
                  items:
                    type: object
                    properties:
                      role:
                        type: string
                        enum:
                          - system
                          - user
                          - assistant
                      content:
                        type: string
                temperature:
                  type: number
                max_tokens:
                  type: integer
                stream:
                  type: boolean
                models:
                  type: array
                  items:
                    type: string
                fallback_models:
                  type: array
                  items:
                    type: string
                redundancy:
                  type: object
                  description: '{ timeout_ms, first_token_timeout_ms, on[] }'
                smltp_policy:
                  type: string
                prompt_shield:
                  type: object
                  description: '{ enabled?, policy? } per-call Prompt Shield override'
      responses:
        '200':
          description: OpenAI chat.completion object plus a `secureai` extension
        '400':
          description: Invalid request (OpenAI error envelope)
        '401':
          description: Invalid API key
        '429':
          description: Rate limited (or all models rate-limited)
        '502':
          description: All model attempts in the redundancy chain failed
      security:
        - ApiKeyAuth: []
components:
  securitySchemes:
    ApiKeyAuth:
      type: http
      scheme: bearer
      description: |
        API key authentication using Bearer token format.
        Example: `Authorization: Bearer sk-your-api-key-here`

````