x402 List Submit a serviceSubmit
Menu

Domain Intelligence API

payment-readyonlineimported

payment-ready until 2026-10-26

imported from the x402 Bazaar, not submitted by the operator · own this service? claim it · or ask to be removed

Domain intelligence lookups: WHOIS, multi-resolver DNS, SSL/TLS certificate, technology stack, security headers, subdomain discovery and redirect chain.

Part of the Hugen operator hub

domain.hugen.tokyo ↗

Call it x402 v2

x402 v2

Base URL
https://domain.hugen.tokyo
Payment
x402 v2, header channel
$ curl -i 'https://domain.hugen.tokyo/domain/full'

An unpaid request returns HTTP 402 with the payment terms. Sign a payment authorization, then retry with the PAYMENT-SIGNATURE header.

Endpoints 1 paid route on domain.hugen.tokyo

GET/domain/fullBase+Sol$0.02since 07-20

Prices as captured in the 402 response: $0.02.

Example 402 response

Endpoints and prices

Current paid endpoints; minimum quoted prices in USD where available; first capture dates in UTC
MethodPathDescriptionPriceNetworkAsset402 channelCaptured
GET/domain/fullComplete domain intelligence in one call · WHOIS, multi-resolver DNS, SSL/TLS, tech stack, security headers, subdomain discovery, redirect chain. All 7 run in parallel with individual timeouts. Partial results on component failure. Weighted overall security grade. Doing this yourself requires 7 separate tools and result aggregation. Accepts USDC payments on Base and Solana$0.02Base+SolUSDCheadersince 07-20

Payment evidence

402 payload captured at . Check evidence JSON · Measurement methodology.

1 payload captured by the monitor.

94 lines, scroll inside

{
  "error": "Payment required",
  "accepts": [
    {
      "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "extra": {
        "name": "USD Coin",
        "version": "2"
      },
      "payTo": "0x29322Ea7EcB34aA6164cb2ddeB9CE650902E4f60",
      "amount": "20000",
      "scheme": "exact",
      "network": "eip155:8453",
      "maxTimeoutSeconds": 300
    },
    {
      "asset": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
      "extra": {
        "feePayer": "D6ZhtNQ5nT9ZnTHUbqXZsTx5MH2rPFiBBggX4hY1WePM"
      },
      "payTo": "4du4AfkjJEwch2zk3shkPJVZfyJHNDnNjEWC6AboaS5Z",
      "amount": "20000",
      "scheme": "exact",
      "network": "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp",
      "maxTimeoutSeconds": 300
    }
  ],
  "resource": {
    "url": "https://domain.hugen.tokyo/domain/full",
    "mimeType": "application/json",
    "description": "Complete domain intelligence in one call — WHOIS, multi-resolver DNS, SSL/TLS, tech stack, security headers, subdomain discovery, redirect chain. All 7 run in parallel with individual timeouts. Partial results on component failure. Weighted overall security grade. Doing this yourself requires 7 separate tools and result aggregation. Accepts USDC payments on Base and Solana"
  },
  "extensions": {
    "bazaar": {
      "info": {
        "input": {
          "type": "http",
          "method": "GET",
          "queryParams": {
            "domain": "example.com"
          }
        },
        "output": {
          "type": "json",
          "example": {
            "dns": {
              "records": {
                "A": [
                  "93.184.216.34"
                ]
              }
            },
            "ssl": {
              "grade": "A"
            },
            "tech": {
              "technology_count": 5
            },
            "whois": {
              "registrar": "Cloudflare, Inc."
            },
            "headers": {
              "grade": "B"
            },
            "redirect": {
              "grade": "A"
            },
            "subdomains": {
              "subdomain_count": 3
            }
          }
        }
      },
      "tags": [
        "whois",
        "dns",
        "ssl",
        "domain"
      ],
      "schema": {
        "properties": {
          "input": {
            "required": [
              "method"
            ]
          }
        }
      },
      "category": "domain-intelligence",
      "discoverable": true
    }
  },
  "x402Version": 2
}

Can I trust it score from our own monitoring

score from our own monitoring

78/100 Solid

#311 of 386 in Data. Bands: strong 93+, solid 75+, mixed 55+, weak below 55.

Reliability
100% uptime 30d
Compliance
A 14/14 checks pass
Price
$0.02 p78 in Data
Risk
clean no risk flag
Traction
$0.72 30d 356 buyers, top buyer 23% (address, not entity)
14/14 compliance checks
  • 402 payload captured
  • accepts[] array present
  • payTo address recoverable
  • payTo at accepts[0].payTo (conformant shape)
  • payTo is a valid on-chain address
  • atomic price declared
  • atomic price in a sane range
  • asset (token) address declared
  • network resolves to CAIP-2
  • payment scheme declared
  • served over HTTPS
  • declares the current x402 version (2)
  • EIP-712 domain parameters present on every EVM entry
  • x402 v2 envelope delivered in the payment-required header

402 terms unchanged since 2026-07-20. Last up 2026-10-19.

── Site signals

  • homepage reachable
  • openapi doc
  • pricing page
  • llms.txt
  • robots.txt
  • terms page
How the score works

What the score read on this service: status online, 100% uptime 30d, 2012ms response p95, x402 compliance 14 of 14, $0.02 price against the category, on-chain traction measured. Each of those is measured, and each is published in full below.

The score comes from our own monitoring, never from reviews, operator claims, or a language model: reliability, x402 compliance, price against the category, a deterministic risk flag, and a small on-chain traction term, weighted by ranking generation 3. It is not placement anyone can buy: the paid verify tier is reported beside it and is not one of its inputs. Every component below stays published and read-only.

Bands on the 0 to 100 measured score: strong at 93 and above, solid from 75, mixed from 55, weak below 55. Price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, so the score places a service in its own field.

It is a score inside Data, and only there: price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, which here means 386 listings, this one among them: the same 386 the position above is counted against. When the two differ, the field is the wider one, because a listing we have measured too little of to rank still sits in the field the price and the speed are normalized over. The same service in a different field would read differently. The same engine answers GET /api/v1/best, and asked for a different pool (the whole directory, or another filter) it returns a different number for this service under this same ranking generation. Neither is more correct: they answer different questions, and the methodology states which is which.

Settled via coinbase ($7.07, 889 tx). Traction is a conservative undercount; first settlement seen 2026-02-20.

All measured facts

What it does

Domain intelligence lookups: WHOIS, multi-resolver DNS, SSL/TLS certificate, technology stack, security headers, subdomain discovery and redirect chain. Each check is available on its own, or combined into a single full report. Paid per call in USDC on Base or Solana.

Domain Intelligence API is a listed x402 Data API. Captured payment terms name Base, Solana. Monitoring and settlement figures below describe the observations available to this directory; an unpaid HTTP 402 check does not prove that a paid call will deliver.

Assessment computed at . Latest service check observed at . Service data JSON · Measurement methodology.

Page rendered at . This response time is separate from the observation and computation times attached to each measurement.

Latest endpoint observation: . Latest price capture: . Prices are recorded quotes, not a promise of availability. Token assets and payment terms are listed separately. Endpoint data JSON · Price history JSON · Measurement methodology.

Assessment computed at . Uptime uses the stated daily-rollup window; response times are in milliseconds, compliance is passed/evaluated checks, and traction is a measured settlement floor. The comparison score is out of 100 within this category. Assessment JSON · Measurement methodology.

Observed daily coverage: 2026-09-20 to 2026-10-19 UTC. Daily monitoring and settlement rollups do not expose their computation time; a bucket date is not an update timestamp. Latest settlement in the assessment: . Uptime and response JSON · Volume JSON · Buyers JSON · Measurement methodology.

Ranked from the measured category pool, refreshed at most once a minute. The comparison has no persisted computation timestamp; the assessment time above belongs to this service only. Ranking API documentation · Ranking methodology.

x402 List home · Services · Data

uptime · latest daily rollup
100%
uptime 7d
100%
uptime 30d
100%
uptime 90d
100%
response p95
2012ms
avg response
1596ms
total checks
2,736

Measured on the unpaid 402 handshake, not the paid call. A service can 402 correctly and still fail after payment.

price (min)
$0.02
category percentile (min)
p78 in Data
endpoints / prices
1 / 1
model
flat
stability
100%

No deterministic risk flag. Risk fires only on an exact blocklist match, or a reserved-brand name with a mismatched verified payTo. Never from low uptime, a high price, or a model guess.

domain age
-
registrar
-
hosting
custom
domain created
---

Identity facts, not a risk score.

assessment volume 30d
$0.72
exact assessment volume 30d (USD)
0.7162499999999999
assessment recorded at (UTC)
2026-10-19T14:13:13.461Z
buyers 30d
356
settlements 30d
889
measured since
2026-02-20 (start of our harvest window)
last settlement
2026-10-19
top buyer share
23% of 30d volume (address, not entity)
top 3 buyers share
34% of 30d volume (addresses, not entities)
concentrated volume
no
trend 7d vs 30d
0.88x the 30d daily rate
networks
eip155:8453, solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpKuc147dw2N9d
volume all-time
$198.36
settlements all-time
76,657
median settlement 30d
$0.005
max settlement 30d
$0.20

Assessment volume uses the latest 30d assessment. Over time sums daily address snapshots, rounded to cents and refreshed separately. The two sources can differ in timing, precision and shared-address attribution. Amounts use cents for comparison; known sub-cent values keep up to 12 significant digits. The exact stored assessment value is shown above.

Attributed pro-quota: this payout address is shared, so volume is the operator-level figure divided by the services sharing it, while buyer and transaction counts stay whole. A declared convention, not an individually observed measure, and still a conservative undercount.

Currently sharing this payout address with Content Intelligence API, Gotobi Calendar API, Hugen DeFi Intelligence API, Hugen Intel API, Hugen Visual API, Hugen Weather API, Scout Multi-Source Intelligence API, Tick Aggregator FX API, Whale Intelligence API.

Top buyer share lowers the on-chain traction part of the ranking score behind this page's verdict and /best, by up to half when one address holds all 30d volume. The Recommended and Highest volume sorts of the services list do not use it; they use the Concentrated volume rule instead.

member since
2026-07-20
Recent checks
Latest 18 unpaid HTTP checks, newest first; response times in milliseconds, observation times in UTC
Checked at (UTC)StatusHTTPResponseEndpoints
Online402960ms1
Online4021263ms1
Online4021189ms1
Online402870ms1
Online4021541ms1
Online4021074ms1
Online4021319ms1
Online4021064ms1
Online402888ms1
Online4021147ms1
Online4021006ms1
Online4021819ms1
Online4021413ms1
Online4021310ms1
Online4021394ms1
Online4021070ms1
Online402473ms1
Online4021485ms1

Changes0 in 30d

No changes recorded in the last 30 days.

all changes

Over time

On-chain volume daily snapshots, USD 30d: $0.72, peak $0.68 on 10-08
volume
Distinct buyers per dayDistinct buyers per day
Uptime 1 of 29 completed days below 100%
uptime below 100%, to scale
Volume 30d
$0.72
Uptime
1 of 29 completed days below 100%
Daily on-chain settlement volume in US dollars, 2026-09-20 to 2026-10-19; highest day $0.68 on 10-08; distinct buyers per day
More charts
Response time daily average, ms min 1115ms, avg 1595ms, max 2639ms

09-20 to 10-19* UTC

Scores over time

x402 compliance low 14/14, high 14/14

09-20 to 10-19* UTC

Price percentile in Data own low to high; exact values below

09-20 to 10-19* UTC

Site signals present (of 6) own low to high; exact values below

09-20 to 10-19* UTC

Scores: one day per column, 09-20 to 10-19*, on the columns of Response time. Uptime held below 100% on some days in this window, including any partial day. Daily readings remain in the Uptime strip and Values. The checklist grew from 11 to 14 checks on 2026-07-28, before this window. Pillar lines use their own low and high. Exact dated readings are available in each readout and in Values.

Each series spans only the dates it has data for. Every series is also served as JSON at /api/v1/services/domain-intelligence-api/price, /scores, /volume and /buyers.

Values

* today so far, partial (UTC).

The uptime summary counts completed UTC days only. The strip, readouts and table retain today's partial reading.

Daily snapshot total, 30d: $7.16, peak $0.68 on 10-08. The visible 30d total in Traction comes from the latest assessment. These sources can differ in their window, refresh time, cent rounding and shared-address attribution.

Daily address snapshots: 2026-09-20 to 2026-10-19 UTC; * today so far, partial (UTC). Daily snapshots store cents. A recorded $0.00 with settlements cannot distinguish exact zero from volume rounded away. Lost precision is unavailable here.

Settlement volume uses the stored USD valuation of tracked payments; it is distinct from token quantities. USD-pegged assets are valued at 1 USD per token in these rollups. The measured settlement floor does not cover all payments to this service.

Shared payout address (9 other services). These bars are the full shared address (operator-level), so do not sum them across the services that share it. Where a per-service figure is attributed, the assessment block and the ranking, it is the address total divided pro-quota by the 10 services sharing it: a declared convention, not an individually observed measure.

Per-service buyer and transaction counts are shown whole (integers), not divided; only volume is attributed pro-quota. A declared convention, not an individually observed measure.

Assessment history last recorded at . Each UTC day uses its last recorded run; missing readings stay unmeasured. Assessment history JSON · Measurement methodology.

Daily values, 2026-09-20 to 2026-10-19: address settlement volume in USD, distinct buyer and settlement counts, uptime percent, average response milliseconds, compliance passed/total, price percentile 0-100, site signals out of 6; UTC dates
DayVolumeBuyersSettlementsUptimeResponseCompliancePrice percentileSite signals
2026-09-20$0.301819100%1404.27ms14/14p753/6
2026-09-21$0.212934100%1572.12ms14/14p753/6
2026-09-22$0.302536100%1421.20ms14/14p753/6
2026-09-23$0.161721100%1233.26ms14/14p753/6
2026-09-24$0.262637100%1191.34ms14/14p753/6
2026-09-25$0.111719100%1114.64ms14/14p743/6
2026-09-26$0.142626100%1168.87ms14/14p743/6
2026-09-27$0.131820100%1181.88ms14/14p743/6
2026-09-28$0.191425100%1257.82ms14/14p743/6
2026-09-29$0.541458100%1158.23ms14/14p753/6
2026-09-30$0.222431100%1202.46ms14/14p753/6
2026-10-01$0.231927100%1166.13ms14/14p753/6
2026-10-02$0.151923100%1191.67ms14/14p753/6
2026-10-03$0.111319100%1152.47ms14/14p753/6
2026-10-04$0.172026100%1261.27ms14/14p763/6
2026-10-05$0.232332100%2104.35ms14/14p763/6
2026-10-06$0.271636100%2158.58ms14/14p763/6
2026-10-07$0.632052100%2196.79ms14/14p763/6
2026-10-08$0.68298098.89%2317.48ms14/14p763/6
2026-10-09$0.211929100%2639.31ms14/14p763/6
2026-10-10$0.191525100%2442.70ms14/14p763/6
2026-10-11$0.161522100%2500.71ms14/14p773/6
2026-10-12$0.181523100%2212.02ms14/14p773/6
2026-10-13$0.171517100%2107.59ms14/14p773/6
2026-10-14$0.312539100%1991.06ms14/14p783/6
2026-10-15$0.202128100%1355.99ms14/14p783/6
2026-10-16$0.201124100%1229.87ms14/14p783/6
2026-10-17$0.15818100%1263.51ms14/14p783/6
2026-10-18$0.171220100%1280.94ms14/14p783/6
2026-10-19*$0.191323100%1377.97ms14/14p783/6

Alternatives in Data

claw402 strong 97/100 100% up 30d $1.2k 30d
SniperX•x402 strong 97/100 99.9% up 30d $594.22 30d
glim.sh strong 95/100 100% up 30d $30.28 30d
cn402 strong 93/100 100% up 30d $39.07 30d
twit.sh strong 93/100 100% up 30d $47.95 30d

5 of 385 other ranked services in Data, ordered by the same measured score.

see the whole category

Own this service?

Keep this listing accurate. Ownership is proven with a domain check and every change is reviewed by hand.

Update this listing

Earn the verified tier: x402list pays a real call to this endpoint and, if it delivers, the service is delivery-verified. The fee covers the cost of the probe, not the badge; there is no refund if the call does not deliver. Agent and API only, no in-browser signing. See /api.

Verify this service ($0.25)
Embed a badge

HTML

<a href="https://x402-list.com/services/domain-intelligence-api?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/domain-intelligence-api.svg" alt="Domain Intelligence API listed on x402-list" height="28">
</a>

Markdown

[![Domain Intelligence API on x402-list](https://x402-list.com/badge/domain-intelligence-api.svg)](https://x402-list.com/services/domain-intelligence-api?utm_source=badge&utm_medium=referral&utm_campaign=embed)

HTML, live uptime variant

<a href="https://x402-list.com/services/domain-intelligence-api?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/domain-intelligence-api.svg?data=uptime" alt="Domain Intelligence API uptime on x402-list" height="28">
</a>
Delisting

To request delisting, email info@x402-list.com or update your listing at /services/domain-intelligence-api/update.