NEAR AI
Bring your own NEAR AI key and route NEAR AI models through TrustedRouter with one base URL, usage records and spend limits.
NEAR AInear-ai
These privacy labels describe NEAR AI, the upstream model provider. Confidential requires all three: verified provider compute, end-to-end encryption and explicit zero data retention. Account and billing metadata are outside the content-retention claim.
| Provider | NEAR AI |
|---|---|
| API operator country | US Legal home of the API operator, not an inference-location guarantee. |
| Headquarters | Not verified |
| Routing status | Not routable |
| Provider website | https://near.ai/ |
| Models | 0 public models |
| Credits routes | 0 |
| Zero data retention | yes All routes |
| Verified confidential inference | Verified |
| Policy note | NEAR AI declares zero data retention for its hosted confidential inference. On TrustedRouter this covers only release-pinned direct Private TEE routes, not NEAR AI's Incognito or Attested Third-Party routes. ZDR describes inference content, not account, billing or operational metadata. Cloud Terms section 7.2 makes retention route-specific; the general privacy policy covers Cloud website and account-administration data, not an all-services ZDR guarantee. TrustedRouter connects directly to the model workload and verifies the live TLS key, Intel TDX quote, NVIDIA GPUs, deployment action log, and pinned workload inside the TrustedRouter enclave before sending content. Verification fails closed. Policy source |
Inference locations
Provider API declarations are also available on each model's endpoint API. Direct chat and Responses replies separate advertised availability from serving location in usage.inference_location; the actual serving region remains unknown when not reported.
usage.provider_usage.gateway_region identifies the TrustedRouter gateway, not the provider's inference location. A value such as europe-west4 does not mean the model ran in Europe. usage.inference_location.serving_region remains null when the provider has not reported it. Older gateways may return the gateway-only field as provider_usage.region.
Where the upstream GPUs execute the model, not the provider's headquarters, API ingress, or data storage. ZDR and confidential inference do not by themselves restrict geography.
- Declared countries or regions
- Not verified
No inference-location declaration has been verified for this provider. - Can locations change?
- Not verified. Do not assume that the serving location is fixed.
- Provider region pinning
- Not verified.
- Pinning through TrustedRouter
- No verified provider-specific location pin documented here.
- Infrastructure declaration
- Inference location not verified; no country-specific residency commitment.
- Evidence
- Not yet reviewed.
Provider selection alone is not a region pin. TrustedRouter's US provider filter selects company jurisdiction, not GPU location. A regional gateway hostname does not pin a downstream GPU. For a binding residency requirement, confirm the model, region, failover scope and enforced controls before sending sensitive data.
Models served by NEAR AI.
Each row links to pricing, provider, benchmark, and API pages for the model.
| Model | AI IQ | Context | Input | Cached input | Output |
|---|
Questions
Does NEAR AI have zero data retention?
TrustedRouter records NEAR AI as supporting provider-level zero data retention based on the policy source linked on this page. This is a provider policy claim, separate from TrustedRouter's content-stateless real-time gateway and from end-to-end confidential compute.
Is NEAR AI end-to-end encrypted?
TrustedRouter records NEAR AI as supporting provider-side confidential compute and end-to-end encrypted inference. The route-specific model page shows whether that protection applies to a particular endpoint.
Which NEAR AI models are available through TrustedRouter?
This page currently lists 0 public NEAR AI models, with live pricing, route count, context length, measured performance when available, and links to each model's provider and benchmark pages.