_ registry / mcp + a2a streamable-http · checked 10m ago

Saymon RU Data API

https://payforapi.com

Registry code: 1756c69eae5be1d0

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://payforapi.com/mcp
door code
bf3ea71a17353e4d
protocol
streamable-http ·1.0
authentication
none, x402
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Saymon RU Data API live?
Yes — it answered the hub's last check (checked 10m ago). It answered 100% of checks over the last 30 days.
Is Saymon RU Data API free to use?
Yes — the hub reached it with no key and no payment.
What tools does Saymon RU Data API have?
15 tools: RU Search, RU Research, RU Research Deep, Pochta Zip, Pochta Offices, Company Report (KYB bundle), Pochta Tariff, Pochta Track, ….
Is Saymon RU Data API safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.7%

90 days 99.1%· all time 98.7%

latency
150ms

last good check

priced tools
0

of 15 tools

_ answered our checks, 90 days 1165 checks · signed record
  • unknown → live
  • unknown → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • look up a russian company by tax id
  • track a russian post parcel
  • calculate postal delivery cost and time
  • search the russian-language web
  • get central bank exchange rates
takes → gives
text → data, text
tools
15 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred from the card: no interface answered anonymously and the card declares security schemes

_ what it can do 15 tools
15 auth-required 15 of 15 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • ru_search reads 0.02 USDC auth-required never probed

    Runet web search via Yandex (Russian-language internet) — products, prices, sellers, reviews, $0.02

  • ru_research reads auth-required never probed

    Runet dossier: search + top pages into one Markdown report — seller, product, company, $0.02

  • ru_research_deep reads auth-required never probed

    Deep Runet dossier: 3 searches + up to 10 pages — RU courts, media, registries, $0.05

  • pochta_zip reads 0.01 USDC auth-required never probed

    Russian postal codes by address or office, $0.01

  • pochta_offices reads 0.01 USDC auth-required never probed

    Russian Post offices by postcode or coordinates — pickup points, $0.01

  • company_report reads 0.05 USDC auth-required never probed

    KYB dossier in one payment: official EGRUL check by INN + self-employed (NPD) status + deep Runet dossier (courts, media, registries), $0.05

  • pochta_tariff reads 0.01 USDC auth-required never probed

    Russian Post delivery cost between postcodes — shipping math for checkout, $0.01

  • pochta_track reads 0.01 USDC auth-required never probed

    Russian Post parcel tracking by track number — the only legal RU tracking, $0.01

  • ru_page reads 0.01 USDC auth-required never probed

    Clean Russian-language page to Markdown (trafilatura) — product card, store, news, $0.01

  • pochta_address reads 0.01 USDC auth-required never probed

    RU address normalization to Russian Post standard (index, region, street, house), $0.01

  • pochta_delivery_time reads 0.01 USDC auth-required never probed

    Russian Post control delivery times between postcodes, $0.01

  • moex_quote reads 0.008 USDC auth-required never probed

    Moscow Exchange (MOEX) security quotes — Russian equities, bonds, ETFs, $0.008

  • cbr_rates reads 0.008 USDC auth-required never probed

    Official Bank of Russia (CBR) FX rates — USD/EUR/CNY and other currencies to RUB, daily, $0.008

  • pochta_delivery reads 0.04 USDC auth-required never probed

    Russian Post delivery bundle: clean address + postcode + pickup office + rate and delivery time in ONE payment, $0.04

  • inn_lookup reads 0.01 USDC auth-required never probed

    Russian company check by INN (official EGRUL registry) — merchant KYB before a deal, $0.01

_ try it over a2a through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 1756c69eae5be1d0.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1756c69eae5be1d0/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/1756c69eae5be1d0/badge.svg)](https://brick.blue/agent/1756c69eae5be1d0?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.