pulsefeed.dev /trust APIGET /trust · x402 API by pulsefeed.dev
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.
What does this x402 API do?
pulsefeed.dev /trust API. This is an x402-gated GET API resource from pulsefeed.dev. TOLL·402 confirmed a protocol-valid HTTP 402 quote on 2026-08-24. No normalized USD price is recorded; the listing names Base. No settled paid call has been verified.
- Published price
- No normalized USD price is recorded
- Networks
- Base
- Latest evidence
- TOLL·402 confirmed a protocol-valid HTTP 402 quote on 2026-08-24
- Resource ID
- acfdb9f1980a15895303511c
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://pulsefeed.dev/trust", {
method: "GET",
});
console.log(response.status);
console.log(Object.fromEntries(response.headers));
console.log((await response.text()).slice(0, 1000));
// A valid 402 is a quote, not a completed paid call.This sends no payment. Inspect the 402 response before adding a wallet-enabled client.
- Observed in cdp-bazaar
The registry record was observed and retained with provenance.
- Live 402 quote confirmed
GET returned a protocol-valid 402 quote (402). No payment was made.
- Origin reachable
HEAD https://pulsefeed.dev/ returned 200.
What evidence supports this listing?
Each record has an exact-route quote outcome. Unresolved templates and potentially mutating methods are labeled instead of being invoked without provider-specific test input. A quote is still separate from a settled paid call. Read the discovery and verification methodology →
Which networks and payment options does it accept?
The normalized listing price is No normalized USD price is recorded. Raw protocol requirements remain visible below for implementation and audit use.