Robin Saige we check the tools AI agents call

Saymon RU Data API

com.payforapi/saymon-ru-data-api

Russian company lookup (EGRUL/INN), Cyrillic search, RU page to Markdown. Pay per call in USDC.

— the operator's own registry description reported

Publisher com.payforapi · first seen 2026-08-24 · endpoint https://payforapi.com/mcp

allow
verdict
mid-slow-solo
cluster
ok_tools
answers
17
tools served

Dependency rating derived

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

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

Does it answer? Q1 · observed
answersalive_tools
latency423 ms
vs populationslow
protocolcurrent
authopen
Can it be used? Q4 · observed
tools17
vs populationmid
capabilities4
harnessB
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_d1cc95394b4aaa722d0595e8 · 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 — 2 probes ●evidence ↓
Q2What is it?kind unknown ● evidence ↓
Q3Can it be checked?V n/a for this kind ◐evidence ↓
Q4Did it hold?harness B · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?mid-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 (2 shown, 2026-08-30 → 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-06inventorytools 11 → 17
2026-08-30outcomefirst 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
unclassified15not classifiable from its textTier-1 only until its tools describe themselves
retrieval-public2serves public factstruth-checkable against a public source — the V-ladder applies in full

Tools last seen observed

cbr_rates claude_opus_5_chat company_report gpt_5_6_sol_chat inn_lookup moex_quote pochta_address pochta_delivery pochta_delivery_time pochta_offices pochta_tariff pochta_track pochta_zip ru_page ru_research ru_research_deep ru_search

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 & specific17/17
has a description17/17
description is substantive17/17
parameters are typed17/17
parameters are described0/170/17

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

claim classkeyverdictprimary source
tariff-dutyunmappedunverifiableus-hts

Protocol conformance observed

2025-06-18
protocol version
session model
1.29.1
server version Saymon RU Data API

Capabilities: experimental prompts resources 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:12:47Zok_tools2004232025-06-18
2026-08-30T06:12:29Zok_tools2004432025-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.payforapi/saymon-ru-data-api.svg)](https://robinsaige.com/s/com.payforapi/saymon-ru-data-api)

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 →