x402 List

x402 Protocol Service Directory

●

ProfitCollector Utility Node

Data PAYMENT-READY

payment-ready until 2026-10-06

Deterministic utility APIs paid per request with x402 on Base.

Pay from $0.005 per request in USDC on Base, settled onchain via the x402 protocol, no signup, no API key needed.

measured since 2026-08-29 (start of our harvest window) · $2.29 all-time · settled via coinbase

BASE URL https://api.bakhour.ca │ WEBSITE https://api.bakhour.ca │ ENDPOINTS 1 │ NETWORK Base │ ASSET USDC │ MEMBER SINCE 2026-08-31 │ MONITORED SINCE 2026-08-31

VERDICT

ranking generation 3

solid 81/100 #226 of 331 in Data by measured score

What the score read on this service: status online, 100% uptime 30d, 5739ms response p95, x402 compliance 14 of 14, $0.005 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.

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 331 listings, this one among them. That set is wider than the 331 the position above is counted against, 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.

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.

ALTERNATIVES IN DATA

Other Data services in this directory, ordered by the same measured score. The figures are ours: 30-day uptime from our own probes, 30-day settlement volume read on-chain (a conservative undercount, and null where we cannot measure it, never a zero).

Ranked alternative x402 services in the same category, with band, measured score, 30-day uptime and 30-day on-chain settlement volume
SERVICE BAND SCORE UPTIME 30D VOL 30D
SniperX•x402 strong 95 100% $298.60
glim.sh strong 94 100% $25.67
cn402 strong 93 100% $34.87
x402node strong 93 100% $34.87
twit.sh solid 92 100% $32.22
5 of 330 other ranked services in Data · see the whole category

ASSESSMENT

updated 5h ago

The parts the verdict above is computed from, each with its proof. Click any chip. Measured values stay read-only; unknown is honest, and an unknown is never counted as a zero.

reliability 100%
uptime · latest daily rollup
-
uptime 7d
100%
uptime 30d
100%
uptime 90d
100%
response p95
5739ms
avg response
1654ms
total checks
2,540

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

compliance A (14/14)

14 of 14 x402 conformance checks pass. Full checklist below.

jump to compliance checklist

price $0.005 (p41 in Data)
price (min)
$0.005
category percentile (min)
p41 in Data
endpoints / prices
1 / 1
model
flat
stability
100%
risk clean

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
2525d
registrar
Go Daddy Domains Canada, Inc
hosting
custom
domain created
2019-10-24

Identity facts, not a risk score.

traction $2.20 30d · 7 buyers · top buyer 95% (address, not entity)
volume 30d
$2.20
buyers 30d
7
settlements 30d
23
measured since
2026-08-29 (start of our harvest window)
last settlement
2026-09-24
top buyer share
95% of 30d volume (address, not entity)
trend 7d vs 30d
0.04x the 30d daily rate
networks
eip155:8453
volume all-time
$2.29
settlements all-time
31
median settlement 30d
$0.005
max settlement 30d
$0.80
settled via
coinbase ($2.20, 23 tx)

Conservative undercount: only USDC settlements via facilitators we measure are counted. A measured floor, not an estimate.

Top buyer share is part of the ranking score: a higher share lowers the traction part of the score, by up to half when one address holds all 30d volume.

WHAT IT DOES

ai-derived

No AI synthesis has been produced for this service yet.

ENDPOINTS

Service endpoints with HTTP method, path, description, pricing, and network
METHOD PATH DESCRIPTION PRICE NETWORK ASSET 402 CHANNEL
GET /dns/lookup $0.005 Base USDC header
1 endpoints

REQUEST / RESPONSE EXAMPLE

An unpaid request to GET /dns/lookup returns HTTP 402 with the payment terms. Settle onchain via your facilitator, then retry with the X-Payment header.

// request
curl -i 'https://api.bakhour.ca/dns/lookup'
// 402 response (captured by monitor) · 1 payload · click to expand
[
  {
    "error": "Payment required",
    "accepts": [
      {
        "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
        "extra": {
          "name": "USD Coin",
          "version": "2"
        },
        "payTo": "0xD6CD12fd5841e5F1dAeb687E4aE041f9d08aC1C3",
        "amount": "5000",
        "scheme": "exact",
        "network": "eip155:8453",
        "maxTimeoutSeconds": 300
      }
    ],
    "resource": {
      "url": "https://api.bakhour.ca/dns/lookup",
      "mimeType": "application/json",
      "description": "DNS record lookup"
    },
    "extensions": {
      "bazaar": {
        "info": {
          "input": {
            "type": "http",
            "method": "GET",
            "queryParams": {
              "domain": "openai.com",
              "record_type": "A"
            }
          },
          "output": {
            "type": "json",
            "example": {
              "domain": "openai.com",
              "answers": [
                "104.18.33.45"
              ],
              "record_type": "A"
            }
          }
        },
        "schema": {
          "type": "object",
          "$schema": "https://json-schema.org/draft/2020-12/schema",
          "required": [
            "input"
          ],
          "properties": {
            "input": {
              "type": "object",
              "required": [
                "type",
                "method"
              ],
              "properties": {
                "type": {
                  "type": "string",
                  "const": "http"
                },
                "method": {
                  "enum": [
                    "GET",
                    "HEAD",
                    "DELETE"
                  ],
                  "type": "string"
                },
                "queryParams": {
                  "type": "object",
                  "required": [
                    "domain"
                  ],
                  "properties": {
                    "domain": {
                      "type": "string"
                    },
                    "record_type": {
                      "type": "string"
                    }
                  }
                }
              },
              "additionalProperties": false
            },
            "output": {
              "type": "object",
              "required": [
                "type"
              ],
              "properties": {
                "type": {
                  "type": "string"
                },
                "example": {
                  "type": "object"
                }
              }
            }
          }
        }
      }
    },
    "x402Version": 2
  }
]

OVER TIME

All charts use the 30d selector; each series spans only the dates it has data for. Every series is also served as JSON at /api/v1/services/profitcollector-utility-node/price, /scores, /volume and /buyers. On-chain volume and distinct buyers are measured over the service's settlement address and are a conservative undercount (only settlements that reach a measured facilitator are counted). The on-chain series roll up hourly, so the latest day can be up to about an hour behind; distinct buyers are counted per payout address, so a service that settles to more than one address is an upper bound.

UPTIME
08-31 · uptime 100.0% · 976ms avg09-01 · uptime 100.0% · 1264ms avg09-02 · uptime 100.0% · 1457ms avg09-03 · uptime 100.0% · 1904ms avg09-04 · uptime 100.0% · 1542ms avg09-05 · uptime 100.0% · 1792ms avg09-06 · uptime 100.0% · 1332ms avg09-07 · uptime 100.0% · 1405ms avg09-08 · uptime 100.0% · 1423ms avg09-09 · uptime 100.0% · 1478ms avg09-10 · uptime 100.0% · 1530ms avg09-11 · uptime 100.0% · 1003ms avg09-12 · uptime 100.0% · 1192ms avg09-13 · uptime 100.0% · 1156ms avg09-14 · uptime 98.9% · 1369ms avg09-15 · uptime 100.0% · 1375ms avg09-16 · uptime 100.0% · 1342ms avg09-17 · uptime 100.0% · 1131ms avg09-18 · uptime 100.0% · 1644ms avg09-19 · uptime 100.0% · 1774ms avg09-20 · uptime 100.0% · 1636ms avg09-21 · uptime 100.0% · 1160ms avg09-22 · uptime 100.0% · 1488ms avg09-23 · uptime 100.0% · 2142ms avg09-24 · uptime 100.0% · 1256ms avg09-25 · uptime 100.0% · 1347ms avg09-26 · uptime 100.0% · 2216ms avg09-27 · uptime 100.0% · 3636ms avg09-28 · uptime 100.0% · 4493ms avg09-29 · uptime 100.0% · 4259ms avg08-3109-29
30D UPTIME 100%
RESPONSE TIME
08-31 · 976ms avg08-31 · 976ms avg09-01 · 1264ms avg09-01 · 1264ms avg09-02 · 1457ms avg09-02 · 1457ms avg09-03 · 1904ms avg09-03 · 1904ms avg09-04 · 1542ms avg09-04 · 1542ms avg09-05 · 1792ms avg09-05 · 1792ms avg09-06 · 1332ms avg09-06 · 1332ms avg09-07 · 1405ms avg09-07 · 1405ms avg09-08 · 1423ms avg09-08 · 1423ms avg09-09 · 1478ms avg09-09 · 1478ms avg09-10 · 1530ms avg09-10 · 1530ms avg09-11 · 1003ms avg09-11 · 1003ms avg09-12 · 1192ms avg09-12 · 1192ms avg09-13 · 1156ms avg09-13 · 1156ms avg09-14 · 1369ms avg09-14 · 1369ms avg09-15 · 1375ms avg09-15 · 1375ms avg09-16 · 1342ms avg09-16 · 1342ms avg09-17 · 1131ms avg09-17 · 1131ms avg09-18 · 1644ms avg09-18 · 1644ms avg09-19 · 1774ms avg09-19 · 1774ms avg09-20 · 1636ms avg09-20 · 1636ms avg09-21 · 1160ms avg09-21 · 1160ms avg09-22 · 1488ms avg09-22 · 1488ms avg09-23 · 2142ms avg09-23 · 2142ms avg09-24 · 1256ms avg09-24 · 1256ms avg09-25 · 1347ms avg09-25 · 1347ms avg09-26 · 2216ms avg09-26 · 2216ms avg09-27 · 3636ms avg09-27 · 3636ms avg09-28 · 4493ms avg09-28 · 4493ms avg09-29 · 4259ms avg09-29 · 4259ms avg08-3109-29
AVG RESP 1674ms
PRICE (captured 402, USD)
08-31 · $0.00509-29 · $0.005$0.00508-3109-29
SUB-SCORES (uptime + x402 compliance)
08-31 uptime: 100.0% compliance: 100% checks09-01 uptime: 100.0% compliance: 100% checks09-02 uptime: 100.0% compliance: 100% checks09-03 uptime: 100.0% compliance: 100% checks09-04 uptime: 100.0% compliance: 100% checks09-05 uptime: 100.0% compliance: 100% checks09-06 uptime: 100.0% compliance: 100% checks09-07 uptime: 100.0% compliance: 100% checks09-08 uptime: 100.0% compliance: 100% checks09-09 uptime: 100.0% compliance: 100% checks09-10 uptime: 100.0% compliance: 100% checks09-11 uptime: 100.0% compliance: 100% checks09-12 uptime: 100.0% compliance: 100% checks09-13 uptime: 100.0% compliance: 100% checks09-14 uptime: 99.9% compliance: 100% checks09-15 uptime: 99.9% compliance: 100% checks09-16 uptime: 99.9% compliance: 100% checks09-17 uptime: 99.9% compliance: 100% checks09-18 uptime: 99.9% compliance: 100% checks09-19 uptime: 99.9% compliance: 100% checks09-20 uptime: 99.9% compliance: 100% checks09-21 uptime: 99.9% compliance: 100% checks09-22 uptime: 99.9% compliance: 100% checks09-23 uptime: 100.0% compliance: 100% checks09-24 uptime: 100.0% compliance: 100% checks09-25 uptime: 100.0% compliance: 100% checks09-26 uptime: 100.0% compliance: 100% checks09-27 uptime: 100.0% compliance: 100% checks09-28 uptime: 100.0% compliance: 100% checks09-29 uptime: 100.0% compliance: 100% checksuptimecompliance08-3109-29

checklist grew 11->14 on 2026-07-28; a step here is a metric change, not a regression

PILLARS OVER TIME (measured)

Measured site and economics pillars from the assessment history, so the latest value shown elsewhere on this page reads as a point on a trend rather than a permanent state.

VOLUME (on-chain settlement, USD)
09-04 · $0.0609-09 · $0.0109-14 · $0.0109-17 · $0.0109-24 · $0.02peak $0.0609-0409-24
DISTINCT BUYERS
09-04 · 1 buyer09-09 · 1 buyer09-14 · 1 buyer09-17 · 1 buyer09-24 · 1 buyerpeak 1 buyer09-0409-24

COMPLIANCE

14/14 checks pass · grade A

last 402 captured 2026-08-31 · last up 2026-09-29

  • 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

SITE PILLARS

  • homepage reachable
  • openapi doc
  • pricing page
  • llms.txt
  • robots.txt
  • terms page
recent checks (18) live · click to expand
TIME STATUS RESP CAUSE
● SLOW 3635ms
● SLOW 5532ms
● SLOW 5367ms
● SLOW 5015ms
● SLOW 3694ms
● SLOW 4757ms
● SLOW 4026ms
● OK 2230ms
● SLOW 4647ms
● SLOW 3303ms
● SLOW 2939ms
● SLOW 4994ms
● SLOW 5219ms
● SLOW 3749ms
● SLOW 5075ms
● SLOW 4261ms
● SLOW 4622ms
● SLOW 3686ms

EMBED THIS BADGE

Show that ProfitCollector Utility Node is monitored on x402-list. Paste this on your site or README, it links back to this live listing.

ProfitCollector Utility Node listed on x402-list
status
ProfitCollector Utility Node uptime on x402-list
live uptime
// HTML
<a href="https://x402-list.com/services/profitcollector-utility-node?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/profitcollector-utility-node.svg" alt="ProfitCollector Utility Node listed on x402-list" height="28">
</a>
// Markdown
[![ProfitCollector Utility Node on x402-list](https://x402-list.com/badge/profitcollector-utility-node.svg)](https://x402-list.com/services/profitcollector-utility-node?utm_source=badge&utm_medium=referral&utm_campaign=embed)
// HTML · live uptime variant
<a href="https://x402-list.com/services/profitcollector-utility-node?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/profitcollector-utility-node.svg?data=uptime" alt="ProfitCollector Utility Node uptime on x402-list" height="28">
</a>

RUN THIS SERVICE?

Keep this listing accurate: propose changes to the name, description, website, category or add new endpoints to monitor. Ownership is verified with a domain proof and every change is reviewed manually; measured data stays read-only.

[ 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) ]

To request delisting, email info@x402-list.com or update your listing at /services/profitcollector-utility-node/update.