Agent access

This repository does not include an MCP server or MCP tool definitions. Agents call the REST API with a scoped bearer key.

Create a key in the developer console. The secret is shown once and is sent as Authorization: Bearer hs_live_… or hs_test_…. Each key has one or more of the scopes read, write, and sign. A key can also require the hybrid ML-DSA envelope on sign. Agents hold API keys, not signing keys.

The same three calls used by the Python SDK — register, sign, and verify — are the integration surface. The contract is the API reference and /openapi.json.

The document stays on the device until the user sends or shares it. Only the SHA-384 seal (96 hex characters) is anchored. Optional cloud review runs only when the user taps it. A hash shows a document has not changed since it was sealed. It does not prove who signed it.