Quick Start¶
Make your first verified inference in 5 minutes.
1. Set Your API Key¶
2. Send an Inference Request¶
SIX uses an OpenAI-compatible API format. If you've used OpenAI, Anthropic, or any chat-completion API, this will feel familiar.
import requests
response = requests.post(
"https://six-sov.com/v1/chat/completions",
headers={"Authorization": f"Bearer {SIX_API_KEY}"},
json={
"model": "default",
"messages": [
{"role": "user", "content": "Summarize HIPAA Section 164.312"}
]
}
)
data = response.json()
print(data["choices"][0]["message"]["content"])
3. Examine the Receipt¶
Every response includes a signed receipt in the response headers or body:
{
"choices": [{"message": {"content": "..."}}],
"receipt": {
"receipt_id": "rcpt_f8c505ce...",
"routing": "sovereign",
"commitment": "04a7f3c2...e9b1d0f",
"signature": "0x69c8...f98c8",
"verified": true
}
}
| Field | Meaning |
|---|---|
receipt_id |
Unique identifier for this inference |
routing |
Confirms sovereign (your infrastructure) or standard routing |
commitment |
Cryptographic commitment binding the receipt fields |
signature |
Server signature — independently verifiable |
verified |
Server-side verification status |
4. Verify Independently¶
Verification Tooling
Independent verification tools are provided to approved partners. See Verification →
What Just Happened¶
- Your request was routed to sovereign compute (your infrastructure)
- The inference executed with cryptographic attestation
- A signed receipt was generated binding the request, response, and routing
- A commitment was created so you can verify no fields were altered
- The receipt was returned with the response
The proof is mathematical, not promissory. Modify any receipt field — the signature breaks. Your team can verify this independently without trusting SIX.
Next Steps¶
- Authentication → — Understanding API key + cryptographic auth
- API Reference → — Complete endpoint documentation
- Verification → — Verify receipts yourself