Roundhouse AI

fetchx402

Trace HTTPS redirects for a hostname. Use when you need live hop facts and must not guess. HEAD of https://{domain}/ on :443 (GET if 405/501); follow Location up to 5 hops. HTTPS :443 only after ConnectGuard. Bodies are omitted.

OtherLiveeip155:8453Exactvia cdp
https://api.fetchx402.com/v1/tools/resolve-redirect
HttpRedirectUrl
Calls · 30d
1→ 0%
This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 23 snapshots so far.
$23.02
Verified settled volume
4,598 settlements proven x402 by their on-chain EIP-3009 marker.
$0.0050
Listed price
As published in the catalog. Always read the live 402 before paying.
1
Calls · 30d
Upstream's own call count for this endpoint, not ours.
1
Unique payers · 30d
Last called 2026-08-16 22:26Z
—
Upstream on-chain volume
Reported by the source catalog.
Paid to
0x33236133BecE789D551d0B5c4f9A50095d4b57d3

The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.

Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

Provider

The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.

Accepts

The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.

0.005USDC≈ $0.005 USD
on Base · exact scheme

Pay 0.005 USDC on Base to 0x3323…b57d3. The signed payment is good for 1 minute.

Paid to
0x3323…b57d3
USD Coin contract
0x8335…02913
Payment window
1 minute
As published
5000 smallest units
The catalog’s raw entry
[
  {
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "extra": {
      "name": "USD Coin",
      "version": "2",
      "resourceUrl": "https://api.fetchx402.com/v1/tools/resolve-redirect"
    },
    "payTo": "0x33236133BecE789D551d0B5c4f9A50095d4b57d3",
    "amount": "5000",
    "scheme": "exact",
    "network": "eip155:8453",
    "maxTimeoutSeconds": 60
  }
]

Extensions

{
  "bazaar": {
    "info": {
      "input": {
        "type": "http",
        "method": "GET",
        "queryParams": {
          "domain": "example.com"
        }
      },
      "output": {
        "type": "json",
        "example": {
          "hops": [
            {
              "url": "https://example.com/",
              "index": 1,
              "method": "HEAD",
              "status": 200,
              "peer_ip": "23.215.0.138",
              "location": null
            }
          ],
          "domain": "example.com",
          "final_url": "https://example.com/",
          "hop_count": 1,
          "start_url": "https://example.com/",
          "truncated": false,
          "stop_reason": null
        }
      }
    },
    "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"
            },
            "headers": {
              "type": "object",
              "additionalProperties": {
                "type": "string"
              }
            },
            "queryParams": {
              "type": "object",
              "required": [
                "domain"
              ],
              "properties": {
                "domain": {
                  "type": "string",
                  "description": "Public fully-qualified domain name to start from, such as example.com. We HEAD https://{domain}/ on :443 (GET if HEAD is 405/501), then follow Location up to 5 hops. IPs, localhost, and internal/mDNS names are rejected. Only HTTPS :443 after ConnectGuard. Response bodies are not returned."
                }
              }
            }
          },
          "additionalProperties": false
        },
        "output": {
          "type": "object",
          "required": [
            "type"
          ],
          "properties": {
            "type": {
              "type": "string"
            },
            "example": {
              "type": "object"
            }
          }
        }
      }
    }
  }
}

Provenance

Seen in the source catalog
2026-08-16 22:26Z
Last indexed by Roundhouse
2026-09-15 22:20Z
Last enriched (probe, favicon, geo)
2026-09-23 22:15Z
x402 version
2
Max timeout
60s
Liveness probe
HTTP 402
Report

Hand this page to an agent

Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.

GET api.roundhouseai.io/v0/endpoints

This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 23 snapshots so far. Verified volume counts only settlements with an on-chain EIP-3009 marker.

Open skill.md
Show the prompt
Using Roundhouse, look up the x402 service fetchx402 and tell me whether it is
worth paying: what a call costs, whether the endpoint answered when last probed, and what
its payment record actually shows.

curl -s 'https://api.roundhouseai.io/v0/endpoints?q=fetchx402'
curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>'

Then call it: read the price from the live 402 at https://api.fetchx402.com/v1/tools/resolve-redirect, never from
a cached figure, and pay with an x402 client.

The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except
/v0/unified* and /v0/endpoints. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402,
or use an organization key from https://roundhouseai.io/dashboard/team.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.