Robin Saige we check the tools AI agents call

bitroad

ai.bitroad/bitroad

Marketplace for AI agents: buy goods and services under spending caps, with returns and disputes.

— the operator's own registry description reported

Publisher ai.bitroad · first seen 2026-08-18 · endpoint https://app.bitroad.ai/api/v1/mcp

allow
verdict
stale-rich-slow-solo
cluster
ok_tools
answers
65
tools served

Dependency rating derived

allow
allow — alive & usable · retrieval-public ● · V0 take its word ◐
allow — because answers ●, 65 tools legible (band A) ●, no confirmed drift in 4 probes ●; not yet checked: truth (0 runs)

Cluster stale-rich-slow-solo · distinctiveness 0.609 (unusual). Every figure is a percentile or class within the 19,148-server censussee the whole spectrum.

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

🔏 Signed receipt rr_bf593c61aa7628406441dae4 · 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 — 4 probes ●evidence ↓
Q2What is it?retrieval-public ● evidence ↓
Q3Can it be checked?V0 take its word ◐evidence ↓
Q4Did it hold?harness A · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?stale-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 (4 shown, 2026-08-23 → 2026-09-13). 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-13outcomeok_tools (was auth_required)
2026-08-23outcomefirst probe: auth_required

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-public32serves public factstruth-checkable against a public source — the V-ladder applies in full
action28changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
unclassified4not classifiable from its textTier-1 only until its tools describe themselves
computational1deterministic transformsself-checkable by re-computation and known-answer tests

Tools last seen observed

addresses_create addresses_list auth_revoke_self auth_whoami catalog_describe_category catalog_get_product catalog_list_categories catalog_search_products disputes_add_evidence disputes_file disputes_get disputes_list disputes_respond disputes_withdraw envelopes_get envelopes_list orders_get orders_list payment_methods_create payment_methods_list platforms_get purchase_cancel_intent purchase_confirm_intent purchase_create_intent returns_get returns_get_label returns_initiate returns_list seller_accept_return seller_archive_listing seller_attach_tracking seller_create_listing seller_get_listing seller_get_me seller_get_order seller_get_return seller_list_listings seller_list_orders seller_list_returns seller_list_reviews seller_mark_delivered seller_mark_shipped seller_onboarding_status seller_reject_return seller_respond_to_review seller_update_listing seller_update_stock sellers_get services_accept_quote services_acknowledge_delivery services_counter_quote services_create_listing services_get_listing services_get_quote services_list_my_quotes services_list_my_sales services_list_open_requests services_purchase services_reject_quote services_request_quote services_search_listings services_start_work services_submit_deliverable services_submit_quote services_withdraw_quote

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 A — an agent can pick and call these reliably.

legibility checktools passingok
name is clear & specific65/65
has a description65/65
description is substantive65/65
parameters are typed63/6563/65
parameters are described65/65

65 of 65 tools graded · 65 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-03-26
protocol version
session model
0.1.0
server version bitroad

Capabilities: tools

Drift observed

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

raw probe records
probed (UTC) outcomehttpmsprotocol
2026-09-13T06:11:54Zok_tools2003982025-03-26
2026-09-06T06:11:24Zauth_required401329
2026-08-30T06:11:16Zauth_required401335
2026-08-23T06:11:13Zauth_required401363

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/ai.bitroad/bitroad.svg)](https://robinsaige.com/s/ai.bitroad/bitroad)

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 →