Skip to content

docs: flatten Verification navigation #62

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
think-in-universe merged 2 commits into from
Oct 12, 2026
Merged

docs: flatten Verification navigation #62

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
dc25fcb
docs: flatten verification navigation
hanakannzashi Oct 12, 2026
f5aad8d
docs: streamline verification landing page
hanakannzashi Oct 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 2 additions & 10 deletions cloud/verification/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,21 +9,13 @@ Use these guides to verify the evidence returned for requests sent through the N
See an example implementation in the [NEAR AI Cloud Verification Example](https://github.com/near-examples/nearai-cloud-verification-example) repo. A more complete verifier is available in the [NEAR AI Cloud Verifier](https://github.com/nearai/nearai-cloud-verifier) repo.
</Tip>

## Verify a NEAR AI Cloud Gateway request

<CardGroup cols={1}>
<Card title="NEAR AI Cloud Gateway" icon="cloud" href="/cloud/verification/cloud-api">
Use this when your application sends requests through `cloud-api.near.ai`. Verify the gateway and, when your policy requires it, every returned NEAR model-attestation candidate.
</Card>
</CardGroup>

<Note>
Using a direct completions endpoint (`{slug}.completions.near.ai`)? Direct verification is experimental. See [Direct Completions](/cloud/experimental/direct-completions) for the current limitations.
</Note>

## What happens next
## Verification flow

The Gateway guide walks through verifying fresh deployment evidence before a completion and, when present, a response signature against its reported signer. Depending on your application's policy, you can also verify the TLS connection and software-image provenance.
Start with [Gateway attestation](/cloud/verification/cloud-api/gateway-attestation) to verify fresh deployment evidence before a completion. When your policy requires NEAR model evidence, verify every returned [model-attestation candidate](/cloud/verification/cloud-api/model-attestations). You can also verify the [TLS connection](/cloud/verification/cloud-api/tls) and [image provenance](/cloud/verification/cloud-api/image-provenance) as required by your policy; after a completion, verify its [response signature](/cloud/verification/cloud-api/response-signatures) when present.

## Common verification concepts

Expand Down
16 changes: 5 additions & 11 deletions docs.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,17 +67,11 @@
"icon": "file-check",
"root": "cloud/verification/index",
"pages": [
{
"group": "NEAR AI Cloud Gateway",
"root": "cloud/verification/cloud-api/index",
"pages": [
"cloud/verification/cloud-api/gateway-attestation",
"cloud/verification/cloud-api/model-attestations",
"cloud/verification/cloud-api/tls",
"cloud/verification/cloud-api/response-signatures",
"cloud/verification/cloud-api/image-provenance"
]
},
"cloud/verification/cloud-api/gateway-attestation",
"cloud/verification/cloud-api/model-attestations",
"cloud/verification/cloud-api/tls",
"cloud/verification/cloud-api/response-signatures",
"cloud/verification/cloud-api/image-provenance",
{
"group": "Reference",
"pages": [
Expand Down
Loading