Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.meshrouter.app/llms.txt

Use this file to discover all available pages before exploring further.

MESH privacy mode produces a signed attestation alongside each completion so callers can verify the response was generated by the published MESH runtime image, not a substituted process.
1

Client sends a privacy-mode request

Set privacy.mode = "mesh" on /v1/chat/completions.
2

MESH runtime processes the request

The MESH runtime — a deployment-pinned image hash — handles the prompt, calls the selected model, and computes the response. No third-party process sees the prompt or response body during this step.
3

Attestation is emitted alongside the response

Before the completion deltas land, the response stream emits a privacy.attestation event containing the runtime measurement, release key id, build provenance, and anchor transaction references.
4

Client verifies the attestation (optional)

POST the document to /v1/attestation/verify to confirm the runtime measurement matches the publicly-pinned MESH release before accepting sensitive content.
GET /v1/attestation returns the signed attestation document, expected runtime measurement, build provenance, release-key reference and latest anchor transactions.

​
Caveats

MESH privacy mode runs inside the MESH runtime: prompts and completion bodies are not retained by default, but MESH operators can in principle observe them in flight. For prompts requiring hardware-isolated decryption with no operator visibility, contact us directly.