ATatomaai
Confidential Images

Create confidential image

Changed on

This handler processes image generation requests in a confidential manner, providing additional encryption and security measures for sensitive data processing. It supports both streaming and non-streaming responses while maintaining data confidentiality through AEAD encryption and TEE hardware, for full private AI compute.

post/v1/confidential/images/generations

Request

Request body

ciphertextstring required

The encrypted payload that needs to be processed (base64 encoded)

client_dh_public_keystring required

Client's public key for Diffie-Hellman key exchange (base64 encoded)

model_namestring required

Model name

node_dh_public_keystring required

Node's public key for Diffie-Hellman key exchange (base64 encoded)

noncestring required

Cryptographic nonce used for encryption (base64 encoded)

num_compute_unitsinteger nullable

Number of compute units to be used for the request, for image generations, as this value is known in advance (the number of pixels to generate)

plaintext_body_hashstring required

Hash of the original plaintext body for integrity verification (base64 encoded)

saltstring required

Salt value used in key derivation (base64 encoded)

stack_small_idinteger required

Unique identifier for the small stack being used

streamboolean nullable

Indicates whether this is a streaming request

Response

Image generations

ciphertextstring required

Encrypted response body (base64 encoded)

noncestring required

Nonce used for encryption (base64 encoded)

response_hashstring nullable

Hash of the response body (base64 encoded)

signaturestring nullable

Signature of the response body (base64 encoded)

Example response

{
  "usage": {
    "completion_tokens": 10,
    "completion_tokens_details": {
      "accepted_prediction_tokens": 10,
      "reasoning_tokens": 10
    },
    "prompt_tokens": 10,
    "prompt_tokens_details": {
      "cached_tokens": 10
    },
    "total_tokens": 20
  }
}

Changes

  • f0bf5a2dde0fRevision changes
    • breaking

      the ///// response's property type changed from integer null to integer, and format from int64 to int32 for status

    • breaking

      the ///// response's property type changed from no type to object for status

    • info

      the response property ///// became required for the status

    • info

      the response property ///// became required for the status

    • info

      added the required property ////// to the response with the status

    • info

      added the required property ////// to the response with the status

    • info

      added the required property ////// to the response with the status

    • info

      added the required property ////// to the response with the status

    • info

      added the required property ///// to the response with the status

  • d714acb641bdRevision changes
    • info

      endpoint added