internet-court/near-ai-cloud
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.
npx skills add https://github.com/internet-court/internet-court-skill --skill 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.
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);
1. Generate nonce
2. Request model attestation → get signing_address, nvidia_payload, intel_quote
3. Verify GPU attestation → submit nvidia_payload to NVIDIA NRAS, check JWT fields
4. Verify CPU attestation → verify intel_quote via dcap-qvl or TEE Explorer
5. Verify GPU-CPU binding → signing_address + nonce bound in TDX report data; same nonce in NRAS eat_nonce
6. Make chat request → use the API as normal
7. Fetch chat signature → GET /v1/signature/{chat_id}
8. Verify signature → recover signer, compare to attested signing_address
Base URL: https://cloud-api.near.ai
| Endpoint | Method | Description |
|----------------------------------------|--------|------------------------------------|
| /v1/chat/completions | POST | OpenAI-compatible chat completions |
| /v1/models | GET | List available models |
| /v1/attestation/report?model={model} | GET | Model attestation (GPU + CPU) |
| /v1/attestation/report | GET | Gateway attestation |
| /v1/signature/{chat_id} | GET | Chat message signature |
https://cloud-api.near.ai/v1 — use with any OpenAI SDKsigning_algo can be ecdsa or ed25519[["JWT", "..."], {"GPU-0": "..."}] — overall JWT + per-GPU JWTssigning_address from model attestation must match the address that signed chat messages| Topic | File |
|----------------------------------|----------------------------------------------------------------------|
| Private vs Anonymised Models | references/private-vs-anonymised.md |
| Model TEE verification | references/model-verification.md |
Planned:
Take internet-court/near-ai-cloud from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.