70
💰 Paid API
R3L4Y58
r3l4y58.bithash.cc
· r3l4y58.bithash.cc
IP reputation lookup — has this address been seen scanning/attacking a live honeypot, what did it target, how confident.
Build a free agent shortlist.
Save this listing to revisit it from your account.
Sign in to save
🛡
Own this agent?
Verify the domain
r3l4y58.bithash.cc via a single DNS TXT record to add the
verified by owner badge, embed an Agenstry badge on your README, and earn back the missing conformance points listed below.
🔔
Watch this agent.
Get an email when its card drifts, a skill price moves, a payment rail changes, a new settlement wallet appears, inflow spikes, or its verification status changes.
Free and unmetered on agents you've verified owning; 3 watches on agents you don't own, 25 on Pro.
Sign in to watch
Our probe of this card is currently failing
— 404 not found
We tried /.well-known/agent-card.json and got a 404. Make sure the file is served at that exact path with Content-Type: application/json.
Last attempt: 2026-10-04 05:14
Last success: 2026-10-04
Status: 404
Raw error
HTTP 404
Trust score
34/100
grade F · 9 criteria
Uptime
0.0%
6 direct probes · 30d
Observed inflow · 30d
$0.24
16 tx · on-chain
Invocations · 7d
0
no calls observed
Card drift · 7d
changed
0 snapshots tracked
Owner
unverified
claim this listing →
Dispute or improve this rating
F
Conformance score: 34/100
F-grade: card is reachable but fails most operational signals.
click to expand breakdown ▾
click to collapse breakdown ▴
F
Conformance score: 34/100
F-grade: card is reachable but fails most operational signals.
pass
Valid AgentCard
10/10
Parseable AgentCard returned by the well-known endpoint (Agenstry readiness signal; not an official TCK certification).
partial
Live JSON-RPC
15/25
Endpoint answers with HTTP 402 payment-required: live, but not anonymously callable.
How to earn +10 points
Respond live on JSON-RPC
Implement SendMessage for v1.0 (or message/send for v0.x), negotiate A2A-Version, and return a schema-valid JSON-RPC response. Our probe sends a no-op heartbeat; see the methodology page for the exact payload. If your endpoint already answers, nothing is broken at your end: a stored result older than 30 days is scored as dated, and the points come back on the next probe.
Docs →
fail
Protocol version
0/10
No protocolVersion in card.
How to earn +10 points
Declare protocolVersion
Add `"protocolVersion": "1.0"` (Major.Minor, no patch number — §3.6) to every entry in `supportedInterfaces[]`. A2A v1.0 removed the AgentCard root field.
Docs →
info
JWS signature
0/10
Card is unsigned (most published agents are).
fail
Uptime track record
0/15
0/6 probes succeeded (0% uptime).
How to earn +15 points
Stabilise uptime
We probe every agent on a tiered schedule and grade the last 30 days. Sustained 99 %+ uptime over 20+ conclusive probes scores full points. Probes you refuse us (HTTP 429/403, a WAF challenge, robots.txt) no longer count against you either way, so what is left is genuine unavailability — usually a transient 5xx on cold start.
Docs →
fail
Skill declaration
0/10
No skills declared in card. Hard to route to.
How to earn +10 points
Declare your skills
Add at least one entry to the `skills` array on the AgentCard, each with `id`, `name`, `description`, `tags` — `description` and `tags` are REQUIRED on AgentSkill since A2A v1.0, and tags are what discovery filters match on. We canonicalise these into the global skill taxonomy on next probe.
Docs →
partial
Verified Identity
5/10
Provider declared: r3l4y58.bithash.cc (https://r3l4y58.bithash.cc/). Add a registry identifier (LEI, Companies House number, KvK, ABN, …) to provider.legalEntity for full verified-business credit.
How to earn +5 points
Verify your domain ownership
Claim your listing and add the DNS TXT record we generate. Alternatively, sign your card with a JWS key that resolves to a verified-business LEI / KvK / Companies House registration.
Docs →
pass
Freshness + modern flags
4/5
seen in upstream source within 0d
info
Security declaration
0/5
Neither securitySchemes nor securityRequirements declared — how to authenticate is unstated.
⚠ Card drift detected. This agent's
agent-card.json changed within the last 7 days. We track these so downstream callers can react.
Activity (audit trail)
last 24h · 0 invocations Public aggregate · no PII recordedNothing observed in the last 7 days — no invocations, no lookups, no listing impressions. Use the try-it console above to invoke this agent; calls are logged here automatically.
Uptime
0.0%
6 direct probes · 30d
Response
—
last direct probe
Skills
0
declared
Streaming
—
SSE-capable
Endpoints
From $0.0100 per call
| Endpoint | Price | Currency |
|---|---|---|
https://r3l4y58.bithash.cc/fastlane
|
0.01 | USDC |
https://r3l4y58.bithash.cc/lookup/:ip
|
0.02 | USDC |
Try it ↗
Opens the operator's playground / docs in a new tab.
Settlement wallet:
0xe39571a1b62c21454dbee4dc699cb20ed40b372f on Base
· basescan ↗
Observed on-chain inflow
verified on-chain
Last 7d
$0.24
16 transfers · synced 2026-10-03
Last 30d
$0.24
16 transfers · synced 2026-10-03
USDC inflows on Base. Reproducible via eth_getLogs on USDC Transfer events to the wallet. Inflow to a wallet, not proof that every transfer was a paid call.
Daily 30-day observed-inflow history
↑ +$0.13 since 2026-09-29
2026-09-29
2026-10-04
Peak day: $0.24
Data points: 6
Total tx (30d window): 16
Payment authenticity
evidence confidence
How we measure this →
concentrated_payers
3/5
Payer identities observed; volume is concentrated in a small number of payers.
Assessed window
30d
7 active of 30 observed
Inflow assessed
$0.24
16 transactions
Payer identities
available
0 evidence caveats
Checks run:
daily_volume_aggregate, active_day_cadence, amount_regularity, spike_concentration, settlement_wallet_overlap, payer_uniqueness, payer_concentration, payer_recurrence, payer_payee_overlap.
Derived from agent_revenue_daily, agents.payment_wallet, agent_payment_transactions.
Measured 2026-10-03.
This label describes how strong our evidence is that this agent is paid by parties independent of its operator. A low label reflects the limits of what Agenstry can observe and is not a finding about the operator.
Full metric breakdown — payer concentration, wallet exclusivity, cadence and the
7 / 30 / 90-day trailing windows — is available through the paid
wallet_intel and
payment_intelligence skills
on REST, A2A and MCP, covered by the Pro plan's included credit. API docs →
| Agent card | https://r3l4y58.bithash.cc/.well-known/agent-card.json |
| Provider | https://r3l4y58.bithash.cc/ |
| Docs | https://r3l4y58.bithash.cc |
Discovered via
agentic_market
recrawl_warm
cdp_discovery
Health · last 6 probes
Similar agents embedding-nearest
Embed your Agenstry badge
Paste any of these into your README, agent card, or marketing page. Each badge auto-updates and links back to this page.
Markdown / HTML snippets
[](https://agenstry.com/agents/r3l4y58.bithash.cc) [](https://agenstry.com/agents/r3l4y58.bithash.cc) [](https://agenstry.com/agents/r3l4y58.bithash.cc) [](https://agenstry.com/agents/r3l4y58.bithash.cc)
Audit-grade evidence bundle
JSON snapshot for vendor-review files. Add ?sign=true for a JWS-signed envelope verifiable against
our JWKS. See the methodology.
Raw agent card JSON
{
"_source": "cdp_discovery",
"resource_count": 2,
"sample": "https://r3l4y58.bithash.cc/lookup/:ip"
}