Skip to content

Integration

SIX uses an OpenAI-compatible API, so integration is straightforward. If your code works with OpenAI, it works with SIX -- and you get cryptographic receipts on every response.

Supported Languages

SIX works with any language that can make HTTPS requests. These guides cover the most common:

Language Guide Method
Python Python Guide requests library or OpenAI client
cURL cURL Guide Direct HTTP from the command line
Any API Reference Standard REST API (JSON over HTTPS)

Not limited to Python and cURL

SIX is a REST API. Any language with an HTTP client works: JavaScript/Node.js, Go, Rust, Java, C#, Ruby, PHP, etc. The Python and cURL guides demonstrate patterns that apply to all languages.

OpenAI Client Compatibility

If you already use the OpenAI Python client, point it at SIX:

from openai import OpenAI

client = OpenAI(
    api_key="YOUR_SIX_API_KEY",
    base_url="https://six-sov.com/v1"
)

response = client.chat.completions.create(
    model="default",
    messages=[
        {"role": "user", "content": "Your prompt here"}
    ]
)

print(response.choices[0].message.content)

Two changes from OpenAI usage:

  1. Set base_url to your SIX endpoint
  2. Use your SIX API key instead of an OpenAI key

Everything else -- message format, streaming, function calling -- works the same way.

Migration from Other Providers

From OpenAI

Change Before (OpenAI) After (SIX)
Base URL https://api.openai.com/v1 https://six-sov.com/v1
API key sk-... Your SIX API key
Model gpt-4 default or provisioned model
New feature -- privacy_tier field (optional)
New feature -- receipt in response body

From Anthropic

Change Before (Anthropic) After (SIX)
Endpoint /v1/messages /v1/chat/completions
Message format Anthropic format OpenAI-compatible format
Auth header x-api-key Authorization: Bearer ...

From Azure OpenAI

Change Before (Azure) After (SIX)
Base URL https://{resource}.openai.azure.com/... https://six-sov.com/v1
Auth Azure AD or API key SIX API key
API version Query parameter Not needed

Handling Receipts

Regardless of language, the receipt handling pattern is the same:

  1. Extract the receipt from the response body
  2. Store the receipt alongside the response in your records
  3. Verify the receipt (immediately or later)
  4. Log the verification result in your audit system
Response
  |
  +-- choices[] --> Your AI output (use normally)
  |
  +-- receipt{} --> Cryptographic proof (store + verify)

Environment Setup

Environment Variables

Set these before running your integration code:

export SIX_API_KEY="your-api-key-here"
export SIX_ENDPOINT="https://six-sov.com"

Configuration Checklist

Item Status Notes
API key obtained Required From your onboarding package
Endpoint URL confirmed Required Unique per organization
Privacy tier selected Optional Default is standard
Receipt storage configured Recommended For audit trail
Verification pipeline set up Recommended For compliance

Next Steps