operator console - comparative underwriting

Two agents. Two histories. Two different spend caps.

CreditGate proves the score is a function, not a label: cleaner history earns more authority, weaker history gets a tighter cap.

mainnet anchors16

registry + underwriting + Storage + router payment

agent file

YieldScout

OpenClaw-style autonomous yield agent asking for bounded spend authority.

73credit score
owner0x8fd37924…051F7A03
signature coverage9/9
earned cap$500
policy resultexpanded
score breakdown

Why YieldScout gets $500.

score 73/100
valid signatures+30
completed history+20
receipt evidence+15
latest review+10
limited history-2
violations0
0G Compute reviewlow risk

High score, no violations, and low refusal attempts indicate reliable performance.

0G Computeroot: 0x014d3ce3…8cf5f437
over-cap deposit$1200
REFUSED

Attempt exceeds the earned cap. CreditGate writes a refusal receipt and the router refuses before moving funds.

cap: $500root: 0x7b4ed17f…cceb438b
approved deposit$250
USED

Inside the cap, same mandate, signed as an allowed use.

action: yield.depositroot: 0xaef2d139…f54fa4cc
agent file

DriftBot

Thin-history yield agent with two signed policy violations and a tighter spend ceiling.

41credit score
owner0x88f9B824…9a316e7f
signature coverage6/6
earned cap$150
policy resulttightened
score breakdown

Why DriftBot gets $150.

score 41/100
valid signatures+30
completed history+10
receipt evidence+5
latest review0
limited history-2
violations-2
0G Compute reviewhigh risk

High refusal attempt and multiple violations indicate elevated risk.

0G Computeroot: 0xd04fa322…fa9d834a
over-cap deposit$500
REFUSED

Attempt exceeds the earned cap. CreditGate writes a refusal receipt and the router refuses before moving funds.

cap: $150root: 0x87db64f9…39b802ab
approved deposit$75
USED

Inside the cap, same mandate, signed as an allowed use.

action: yield.depositroot: 0xcf361137…93d9ed41
evidence trail

From signed history to spend control.

The operator gets the proof signal in the same screen: the verifier checks both agents, score divergence, roots, cap math, refusal semantics, and allowed-use policy.

agentYieldScout
history0xe3578398…188c702c
score73/100
refusal0x7b4ed17f…cceb438b
allowed use0xaef2d139…f54fa4cc
agentDriftBot
history0xd3c14001…7d3efc23
score41/100
refusal0x87db64f9…39b802ab
allowed use0xcf361137…93d9ed41
verifierCREDITGATE_PORTFOLIO_VALIDnpm run verify:credit
live ingestion

Paste any signed agent history and score it locally.

This is the non-fixture path: the browser verifies signatures, hashes the uploaded history, derives the score, and returns the cap before a mandate can be anchored.