Skip to content

Models: describe the three privacy tiers used in the catalog - #61

Merged
alejoras merged 1 commit into
mainfrom
models/privacy-tier-names
Oct 5, 2026
Merged

alejoras merged 1 commit into
mainfrom
models/privacy-tier-names

Conversation

@alejoras

@alejoras alejoras commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

What changes

  • cloud/models.mdx: replaces the old "TEE-hosted vs third-party" split with the three tiers the catalog at near.ai/models now shows: Confidential TEE (NEAR AI-hosted), 3P Confidential TEE (attested third-party enclaves, provider listed as Attested 3P), Incognito (routed through the TEE gateway under NEAR AI's provider account, model runs at the provider).
  • cloud/inference-sdk/python.mdx: Chutes-hosted models are 3P Confidential TEE in the catalog. The page called them "Incognito". It now says they get Gateway-only verification in Python and that the SDK's "Incognito mode" is separate from the catalog tier.

Companion to nearai/nearai-website#84.

Checks

`mint broken-links` and `mint validate` pass.

🤖 Generated with Claude Code

The model catalog now labels models Confidential TEE, 3P Confidential TEE
or Incognito. Describe the three tiers on the models page, and stop the
Python SDK page from calling Chutes-hosted 3P Confidential TEE models
"Incognito" without saying it is an SDK verification mode.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@alejoras
alejoras merged commit 021296c into main Oct 5, 2026
2 checks passed
@alejoras
alejoras deleted the models/privacy-tier-names branch October 5, 2026 21:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant