JavaScript
Requires Node.js 24.22.1 or later.
Python
Requires Python 3.12 or later.
Rust
Use Rust stable and Cargo.
Go
Requires Go 1.26.10 or later.
Widget
Use the Embedded guide to add the Verification Center to your web application.Install
Supported APIs
Choose the API listed on your model’s page in the model catalog, then open its example in your language guide. All four languages support the APIs below; Chat Completions, Responses, and Messages also support streaming.E2EE
End-to-end encryption (E2EE) encrypts supported Chat fields to a verified model key. It is disabled by default and requires a supported NEAR TEE model. Enable it in your language’s client options; leave it disabled for Responses, Messages, and System One.Verification
The SDK verifies Gateway attestation before sending a request and model attestation where supported. After receiving the answer, callverifyResponse() or your language’s equivalent before using the output. For streaming, consume the entire stream first.
System One’s receipt ID is separate from the upstream request ID. If a receipt is temporarily unavailable, retry verification on the same client with the same ID; do not resend inference. Response records expire after 60 minutes by default; verify before expiry or closing the client.
Check the returned signature kind:
provider_tee: the verified model signer signed the request and response bytes.gateway: the verified Gateway signed those bytes. This does not verify model TEE execution.
OHTTP
OHTTP adds encryption between the client and the attested Gateway for Chat Completions, Responses, and Messages. It is optional, disabled by default, and requires Ed25519. See the JavaScript, Python, Rust, or Go configuration.Examples
- SDK examples: complete projects for each language.
- Image provenance examples: check image builds and Compose Manager deployment evidence against your policies.