Near AI Cloud
NEAR AI Cloud private inference and verification.
Install
npx skills add internet-court/internet-court-skill --skill near-ai-cloud -g -a claude-code -y- Repository
- internet-court/internet-court-skill7k
- Category
- Engineering
- Updated
- 9d ago
- License
- See repository
- Context cost
- Lightabout 1,147 tokens
- Runs scripts
- No, instructions only
What it does
NEAR AI Cloud private inference and verification. Use when integrating NEAR AI Cloud API for verifiable private AI inference, verifying model or gateway TEE attestation (NVIDIA NRAS, Intel TDX), verifying chat message signatures, implementing end-to-end encrypted chat, or using the OpenAI-compatible API with NEAR AI Cloud.
NEAR AI Cloud
Verifiable private AI inference through Trusted Execution Environments (TEEs). All inference runs inside Intel TDX confidential VMs with NVIDIA TEE GPUs, your data stays encrypted and isolated from infrastructure providers, model providers, and NEAR itself.
Quick Start
The API is OpenAI-compatible. Point any OpenAI SDK at https://cloud-api.near.ai/v1:
import openai
client = openai.OpenAI(
base_url="https://cloud-api.near.ai/v1",
api_key="YOUR_API_KEY" # from cloud.near.ai dashboard
)
response = client.chat.completions.create(
model="deepseek-ai/DeepSeek-V3.1",
messages=[{"role": "user", "content": "Hello, NEAR AI!"}]
)
print(response.choices[0].message.content)
import OpenAI from 'openai';
const openai = new OpenAI({
baseURL: 'https://cloud-api.near.ai/v1',
apiKey: 'YOUR_API_KEY',
});
const completion = await openai.chat.completions.create({
model: 'deepseek-ai/DeepSeek-V3.1',
messages: [{ role: 'user', content: 'Hello, NEAR AI!' }]
});
console.log(completion.choices[0].message.content);
How It Works
- All inference runs inside Intel TDX confidential VMs with NVIDIA TEE GPUs
- TLS terminates inside the TEE, not at a load balancer, prompts are never exposed in plaintext
- TEEs generate cryptographic attestation proofs verifiable via NVIDIA NRAS and Intel TDX
- Every chat response is signed by a key that never leaves the TEE
- You can independently verify hardware attestation and bind it to message signatures
