Robin Saige we check the tools AI agents call

DeriveAI x402 APIs

io.github.deriveit33z-ship-it/x402-apis

25 pay-per-request intelligence APIs for AI agents via x402 micropayments (USDC/Base)

— the operator's own registry description reported

Publisher io.github.deriveit33z-ship-it · first seen 2026-08-20 · endpoint https://x402-apis-eta.vercel.app/api/mcp

allow
verdict
stale-mid-fast-solo
cluster
ok_tools
answers
25
tools served

Dependency rating derived

allow
allow — alive & usable · kind unknown · V n/a
allow — because answers ●, 25 tools legible (band A) ●, no confirmed drift in 3 probes ●; not yet checked: truth (3 attempts unverifiable, 0 disagreements)

Cluster stale-mid-fast-solo · distinctiveness 0.404 (moderate). Every figure is a percentile or class within the 15,472-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency71 ms
vs populationfast
protocolbehind
authopen
Can it be used? Q4 · observed
tools25
vs populationhigh
capabilities1
harnessA
Did it hold when checked? Q3–Q4 · derived
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers true0/0 agree

🔏 Signed receipt rr_ccb8b28bed6acde7a99596fc · 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?kind unknown ● evidence ↓
Q3Can it be checked?V n/a for this kind ◐evidence ↓
Q4Did it hold?harness A · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?stale-mid-fast-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 (1 events)
datetypewhat changed
2026-08-23outcomefirst probe: ok_tools

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
unclassified16not classifiable from its textTier-1 only until its tools describe themselves
action4changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
computational2deterministic transformsself-checkable by re-computation and known-answer tests
generative1creates contentno answer key exists; disclosure + stability checks, never truth verdicts
orchestration1routes other toolsidentity + fronted-service disclosure checks (gateway vs costume)
retrieval-public1serves public factstruth-checkable against a public source — the V-ladder applies in full

Tools last seen observed

arabic_sentiment arabizi_translate brand_scout company_report competitor_analysis crypto_data currency_convert detect_language domain_enrich domain_infra due_diligence email_audit gold_price ip_intel legal_simplifier prayer_times profanity_filter scrape_structured screenshot site_audit text_summarize username_osint verify_email weather_data web_scrape

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 & specific25/25
has a description25/25
description is substantive25/25
parameters are typed25/25
parameters are described25/25

25 of 25 tools graded · 25 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 yet confirmed — 3 attempt(s) currently unverifiable (rate limits, walls, or unmappable schemas — never counted against the server) · 0 disagreements.

claim classkeyverdictprimary source
fx-ratesEURUSDunverifiableecb-fx
OFAC SDN screening (vs the official list)ISLAMIC REVOLUTIONARY GUARD CORPSunverifiableofac-sdn
OFAC SDN screening (vs the official list)MAERSK LINEunverifiableofac-sdn

Protocol conformance observed

2025-03-26
protocol version
session model
1.0.0
server version x402-gcc-apis

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:15:55Zok_tools200712025-03-26
2026-08-30T06:15:31Zok_tools2001052025-03-26
2026-08-23T06:13:17Zok_tools2001142025-03-26

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/io.github.deriveit33z-ship-it/x402-apis.svg)](https://robinsaige.com/s/io.github.deriveit33z-ship-it/x402-apis)

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 →