40
💰 Paid API
Holyterminal
holyterminal.xyz
· holyterminal.xyz
step-by-step x402 settlement trace + fix list
Build a free agent shortlist.
Save this listing to revisit it from your account.
Sign in to save
🛡
Own this agent?
Verify the domain
holyterminal.xyz 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
Last probe error:
gate: missing protocolVersion/capabilities/skills
Last attempt: 2026-10-03 16:24
Last success: 2026-10-03
Status: 200
1 thing in this card we could not use
Everything else was indexed. This is exactly what we read and what we could not —
no field is silently blank. Fix the card at
https://holyterminal.xyz/.well-known/agent-card.json and the next probe clears this panel.
| Field | What we saw | What we stored |
|---|---|---|
capabilities |
Beyond a name and a URL the card declares nothing: no protocolVersion, no capabilities object and no skills. There is no way to tell what this agent does or how to talk to it. | dropped — we read the card but cannot list this agent as callable |
Trust score
33/100
grade F · 9 criteria
Uptime
accumulating
1/5 direct probes · 30d
Observed inflow · 30d
not yet measured
wallet declared · scan pending
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: 33/100
F-grade: card is reachable but fails most operational signals.
click to expand breakdown ▾
click to collapse breakdown ▴
F
Conformance score: 33/100
F-grade: card is reachable but fails most operational signals.
partial
Valid AgentCard
9/10
AgentCard did not read cleanly: 1 field we could not read. Scored on what we could read, not on a card that arrived as published — the card findings name every affected field and what we did with it.
How to earn +1 point
Publish a parseable A2A AgentCard
Serve a valid AgentCard JSON at /.well-known/agent-card.json. The A2A 1.0 schema is the reference; we accept the v0.x backwards-compatible variant too.
Docs →
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).
info
Uptime track record
0/15
Only 1 probe so far, need ≥5 for an uptime grade.
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: holyterminal.xyz (https://holyterminal.xyz/). 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
accumulating
1 direct probes · 30d
Response
35ms
last direct probe
Skills
0
declared
Streaming
—
SSE-capable
Endpoints
This agent accepts x402 payments but did not publish a per-endpoint price map.
Try it ↗
Opens the operator's playground / docs in a new tab.
Settlement wallet:
0xc0180300a00505833c3abedb4ad7a03fec0a0fcf on Base
· basescan ↗
Observed on-chain inflow
verified on-chain
Last 7d
$0.02
1 transfer · 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.
Payment authenticity
evidence confidence
How we measure this →
single_payer_observed
2/5
Payer identities observed; a single payer accounts for effectively all observed volume.
Assessed window
30d
2 active of 21 observed
Inflow assessed
$11.59
2 transactions
Payer identities
available
2 evidence caveats
single_day_concentration —
Most observed volume landed on a single day of the window.
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
get_agent_full and
payment_intelligence skills
on REST, A2A and MCP. API docs →
| Agent card | https://holyterminal.xyz/.well-known/agent-card.json |
| Provider | https://holyterminal.xyz/ |
| Docs | https://holyterminal.xyz/v1/paid/x402-diagnosis |
Discovered via
cdp_discovery
recrawl_warm
Health · last 1 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/holyterminal.xyz) [](https://agenstry.com/agents/holyterminal.xyz) [](https://agenstry.com/agents/holyterminal.xyz) [](https://agenstry.com/agents/holyterminal.xyz)
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": 1,
"sample": "https://holyterminal.xyz/v1/paid/x402-diagnosis"
}