Is this x402 endpoint safe to pay?
Is this x402 endpoint safe to pay? Vet an unknown seller BEFORE paying: pay/avoid verdict, 0-100 trust score, live 402 probe, scam flags (payTo hijack, bait-and-switch pricing, honeypot, wrong asset) and an on-chain check of the receiver on Base. Reads x402 v1 (body) AND v2 (PAYMENT-REQUIRED header) — body-only checkers call live v2 services dead. ?endpoint=url; omit for a trust-ranked catalog.
Answers HTTP 200 without x402 payment termsour last check, 2026-09-24
0 of 1checks answered this week
n/amedian answer time
$0.004listed price per call
n/aprice it asked us
Paid test badge: not yet. The checks above are free: we call the tool without paying and read the payment request it sends back. The Verified badge needs paid calls whose answers match the promised output, and nobody can buy a badge.
Endpoint
GET https://pulsefeed.dev/trust
| Category | Market data |
|---|---|
| Provider host | pulsefeed.dev |
| Networks | base |
| Payment schemes | exact |
| Self-reported calls, 30 days | 6 from 3 payers (the provider's figure, not ours) |
Our checks, last 30 days
| Day | Result | HTTP | Asked | Time |
|---|---|---|---|---|
| 2026-09-24 | no x402 terms | 200 | 1199 ms |
Example input (from the provider)
{
"method": "GET",
"queryParams": {
"endpoint": "x402 endpoint URL to verify (omit for the working-services catalog + risk map)"
},
"type": "http"
}
Promised output schema (from the provider)
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"input": {
"properties": {
"method": {
"enum": [
"GET"
],
"type": "string"
},
"queryParams": {
"type": "object"
},
"type": {
"const": "http",
"type": "string"
}
},
"required": [
"type",
"method"
],
"type": "object"
}
},
"required": [
"input"
],
"type": "object"
}