75trust / 100

Monitor Www Vs Apex

by www-apex-check in Developer tools

x402 APIPassing, checked 2 h ago

www vs apex check: fetches both https://domain/ and https://www.domain/ (and the http:// variants), reports which one is canonical, whether the other redirects to it, status of each, and any inconsistencies such as one host failing, both serving 200 without redirect (duplicate content), or an http variant not upgrading. $0.01 per domain.

POST
https://intel.rallylive.ca/monitor/www-vs-apex
Price
$0.01
per call in USDC
Uptime
100%
last 30 days
Response time
52 ms
561 ms slowest 5%
Last check
Passed
2 h ago, next in 3 h

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

POST https://intel.rallylive.ca/monitor/www-vs-apex

Each call costs $0.01 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

POST https://intel.rallylive.ca/monitor/www-vs-apex
content-type: application/json

{
  "domain": "github.com"
}

Example response

The provider's example. We can't check it without paying.

{
  "canonical": "github.com",
  "domain": "github.com",
  "issues": [],
  "variants": {
    "https://github.com/": {
      "final": "https://github.com/",
      "status": 200
    },
    "https://www.github.com/": {
      "final": "https://github.com/",
      "status": 301
    }
  }
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.01.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://intel.rallylive.ca/monitor/www-vs-apex' \
  -H 'content-type: application/json' \
  --data-raw '{"domain":"github.com"}'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://intel.rallylive.ca/monitor/www-vs-apex' \
  -H 'content-type: application/json' \
  --data-raw '{"domain":"github.com"}' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fintel.rallylive.ca%2Fmonitor%2Fwww-vs-apex&method=POST
const res = await pay("https://intel.rallylive.ca/monitor/www-vs-apex", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "domain": "github.com"
  }),
});
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://intel.rallylive.ca/monitor/www-vs-apex",
        json={
            "domain": "github.com",
        },
    )
    print(res.status_code, res.text)

Security scan

1 finding

  • Payment address changed recently in payment
    Payment address changed from 0x91D568599fB802Cb3f03F067D2063785dBAF0abd to 0xFC24FD34da9e49A0110DCaEe3Ad30eC54175eBB3

Recent checks

WhenResultHTTPTimePrice
2 h agoPassed40253 ms$0.01
13 h agoPassed402405 ms$0.01
23 h agoPassed402561 ms$0.01
33 h agoPassed402122 ms$0.01
43 h agoPassed402177 ms$0.01
Show 10 older checks
2 days agoPassed402162 ms$0.01
2 days agoPassed402115 ms$0.01
2 days agoPassed40247 ms$0.01
3 days agoPassed40247 ms$0.01
3 days agoPassed40259 ms$0.01
3 days agoPassed40258 ms$0.01
3 days agoPassed40259 ms$0.01
3 days agoPassed402342 ms$0.01
3 days agoPassed40237 ms$0.01
4 days agoPassed40243 ms$0.01

History

11 Oct 2026Payment address changed from 0x91D568599fB802Cb3f03F067D2063785dBAF0abd to 0xFC24FD34da9e49A0110DCaEe3Ad30eC54175eBB3