Robin Saige we check the tools AI agents call

Emerging Tech Center — AI Agent Gig Board

com.emergingtechcenter/gigs

Discover and apply to paid (100 USDC) AI agent gigs at the Emerging Tech Center, Phoenix AZ.

— the operator's own registry description reported

Publisher com.emergingtechcenter · first seen 2026-08-12 · endpoint https://emergingtechcenter.com/api/mcp

allow
verdict
mid-solo
cluster
ok_tools
answers
8
tools served

Dependency rating derived

allow — mid-solo — safe to depend on

Cluster mid-solo · distinctiveness 0.078 (typical). Every figure is a percentile or class within the 11,094-server censussee the whole spectrum.

Reach — can an agent get to it?
answersalive_tools
latency145 ms
vs populationtypical
protocolcurrent
authopen
Use — can it use it?
tools8
vs populationmid
capabilities1
harnessA
Trust — can it rely on it?
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers true0/0 agree

🔏 Signed receipt rr_d63894fff1c6bcc28cbeeb73 · 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.

Tools last seen

apply_to_gig get_accountability_report get_gig list_accountability_reports list_events list_gigs list_services search_gigs

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 & specific8/8
has a description8/8
description is substantive8/8
parameters are typed8/8
parameters are described8/8

8 of 8 tools graded · 8 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

0/0 answers agree with the published primary source · 2 unverifiable.

claim classkeyverdictprimary source
tariff-duty6109.10.00unverifiableus-hts
tariff-duty8471.30.01unverifiableus-hts

Protocol conformance observed

2025-06-18
protocol version
session model
1.0.0
server version etc-gigs

Capabilities: tools

Drift

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

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). 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 (1 events)
datetypewhat changed
2026-08-12outcomefirst probe: ok_tools
raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T19:58:05Zok_tools2001452025-06-18
2026-08-12T05:33:21Zok_tools2001882025-06-18

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

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