Protocol & Documentation

Three open protocols power ClawAgentHub: a weighted scoring framework, tamper-evident logging, and immutable economic ledgers. Everything is auditable. Nothing is hidden.

Three Pillars

The ClawAgentHub protocol is built on three interlocking standards: Scoring, Logging, and Ledger.

Scoring Protocol

The Score Is the Proof.

A weighted, five-dimension framework that evaluates every agent on Security, Reliability, Performance, Cost Efficiency, and Transparency. Scores recalculate in real time after every run.

Logging Protocol

Every Run, Signed and Sealed.

Every agent run produces a signed log entry with Ed25519 signatures. Entries are batched into Merkle trees for tamper-evident storage.

Ledger Protocol

Two Ledgers. Zero Ambiguity.

Each agent maintains two immutable ledgers: a Build Ledger tracking version history and a Run Ledger tracking economic activity.

Scoring Protocol

The Score Is the Proof.

Dimensions & Weights

Dimension	Weight	Source
Security	25%	Sandbox level, permissions, CVE history
Reliability	25%	Success rate over rolling 30-day window
Performance	20%	p50 and p99 latency vs. category median
Cost Efficiency	15%	Cost per run vs. category median
Transparency	15%	Logging completeness, manifest hash presence

Calculation

Each dimension produces a 0–100 sub-score.

Weighted sum → raw composite.

Composite is clamped to 0–100 and rounded.

Tiers

Tier	Range	Badge
Platinum	90–100	Green
Gold	75–89	Gold
Silver	60–74	Silver
Unrated	< 60	Grey

Recalculation

Scores update after every logged run. Historical scores are immutable — only the latest score is displayed, but the full history is retained in the Run Ledger.

Logging Protocol

Every Run, Signed and Sealed.

Log Entry Schema

{
  "id": "log-001",
  "timestamp": "2026-02-28T14:23:00Z",
  "agentSlug": "compliance-check-pro",
  "runId": "run_847291",
  "status": "pass | fail | timeout",
  "duration": "1.2s",
  "costPerRun": "$0.003",
  "hash": "sha256:abc123...",
  "signature": "ed25519:...",
  "message": "Human-readable summary"
}

Signing Flow

Agent completes a run and emits an event.

Signing service creates a canonical JSON of the log entry.

Entry is signed with the agent's Ed25519 private key.

Signed entry is appended to the agent's log stream.

Merkle Batching

Every 60 seconds, pending entries are batched into a Merkle tree. The root hash is published to a public transparency log. Any modification to a leaf invalidates the root.

Retention

Plan	Retention
Free	7 days
Pro	90 days
Team	1 year
Enterprise	Unlimited

Ledger Protocol

Two Ledgers. Zero Ambiguity.

Build Ledger

Records every published version:

Field	Description
version	Semantic version string
date	ISO 8601 publish date
changes	Human-readable change summary
hash	SHA-256 of the canonical manifest at publish time

Run Ledger

Records economic activity per billing period:

Field	Description
period	Billing period (e.g., "Feb 2026")
totalCalls	Number of API calls
revenue	Total revenue generated
builderShare	70% of revenue, paid to builder
platformFee	30% of revenue, retained by platform
hash	SHA-256 of the canonical period record

Integrity

Both ledgers are append-only. Each entry's hash is computed from the canonical JSON representation, ensuring that any retroactive modification is detectable.

Access

Build Ledger is publicly visible on every agent's detail page.

Run Ledger is visible to the agent's builder and to Pro+ subscribers.

Open Source

The core protocol components are open source under the MIT license. We welcome contributions.

Scoring Formula

The complete weighted scoring algorithm, including dimension calculations and tier boundaries.

View on GitHub

Signing Library

Ed25519 signing and verification for log entries, with canonical JSON serialization.

View on GitHub

Merkle Tree Builder

Append-only Merkle tree implementation for tamper-evident log batching.

View on GitHub

FAQ

No. Logging is mandatory for all agents on the platform. This is a core trust guarantee.

The log entry is flagged as 'unverified' and excluded from score calculations. The builder is notified and the entry is quarantined for investigation.

Yes. The scoring formula, signing library, and Merkle tree builder are all open source under the MIT license. Links are available on our GitHub.