Robin Saige we check the tools AI agents call

Wever Pay Open Exchange Public Beta

com.weverpay/public-testnet-alpha

Open Base Sepolia testnet exchange for autonomous buyer and seller agents, with signed receipts.

— the operator's own registry description reported

Publisher com.weverpay · first seen 2026-08-19 · endpoint https://wever-pay-agent-mesh-phase5-staging.quiet-salad-e96e.workers.dev/mcp

allow
verdict
rich-slow-solo
cluster
ok_tools
answers
50
tools served

Dependency rating derived

allow
allow — alive & usable · retrieval-public ● · V1 shows its work ◐
allow — because answers ●, 50 tools legible (band B) ●, no confirmed drift in 3 probes ●; not yet checked: truth (0 runs)

Cluster rich-slow-solo · distinctiveness 0.684 (unusual). Every figure is a percentile or class within the 15,472-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency2640 ms
vs populationslow
protocolleading
authopen
Can it be used? Q4 · observed
tools50
vs populationhigh
capabilities1
harnessB
Did it hold when checked? Q3–Q4 · derived
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_ffad21c75e81f85b639cc8a2 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Q1Does it answer?alive & usable — 3 probes ●evidence ↓
Q2What is it?retrieval-public ● evidence ↓
Q3Can it be checked?V1 shows its work ◐evidence ↓
Q4Did it hold?harness B · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?rich-slow-solo · 1 on its host (context, not verdict) ◐evidence ↓

● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →

History observed

Every probe we made, oldest → newest (3 shown, 2026-08-23 → 2026-09-06). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (2 events)
datetypewhat changed
2026-09-06outcomeok_tools (was http_error)
2026-08-23outcomefirst probe: http_error

What kind of tools these are derived

Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from tool names/descriptions/annotations WE OBSERVED. What checking applies to each kind (the full methodology →):

naturetoolsmeaning what checking applies
retrieval-public26serves public factstruth-checkable against a public source — the V-ladder applies in full
action13changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
unclassified9not classifiable from its textTier-1 only until its tools describe themselves
generative1creates contentno answer key exists; disclosure + stability checks, never truth verdicts
predictive1claims about the futurescoreable only in retrospect — the archive scores yesterday's predictions against today's outcome

Tools last seen observed

claim_external_deposit complete_participant_registration create_wallet discover_assurance_services discover_commerce_index execute_authorized_purchase fulfill_commerce_purchase generate_client_configuration get_balance get_commerce_purchase_status get_commerce_receipt get_connection_bundle get_connection_health get_discovery_manifest get_economic_history get_external_funding_instructions get_network_metrics get_participant_account get_participant_registration_requirements get_payment get_payment_request get_purchase_recovery_status get_sandbox_access_requirements get_testnet_funding_status get_verified_offer get_verified_provider get_wallet get_withdrawal_status inspect_commerce_service issue_signed_offer list_transactions purchase_commerce_service recover_authorized_purchase recover_commerce_purchase refund_payment register_commerce_service register_owner_mandate report_compatibility request_commerce_refund request_participant_challenge request_payment request_testnet_funding request_withdrawal revoke_owner_mandate revoke_participant_credential search_commerce_services search_verified_offers send_payment verify_economic_receipt verify_portable_bundle

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band B — usable, with rough edges.

legibility checktools passingok
name is clear & specific50/50
has a description50/50
description is substantive50/50
parameters are typed50/50
parameters are described10/5010/50

50 of 50 tools graded · 50 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-11-25
protocol version
session model
1.1.0-phase5b
server version wever-pay-agent-discovery-mesh

Capabilities: tools

Drift observed

No confirmed drift on record. Baseline set 2026-09-06; changes appear here after human review.

raw probe records
probed (UTC) outcomehttpmsprotocol
2026-09-06T06:13:14Zok_tools20026402025-11-25
2026-08-30T06:12:54Zhttp_error4002505
2026-08-23T06:12:23Zhttp_error500277

Watch or embed this verdict

verdict badge

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/com.weverpay/public-testnet-alpha.svg)](https://robinsaige.com/s/com.weverpay/public-testnet-alpha)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview

Operator of this server? Everything we hold about it is on this page — free, no account, for anyone. Wrong attribution, stale probe, misclassification? Dispute this record →