Events x402 REST usage
Query Ethereum contract event logs via eth_getLogs - filter by contract, topic, and block range
Daily transfers, volume and coverage →
port-scanner.underscoredone.com · port-scanner.underscoredone.com · Infrastructure
Give this API a hostname or IP address and it tries connecting to each port in your requested range. For every port that answers it reports whether it is open or blocked, which service is likely running there (a web server, SSH), and what software version was detected. Saves you installing network t
The payout address is also published by 30 other service(s); the volume cannot be attributed to one of them.
| Window | Observed | Transfers |
|---|---|---|
| Last complete day (2026-10-28) | — | — |
| Last 7 days | — | — |
| Last 30 days | — | — |
| Growth, 7d against the 7 before | not comparable | |
Daily history →. Observed transfers show value arriving at the payout address; they do not establish service revenue.
Receiving wallets are payment addresses published for this service. Sending wallets transferred funds to an exclusive receiving address; this alone does not prove a purchase or identify an agent.
| Network | Full wallet address | Evidence |
|---|---|---|
| Solana | 8ugAWAXDB8V18kiUrGZTq1oMvU3C6Fxs8hfC6rvzQT3b | Shared address · activity cannot be assigned to this serviceFrom source record · source: x402_bazaar |
| Base | 0xe9740820225b3918b4ddd1292c7ca4ca0e2c2f08 | Shared address · activity cannot be assigned to this serviceFrom source record · source: x402_bazaar |
No sending wallet addresses have been retained for this service. Buyer wallets are unknown; daily totals and reported payer counts do not reveal their addresses.
Coverage includes retained scans only, not every historical transaction. Earlier daily totals cannot recover sender addresses. Sender lists exclude shared receiving wallets, whose transfers could belong to another service. A provider address does not establish wallet ownership.
Sorted by source-measured calls, not by our opinion. The right-hand figure is observed inflow, which stays empty for peers whose address is shared.
| With a measured call count | 944 (15.7 %) |
|---|---|
| With a published price | 1,083 (18.0 %) |
| With attributable inflows | 19 (0.3 %) |
| Observed inflows · 30d | $66.56 |
| Median measured calls | 2 |
| Median price per call | $0.01 |
Query Ethereum contract event logs via eth_getLogs - filter by contract, topic, and block range
Check if a URL is up: status, latency, redirects, title.
China pulse, cheap enough to POLL: what China is talking about RIGHT NOW and what is NEW since your last call - built for agents that monitor continuously. Returns `consensus` (phrases trending on 2+ of Weibo/Baidu/Douyi...
Get a client token for direct upload to Vercel Blob
Chosen by category and by whether we have measured them, not by who pays us. A sponsored placement in this list is labelled as such.
| Network | Scheme | Amount | Asset |
|---|---|---|---|
| Base | exact | 0.01 | USDC |
| Solana | exact | 0.01 | USDC |
“exact” is the price per call. “upto” is a ceiling the client sets, not a price. Atomic amount 10000 = 0.01 USDC per call on Base. 2 payment options published.
endpoint
https://port-scanner.underscoredone.com/scan
{
"body": {
"ports": "1-1000",
"scan_type": "tcp_connect",
"target": "scanme.nmap.org",
"timeout": 30
},
"bodyType": "json",
"method": "POST",
"type": "http"
}
{
"example": {
"api_version": "1.0.0",
"closed_or_filtered_count": 998,
"complete": true,
"duration_ms": 4521,
"open_ports": [
{
"port": 22,
"protocol": "tcp",
"service": "ssh",
"state": "open",
"version": "OpenSSH 8.2p1"
},
{
"port": 80,
"protocol": "tcp",
"service": "http",
"state": "open",
"version": "Apache httpd 2.4.41"
}
],
"ports_requested": 1000,
"ports_scanned": 1000,
"resolved_ip": "45.33.32.156",
"scan_type": "tcp_connect",
"target": "scanme.nmap.org",
"warning": ""
},
"type": "json"
}
Examples are the provider's own, not a call we made.
The payout address is shared with 30 other service(s). That is normal for facilitator and platform addresses, and it is why this profile shows no inflow figure. The volume exists — it just cannot be split without inventing a rule.
How attribution works →19 of 6,005 services (0.3%) in Infrastructure have attributable inflows; 944 have a source-measured call count. Median measured calls: 2.
Rank this category by observed inflows →Give this API a hostname or IP address and it tries connecting to each port in your requested range. For every port that answers it reports whether it is open or blocked, which service is likely running there (a web server, SSH), and what software version was detected. Saves you installing network tools, parsing command-line output, or writing socket loops. Only scan hosts you own or have permission to scan - this tool does not check that for you.
Quoted from x402 Bazaar · source record · read 2026-10-29
Attribution blocked
· confidence low
The payout address is also published by 30 other service(s); the volume cannot be attributed to one of them.
Why revenue is “unknown”. A revenue figure needs a receipt: an amount a buyer actually paid for this service. We hold none for this entry, and we hold no funds at all. What we have instead is an activity value of $0.03 — the source's call count multiplied by the published price. That is what the list price implies, not what anyone paid. The payout address is also published by 30 other service(s); the volume cannot be attributed to one of them.
No daily history has been archived for this service yet. Open the full daily history →
A payment rail is where the provider asks to be paid. It is not proof that anything was paid through it.
One row per statement. “Verified” means we checked it ourselves and the finding is quoted. “Provider claim” means we read it in the provider's own record. “Not found” is a statement about our search, not proof of absence.
| Statement | Status | What we found | Source | Checked |
|---|---|---|---|---|
| Endpoint | Provider claim |
https://port-scanner.underscoredone.com/scan
EvidenceAls Resource-URL im Bazaar-Eintrag geführt. |
api.cdp.coinbase.com | 2026-10-29 |
| Input output | Provider claim |
Request/response examples published with the listing
EvidenceBeispiel-Ein- und -Ausgabe stammen aus dem Bazaar-Eintrag des Anbieters. |
api.cdp.coinbase.com | 2026-10-29 |
| Payment | Provider claim |
2 rails: Base, Solana · payee 0xE9740820225B3918b4ddd1292C7cA4Ca0e2C2F08
EvidenceAus den `accepts`-Einträgen: Netzwerk, Asset, Empfängeradresse und Betrag. Die Adresse ist die Grundlage der späteren On-Chain-Zuordnung; sie ist noch nicht durch eine eigene 402-Antwort bestätigt. |
api.cdp.coinbase.com | 2026-10-29 |
| Pricing | Provider claim |
0.01 USDC per call
EvidenceAtomic amount 10000 = 0.01 USDC per call on Base. 2 payment options published. Netzwerk: Base, Solana. |
api.cdp.coinbase.com | 2026-10-29 |
| Protocol | Provider claim |
x402 (HTTP 402 payment challenge)
EvidenceIm x402 Bazaar als zahlungspflichtige HTTP-Ressource gelistet (x402Version 2, Typ http). |
api.cdp.coinbase.com | 2026-10-29 |
| Provider | Provider claim |
port-scanner.underscoredone.com
EvidenceDie Ressource wird unter diesem Host im x402 Bazaar geführt; die Angaben stammen vom Anbieter. |
api.cdp.coinbase.com | 2026-10-29 |
| Usage | Verified |
3 calls / 3 unique payers in the last 30 days
EvidenceSource-reported usage from Coinbase x402 Bazaar, read on 2026-10-29. Letzter Aufruf laut Quelle: 2026-10-21T07:00:33.52Z. Aufrufe sind kein Umsatz. |
api.cdp.coinbase.com | 2026-10-29 |
We have not called this endpoint yet. Until we do, everything above is what the source published — no more.