Core Concepts

Agent Identity

Agents are identities you register in Cyphrex. Each agent has a unique ID and optional name. All checks are attributed to an agent so you can enforce policies and track usage per agent.

Blockchain SSN

Every agent can optionally receive a blockchain Social Security Number — a cryptographically verified on-chain identity on Solana. It anchors your agent for enterprises that need proof of registration and auditability, not just logs.

  • Immutable identity — A program-derived address (PDA) acts as the agent's permanent SSN on-chain.
  • Cryptographic verification — Buyers and auditors can verify identity and registration status (see GET /v1/verify/:ssn).
  • Self-custody model
    • Self-custody — You own the identity on all plans. Cyphrex never holds private keys.
    • Gas policy: Gas is covered on Core, Scale and Enterprise.
  • Action attribution — Cyphrex ties checks and audit events to the on-chain identity. Heavier on-chain aggregation can be Merkle-batched over time for cost efficiency where applicable.

Blockchain SSN is optional. All monitoring, enforcement, audit log, and alert features work without it. Use it when you need cryptographic audit trails, enterprise verification, and a clear identity layer for autonomous systems.

Behavior Profiles

Behavior profiles define what an agent is allowed to do: which URLs it can call, which action types are permitted, rate limits, and spend caps. You attach a profile to an agent when registering or updating it.

Safety Packages

Pre-built profiles for common use cases:

  • Finance — Restricted URLs, high audit retention
  • Healthcare — PHI-safe defaults, strict access
  • Support — Ticket systems, knowledge bases
  • Research — Academic APIs, read-heavy
  • Code — Repos, CI/CD, no production writes by default
  • Custom — Define your own rules

Action Types

Every check includes an action type. Supported types include:

  • http_call — Outbound HTTP/API requests
  • llm_response — LLM completions
  • db_query — Database queries
  • file_access — File read/write
  • tool_use — Tool or function calls
  • Custom types for your framework

Audit Logs

Cyphrex records each check: agent, action type, URL (if applicable), result (allowed/blocked), violations, spend, and timestamp. Retention depends on your plan: 30 days (Sandbox), 1 year (Core), 3 years (Scale), custom (Enterprise).

Alerts

Alerts are triggered when violations occur or thresholds are exceeded. Severity levels: P1 (critical), P2 (warning), P3 (info). Delivery via email and/or webhook. View violations under Alerts; configure destinations under Settings → Alert notifications.

Signed Compliance Reports

Every compliance report exported from Cyphrex is hashed with SHA-256 over RFC 8785 JSON Canonicalization Scheme (JCS) bytes, Ed25519 signed bycyphrex-signer-prod-01, and independently verifiable against the public key PEM at cyphrex.io/api/keys/cyphrex-signer-prod-01 (text/plain). The HTML registry page is cyphrex.io/keys/cyphrex-signer-prod-01.

Supported frameworks: SOC 2 Type II, EU AI Act (Regulation (EU) 2024/1689 as amended by Regulation (EU) 2026/1744), HIPAA, SR 11-7 (superseded by SR 26-2, April 2026), SR 26-2, NYDFS Part 500, Cal. Civ. Code § 1714.46 (AB 316, Stats. 2025, ch. 672), ABA Model Rules 1.1/1.6/5.1/5.3 (Formal Opinion 512), Court AI Disclosure (22 NYCRR Part 161; FRCP 11(b)), eDiscovery TAR (FRCP 26 and 34; Sedona Principles 2 and 6), ISO 42001, HHS OCR Phase 3, EU AI Act Annex III, FINRA Rule 4511, SOX 302 and 906, AML and FinCEN, NAIC Model Bulletin, Colorado ADMT Law (SB 26-189, effective 1 January 2027). Each agent action maps to a specific regulation clause with a status of Satisfied, Prevented, or Gap, review required. Mapping is not certification.

Signed compliance reports are included on Core, Scale and scoped for Enterprise as contracted. Reports are downloadable as PDF or JSON from the dashboard (Reports tab) or via the export API endpoint.

Vertical Compliance Reports

Compliance reports are scoped to your industry vertical, selected during onboarding.

  • Legal: ABA Model Rules 1.1, 1.6, 5.1, 5.3 with Formal Opinion 512 (2024). Court AI Disclosure under 22 NYCRR Part 161 and FRCP 11(b). eDiscovery TAR under FRCP 26 and 34 and Sedona Principles 2 and 6. Cal. Civ. Code § 1714.46 (AB 316). ISO 42001 control mapping.
  • Healthcare: HIPAA PHI access documentation. HHS OCR audit-ready risk assessment packages. EU AI Act Annex III high-risk system documentation from 2 December 2027. CMS prior authorization decision audit trails coming soon.
  • Finance: SR 26-2 superseded SR 11-7 in April 2026; both remain mapped. FINRA Rule 4511 auditable records. SOX 302 and 906 financial close audit trails. NYDFS Part 500 compliance reports. AML and FinCEN decision audit trails. SEC Rule 17a-4 and DORA coming soon.
  • Insurance: NAIC model bulletin per-agent underwriting documentation, adopted in at least 24 states and DC. Colorado ADMT Law (SB 26-189, effective 1 January 2027). NYDFS Part 500. EU Solvency II and UK FCA reports coming soon.

Select your industry during onboarding to unlock vertical-specific reports in the dashboard.

Merkle Anchoring

On Core, Scale and Enterprise (as contracted), agents are Merkle-anchored on Solana. Each batch hashes a closed leaf per event into a Merkle tree and writes the root on-chain, giving you:

  • A Merkle root of that hour's leaf set, on chain
  • Per-event proof of inclusion in that on-chain root

An inclusion proof shows a closed leaf was in the tree whose root was anchored. It does not prove completeness — Cyphrex chooses the leaf set — and it does not cover event fields outside the closed leaf.

Hourly Merkle anchoring on Solana is available on Core. Scale uses five minute anchoring. Enterprise can add real time on chain authorization.

Message the founder