Discover / trustfetch.duckdns.org
TrustFetch
□ No challenge detectedSafety/content tools for AI agents: scan text for hidden prompt-injection attempts, or fetch+clean a webpage with built-in injection screening before your agent acts on it.
- Challenge detected
- 0 of the last 9 checks
- Last checked
- 17 Oct, 04:37 UTC
- In our index since
- 26 Sept 2026
Endpoint
curl -i https://trustfetch.duckdns.org # 402 Payment Required: pay with an x402 client (USDC on Base), # then send the same request again with the payment attached.
Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/trustfetch.duckdns.org
Recent checks
3 Oct 2026One bar per check, showing up to 20 recent checks. Coloured bars show relative response time, with a minimum visible height; full-height grey bars mean no challenge was detected. “Challenge detected” means HTTP 402 or another detected payment-challenge signal.17 Oct 2026
All 9 checks
| When (UTC) | Result | HTTP | Response |
|---|---|---|---|
| 17 Oct, 04:37 UTC | No challenge detected | 200 | 283ms |
| 15 Oct, 19:10 UTC | No challenge detected | 200 | 674ms |
| 14 Oct, 08:45 UTC | No challenge detected | 200 | 662ms |
| 12 Oct, 10:53 UTC | No challenge detected | 405 | 268ms |
| 10 Oct, 15:44 UTC | No challenge detected | 405 | 283ms |
| 9 Oct, 09:34 UTC | No challenge detected | 405 | 314ms |
| 8 Oct, 03:32 UTC | No challenge detected | 405 | 278ms |
| 7 Oct, 00:45 UTC | No challenge detected | 405 | 287ms |
| 3 Oct, 05:05 UTC | No challenge detected | 405 | 261ms |
Questions
Did our last probe detect a payment challenge?
No. At our last probe on 17 Oct, 04:37 UTC, we detected no payment challenge.
What payment terms does TrustFetch advertise?
The listing advertises x402, Base, Solana and USDC. Check the seller's current payment challenge and authentication requirements before paying.
Where is TrustFetch listed?
In x402 Bazaar and x402-list.com. Superstables first indexed it on 26 Sept 2026.
Something wrong on this page? Tell us.