No Train Add

POST

/v1/ratchet/no-train

curl --request POST \
  --url http://localhost:8000/v1/ratchet/no-train

• Local mock mode (make demo)
• Your gateway (the public demo's host by default)

Register an end user ({"end_user": "<user or safety_identifier>"}) as no-train: from now on that user’s requests are answered as usual but never stored (FR-13.2), whether a request names the user in user or in safety_identifier. Only the HMAC is kept, and it is not returned: the endpoint must not become a way to compute hashes. Open where chat completions are (an opt-out only removes storage); an admin may name a client, or register the user for every client, also those added later (the every-client scope). Whether the end user was registered before (created) is told to an API key or an admin key only: without keys anyone may call this.

Parameters

Header Parameters

x-api-key

Any of:

string

string

null

null

Responses

200

Successful Response

Media typeapplication/json

Response No Train Add V1 Ratchet No Train Post

object

Example ^generated

{}

422

Validation Error

Media typeapplication/json

HTTPValidationError

object

detail

Detail

Array<object>

ValidationError

object

loc

required

Location

Array

msg

required

Message

string

type

required

Error Type

string

Example ^generated

{
  "detail": [
    {
      "loc": [
        "example"
      ],
      "msg": "example",
      "type": "example"
    }
  ]
}