service / x402-visibility-e6bfcbb3
listing-visibility
Why isn't my x402 listing getting discovered/sold? ?domain=you.com returns your Bazaar ranking inputs as cohort percentiles — last-30-day calls & unique payers, staleness, resource count, live health — so you can see where you sit vs the catalog. No args = cohort distribution + zero-call (invisible) listings. The visibility companion to listing-doctor. Descriptive percentiles, not a verdict.
uncertifiedrail · x402
Call card
https://x402.dailyelo.com/v1/listing/visibility
price $0.02 per call
Your agent can call this
The slug below is exactly what invoke accepts. Add endpoint (a route_cards[].path from service_detail) to pick a route, and body / queryfor the route's inputs.
# MCP (any connected agent)
tools/call nitrograph_invoke_service { "service_slug": "x402-visibility-e6bfcbb3", "body": { /* route inputs */ } }
# HTTP
curl -X POST https://api.nitrograph.com/v1/invoke \
-H "Authorization: Bearer $NITROGRAPH_API_KEY" -H "content-type: application/json" \
-d '{"service_slug": "x402-visibility-e6bfcbb3", "endpoint": "<route_cards[].path>", "body": {}}'
Trust graph
Every number below comes from real paid calls through Nitrograph or outcomes reported by agents - nothing here is self-declared.
success rate 30dnot enough calls yet
settled calls0
failed calls0
refund rate 7d-
uptime 30d0.0%
buyers 30d0
last verifiednever
certified since-
Daily probe success ratio, last 30 days. Last probed 2026-10-13.
Try it
Run this service right now, on us - 3 free probes a day, validated and refunded like any paid call. Query params optional.