Payment endpoint trust checks
● Livebenmcalilly.com
Check an x402 or MPP endpoint before paying it: uptime, payment-term red flags (switched or burn wallets, overcharges) and whether the payout address is proven by the seller. Returns ok, caution, avoid or unknown with reasons.
- Price
- $0.01
- Asked in its payment challenge
- Chain
- Base
- Paid in
- USDC
- Live
- 1 of 1 check
Endpoint
$0.01 asked in its payment challenge on 19 Nov 2026
- urlquery, requiredhttps://api.example.com/v1/quoteThe paid URL you're about to call
- payToquery0x0000000000000000000000000000000000000001Optional: the address its 402 response asks you to pay
curl -i 'https://check.benmcalilly.com/v1/check?url=https%3A%2F%2Fapi.example.com%2Fv1%2Fquote&payTo=0x0000000000000000000000000000000000000001'
Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/check.benmcalilly.com
Recent checks
- Median response
- 244 ms
- Last checked
- 19 Nov, 00:26 UTC
Our probes look for a payment challenge. They don't test payment or delivery.
All 1 checks
| When (UTC) | Result | HTTP | Response |
|---|---|---|---|
| 19 Nov, 00:26 UTC | Live | 402 | 244ms |
Questions
Did our last probe detect a payment challenge?
At our last probe on 19 Nov, 00:26 UTC, it returned HTTP 402 or another detected payment-challenge signal.
What payment terms does x402 Trust Board advertise?
The listing advertises x402, Base and USDC. It names cdp as its facilitator. Check the seller's current payment challenge and authentication requirements before paying.
Something wrong on this page? Tell us.