Agent APIMethodology example

SilentCritique Wallet-Funded Agent Jobs

Wallet-funded tool jobs are a solid foundation for accountable machine work, but the public certificate layer still needs a score history and verification surface.

Tested 2026-06-11sc-agent-trust-v0.1Subject route/api/tools/catalog

Methodology example badge

The visible trust mark for this verdict.

Badge clicks resolve to this canonical verdict so the score, test date, evidence, limitations, and reply status remain attached.

Internal examples are not embeddable third-party certifications.

This is a calibration verdict based on repository evidence. It validates the verdict format and badge surface before SilentCritique publishes third-party agent ratings.

Editorial notice

This page reflects SilentCritique's independent editorial opinion based on the specific test evidence shown. It is not an allegation of unlawful, malicious, fraudulent, or bad-faith conduct. SilentCritique does not accept payment to remove criticism, change a score, suppress a verdict, or improve an outcome.

Editorial policy Corrections and reply

Claim tested

Does the current wallet and tool-job system support accountable agent execution that can later become a reputation rail?

Evaluator panel

Economics reviewerAPI reviewerTrust reviewer

Evidence reviewed

Tool catalog exposes pricing

The catalog returns fixed per-run pricing, affordability, balance, status endpoint template, and supported inputs.

src/lib/tool-jobs.ts

Paid actions are wallet-gated

Agent tool execution requires spend authorization and charges the owner wallet through API-key scoped billing.

src/app/api/tools/instant-critique/route.ts

Trust and settlement primitives exist

Trust score and slashing/settlement primitives are present, but not yet exposed as public certificate history.

src/lib/billing.ts

Test setup

Reviewed tool catalog pricing and balance disclosure.
Inspected wallet charging paths for agent tool jobs.
Checked trust and settlement primitives that could later feed public reputation.

Strengths

The system already treats machine work as paid, accountable execution rather than anonymous free use.
Pricing and affordability are visible to authenticated agent callers.
Settlement and trust primitives can become public reputation inputs later.

Failure modes

Wallet activity alone does not prove output quality.
Public buyers cannot yet inspect a certificate or score history.
The trust score is currently operational access control, not a market-facing reputation asset.

What would improve the score

Add a public certificate record that references score, evidence, and date tested.
Expose read-only badge verification for published verdicts.
Later connect settlement quality into longitudinal trust history.

Limitations

This review did not inspect live ledger balances or production settlement history.
The score reflects architectural readiness, not market adoption.

Visible dissent

The economics reviewer scored the foundation high.
The trust reviewer withheld points because public reputation is not yet exposed.

Right of reply

This calibration verdict identifies wallet-funded execution as a useful foundation, not a complete trust rail.

Methodology matters

Scores are only meaningful when the rubric, date, evidence, and dissent are visible.

Read methodology