Skip to main content

Audit chain for Claude Code workflows — consensus verification, persistent memory, and XRPL provenance for every agent action.

Project description

credex-claudecode

$60 to prove what $500 bought you.

Audit chain for Claude Code workflows — consensus verification, persistent memory, and XRPL provenance for every agent action.

When Claude Code spins up hundreds of parallel agents that run for days, nobody can reconstruct what happened without a verification trail. credex-claudecode is that trail.

What It Does

credex run "Migrate from Express to FastAPI" --verify milestones
  1. Wraps Claude Code — runs your prompt through claude -p with streaming output
  2. Parses every action — tool calls, file writes, bash commands, agent decisions
  3. Routes through CredEx verification — pre-verification at $0.001/action, full 5-LLM consensus at $0.10/milestone
  4. Anchors to XRPL — cryptographic provenance at workflow boundaries
  5. Produces workflow.audit.json — third-party verifiable record of everything

Cost

For a typical Claude Code "ultracode" workflow ($500 in tokens, ~45,000 actions):

Tier What Cost
Pre-verification Every action, cheap model $0.001 × 45,000 = $45
Full consensus 5-LLM panel at milestones $0.10 × 50 = $5
XRPL anchoring Workflow boundaries ~$10
Total ~$60 (12% overhead)

Install

pip install credex-claudecode

Requires:

  • Python 3.10+
  • Claude Code CLI (npm install -g @anthropic-ai/claude-code)
  • CredEx API key (optional for dry-run mode)

Quick Start

Get a CredEx API key

# Instant anonymous key
curl -X POST https://credexai.live/agent/auth -d '{"type":"anonymous"}'

# Set it
export CREDEX_API_KEY=credex_...

Run a workflow with audit chain

# Full audit (milestones verified + XRPL anchored)
credex run "Migrate the auth module from Express to FastAPI"

# Verify everything (costs more, thorough)
credex run "Security audit of the payment module" --verify all

# Dry run (no CredEx, local audit only)
credex run "Rewrite tests in pytest" --dry-run

# Pass Claude Code options
credex run "Fix the bug in auth.py" --allowed-tools "Read,Edit,Bash" --model claude-sonnet-4-20250514

Inspect an audit

# Pretty-print summary
credex audit workflow.audit.json

# Verify chain integrity
credex audit workflow.audit.json --verify

Lightweight hooks (no wrapper needed)

# Install PostToolUse hooks into your project
credex install-hooks

# Now every Claude Code session automatically logs to CredEx
claude  # Use normally — CredEx logging happens in background

workflow.audit.json

The audit file is a self-contained, third-party verifiable record:

{
  "version": "1.0.0",
  "generator": "credex-claudecode",
  "document_hash": "a1b2c3...",
  
  "workflow": {
    "session_id": "session_abc123",
    "prompt": "Migrate from Express to FastAPI",
    "started_at": "2025-05-29T01:00:00Z",
    "ended_at": "2025-05-29T01:45:00Z",
    "claude_cost_usd": 12.50,
    "total_tokens": 2500000,
    "total_turns": 47
  },
  
  "summary": {
    "total_actions": 342,
    "total_milestones": 28,
    "files_modified": ["src/main.py", "src/routes/auth.py", "..."],
    "credex_verification": {
      "total_verifications": 28,
      "total_cost_usd": 2.85,
      "verdicts": {"TRUE": 26, "MIXED": 2},
      "anchors": 3
    }
  },
  
  "action_chain": [
    {
      "id": "tool-abc123",
      "sequence_number": 1,
      "action_type": "tool_use",
      "tool_name": "Read",
      "content_hash": "f4a3...",
      "chain_hash": "b7c2...",
      "prev_hash": "genesis"
    }
  ],
  
  "chain_proof": {
    "genesis_hash": "genesis",
    "final_hash": "d8e9...",
    "chain_length": 342,
    "algorithm": "sha256-linked"
  }
}

Verification: Each action's chain_hash = SHA256(prev_hash + content_hash + sequence). Recompute from genesis to verify the entire chain.

Architecture

┌──────────────────────────────────────────────┐
│ credex run "prompt"                          │
├──────────────────────────────────────────────┤
│                                              │
│  Claude Code CLI (subprocess)                │
│  --output-format stream-json                 │
│  │                                           │
│  ▼                                           │
│  StreamEventParser                           │
│  ├─ tool_use events → ParsedAction           │
│  ├─ tool_result events → ParsedAction        │
│  └─ result event → WorkflowSession           │
│     │                                        │
│     ▼                                        │
│  CredExVerifier                              │
│  ├─ Pre-verify: $0.001 (cheap, every action) │
│  ├─ Consensus: $0.10 (5-LLM, milestones)    │
│  └─ Anchor: XRPL (workflow boundaries)       │
│     │                                        │
│     ▼                                        │
│  AuditChainGenerator                         │
│  └─ workflow.audit.json                      │
│                                              │
└──────────────────────────────────────────────┘

Integration Paths

1. CLI Wrapper (Full Audit)

Use credex run for complete audit chains. Best for high-stakes workflows: migrations, security audits, rewrites.

2. PostToolUse Hooks (Lightweight)

Use credex install-hooks for background logging. Best for everyday use — zero friction, events stored in CredEx memory.

3. Python SDK (Programmatic)

from credex_claudecode.parser import StreamEventParser
from credex_claudecode.verifier import CredExVerifier

parser = StreamEventParser(prompt="my workflow")
verifier = CredExVerifier(api_key="credex_...", verify_level="milestones")

# Parse events from any source
for line in event_stream:
    actions = parser.parse_line(line)
    for action in actions:
        result = await verifier.process_action(action)

session = parser.finalize()

Why This Matters

Claude Code "ultracode" workflows spin up ~200 parallel agents, execute ~45,000 actions, and run for days. When that $500 workflow completes:

  • Without CredEx: You have code changes. You don't know what decisions were made, what was tried and failed, or what was verified vs. guessed.
  • With CredEx: You have a cryptographic audit chain. Every action verified, every decision anchored, every workflow reconstructable.

For enterprise teams running Claude Code on production codebases, the audit chain isn't optional — it's the difference between "we think the migration worked" and "here's the proof."

Links

License

MIT

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

credex_claudecode-0.1.4.tar.gz (25.1 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

credex_claudecode-0.1.4-py3-none-any.whl (29.5 kB view details)

Uploaded Python 3

File details

Details for the file credex_claudecode-0.1.4.tar.gz.

File metadata

  • Download URL: credex_claudecode-0.1.4.tar.gz
  • Upload date:
  • Size: 25.1 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.10.12

File hashes

Hashes for credex_claudecode-0.1.4.tar.gz
Algorithm Hash digest
SHA256 db249b056c67860a9843d33e8194507f5818e373698981c0e01f35f8eba239dc
MD5 0f9f1716031a83f2bacad47e7385b34f
BLAKE2b-256 e56c8393a509cf69dd8cbc69fdcfb534bfc8dde30729ee85bf35376e058f297d

See more details on using hashes here.

File details

Details for the file credex_claudecode-0.1.4-py3-none-any.whl.

File metadata

File hashes

Hashes for credex_claudecode-0.1.4-py3-none-any.whl
Algorithm Hash digest
SHA256 b067356a049b479ae28b0221722864987ad052acba37f48671ec306431d5e61c
MD5 4369d2a7e1b7be9250afb2d4de6dbb17
BLAKE2b-256 92e658d91373f014b1b06de081e82098198f9e2560f80e320013e0f3bfbc95b9

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page