Quick Start Guide
Welcome to the TATC Platform Developer Documentation. This guide details the integration flow to authenticate, issue inference requests via the TATC Token API, and verify environment access for Bare Metal GPU Infrastructure.
1. Authentication Standard
The TATC Platform utilizes Bearer Token authentication across all API endpoints. All requests must include your provisioned API key in the Authorization HTTP header.
Security & Compliance Boundary: API keys carry full access permissions for your allocated tenant quota. Always store keys securely using environment variables or secret management vault systems. Never expose raw keys in public repositories or client-side codebases.
2. TATC Token API Integration
The TATC Token API provides a unified RESTful interface fully compatible with standard OpenAI client libraries, LangChain, and LiteLLM orchestration frameworks.
Option A: HTTP REST Request (cURL)
Execute an HTTP POST request to the /v1/chat/completions endpoint to verify endpoint connectivity and key authorization:
curl https://api.tatc.cloud/v1/chat/completions \
-H "Content-Type: application/json" \
-H "Authorization: Bearer sk-xxxx" \
-d '{
"model": "model-name",
"messages": [
{
"role": "user",
"content": "Verify system connectivity and latency."
}
],
"temperature": 0.2
}'Option B: Python Integration
Configure the standard openai SDK by directing the base_url to the TATC Gateway:
import os
from openai import OpenAI
# Initialize client using environment variable authentication
client = OpenAI(
base_url="https://api.tatc.cloud/v1",
api_key=os.environ.get("TATC_API_KEY", "sk-xxxxxxx")
)
# Execute completion request
response = client.chat.completions.create(
model="model-name",
messages=[
{"role": "system", "content": "You are an enterprise AI assistant."},
{"role": "user", "content": "Confirm active API endpoint status."}
],
temperature=0.2
)
print(response.choices[0].message.content)3. Bare Metal GPU Server Environment
TATC Bare Metal GPU Servers provide dedicated, single-tenant physical compute engineered for high-density AI and HPC workloads.
Architectural Features
- •Physical Isolation: Single-tenant hardware with zero virtualization overhead and direct hardware pass-through.
- •Full Root Authority: Complete operational control over custom OS kernels, container runtimes, and local execution stacks.
- •High-Throughput Interconnect: Dedicated regional fabric supporting high-bandwidth cluster scale-out topologies.
Enterprise Provisioning & Access
To maintain strict physical isolation and dedicated hardware routing, all bare-metal clusters are deployed via our Managed Enterprise Provisioning process.
Upon account verification and cluster allocation:
- Network routes, dedicated IP assignments, and access parameters are provisioned by TATC SRE engineers.
- Secure root access is granted to your designated organization administrators via SSH key authentication.
Operational Boundary: TATC maintains physical data center facility operations, power redundancy, and hardware health. Customers hold sole responsibility for software stack deployment, kernel configurations, and application-level workloads.
4. Standard Gateway Response Codes
The TATC Gateway returns standard HTTP status codes. Refer to the table below for handling API responses:
| HTTP Code | Status Description | Cause & Resolution |
|---|---|---|
| 200 | OK — Success | Request completed successfully. |
| 401 | Unauthorized — Authentication Failure | Missing or invalid sk- API key in Authorization header. |
| 429 | Rate Limit — Quota Exceeded | Account TPM/RPM threshold or hard spend cap reached. |
| 500 | Internal Error — Gateway / Infrastructure Fault | Upstream compute node fault; retry using exponential backoff. |
5. Security & Data Governance Principles
Zero-Data-Retention (ZDR): The TATC Gateway operates purely on a transit basis. Prompt payloads and response streams are processed in memory and are never stored, logged, or utilized for model training.
IaaS Boundary: TATC maintains physical data center facility availability, hardware health, and network connectivity. Customers hold sole responsibility for OS-level packages, kernel configurations, and application security.