Review filenames, sizes, content hashes, and attestation state.
Docs · Portal
Owner portal.
owner controlsfiles · ops · usage
The owner dashboard for locker operations.
The owner portal is the browser-facing control surface for managing lockers, inspecting stored records, reviewing agent operations, checking usage, sharing viewer access, and running verification from a passkey-gated session.
See task summaries, tool calls, statuses, and runtime usage.
Open receipt-level verification from the same owner surface.
Access
Enter through a passkey-gated owner session
The owner portal begins with human authentication, then resolves the locker and signing-key state for that owner.
Owner portal Sign in with passkey Load owner status Resolve linked key identities GET /v1/portal/status
Code notes
The owner portal starts with passkey authentication. After the browser verifies the credential, the portal can load owner-scoped locker status, files, operations, usage, and alerts.
Passkey login unlocks the browser UI. Gateway operations still rely on the owner's Ed25519 or secp256k1 authorization layer.
Dashboard
Inspect files, operations, usage, and receipts
Portal endpoints present owner data as dashboard views without requiring the owner to run SDK or HTTP commands.
GET /v1/portal/filesGET /v1/portal/ops-logGET /v1/portal/usageGET /v1/portal/alerts GET /v1/portal/verify/{receipt_id}
Code notes
The portal is the dashboard layer over owner data. Use it to inspect stored files, recent operations, usage totals, and alerts without dropping into the SDK or raw HTTP flow.
Some portal data routes are dashboard endpoints. Verification routes should fail loudly when verification cannot be completed.
Share
Generate read-only viewer access
Owners can expose verification-oriented views to recipients while keeping mutation authority inside the owner portal.
Owner portal Files Select record Share viewer URL https://portal.nukez.xyz/viewer/lkr_7a2c...e9f3#v=A7F1
Code notes
Owners can share a scoped viewer URL for a locker or a specific record. The recipient authenticates with their own passkey and receives a read-only verification surface, not owner controls.
Viewer URLs are read-only. They do not expose the owner passkey, owner portal session, or signing key.
Control
Keep authority-changing actions explicit
Capacity, signing-key, provider, and attestation changes belong in deliberate owner workflows.
Owner operations Expand capacity Rotate signing key Link Ed25519 or secp256k1 identity Rebind provider Re-attest storage state
Code notes
Owner operations that change authority or storage posture should be explicit: expand capacity through a paid confirmation flow, rotate or link signing keys deliberately, and use provider rebinding only when the storage migration and attestation implications are clear.
The portal should make irreversible or authority-changing actions obvious before the owner confirms them.
Owner access is broader than viewer access.
Owners can inspect records, initiate authority-changing workflows, and create viewer links. Viewers can only inspect the scoped records they were given. If the portal is not enrolled yet, start with passkey setup before using owner controls.