H33 Customer Dashboard
Overview
Your H33 authentication activity at a glance
| Auth ID | Backend | Method | Status | Latency | Time |
|---|---|---|---|---|---|
| Loading activity... | |||||
Products & Services
Configure your FHE backends, signature schemes, routing, and add-on services
Usage & Analytics
Per-endpoint breakdown, latency percentiles, error tracking
| Time | Endpoint | Error Code | Message | Count |
|---|---|---|---|---|
| 1m ago | /v1/auth/fullstack | E5029 | Encrypted execution timeout — computation depth exceeded configured threshold | 3 |
| 14m ago | /v1/auth/biometric | E4001 | Biometric verification failed — similarity below acceptance threshold | 8 |
| 47m ago | /v1/auth/zk | E5003 | Proof verification failed — deterministic replay did not match expected output | 1 |
API Key Management
Create, scope, and manage trust surface credentials for your integrations
export H33_API_KEY=h33_live_...). Never commit keys to source control. Rotate keys every 90 days. Use the most restrictive scopes possible. Keys auto-hide after 30 seconds when revealed.
Integration & SDKs
Quick-start code, environment management, and SDK references
Security
Security settings define who may act. Continuity infrastructure proves what actually happened.
Attestation Audit Trail
Every operational event produces a cryptographic attestation. Independently verifiable. Post-quantum signed.
Decision Responsibility Ledger
Every operational event produces a governance receipt. PQ-signed. Replayable. Independently verifiable. Continuity-bound.
AI Agent Activity — H33-74 Attested
Every agent action becomes a replayable cryptographic receipt without exposing underlying data.
H33 Authority Infrastructure for Agents
How do you control 10,000 AI agents? Live meters for every decision, every Agent Firewall refusal, every signed receipt, every chaos block. Backed by the Free / Pro / Enterprise / Sovereign plan you selected.
.h33pqv.json artifact to verify it independently.Notification Connectors
Layer 4 of the four-layer authority architecture. Configure where escalation notifications are delivered per principal. BYOK — H33 never holds your Slack / SMS / Email / Teams / PagerDuty credentials in plaintext. Substrate-signed handle only — the notification never carries free-text auth content.
- Layer 1 — Authority Substrate. Who has authority (qsign-delegation).
- Layer 2 — Substrate-signed Routing. Who receives the escalation (qsign-escalation).
- Layer 3 — Enterprise Escalation Policies. What policy governs how the chain is walked (qsign-policies).
- Layer 4 — Notification Connectors. How they're notified (this panel).
xoxb bot token.STS:AssumeRole into your role at delivery time, sends via SES, discards. No long-lived AWS keys held.H33_NOTIFY_CONFIGS_JSON environment variable (keyed by principal_id), or POST to your tenant config endpoint when v0.2 wires durable storage.{
"principal_id": "",
"channels": []
}
H33_NOTIFY_DRY_RUN=true on the function env to no-op delivery and return masked metadata. Useful before pointing at a live Slack workspace.Replay Integrity
Deterministic replay verification — proving every operational state can be independently reconstructed.
Exposure State
Cryptographic proof of data non-exposure. Not monitoring — mathematical attestation.
Last verified: 14 seconds ago
Evidence Portability SURVIVAL
Cross-chain attestation anchoring — cryptographic witnesses across multiple blockchains.
Credits & Billing
Monitor unit usage, choose your plan, and manage invoices
Webhooks
Configure real-time event delivery to your endpoints
| ID | Event | Endpoint | Status | Latency | Time |
|---|---|---|---|---|---|
| No deliveries yet. Webhook events will appear here once endpoints are configured. | |||||
Legal & Compliance
All accepted agreements, addenda, and compliance records
H33 Token
Connect your Solana wallet, view token balance, and manage H33 token activity
Account
Manage your profile, plan, and notification preferences
Knowledge Base
Product guides, integration examples, unit costs, and use cases