Verified Pay-Per-Call Catalog by @402xAgent

← All services

You.com search

Provider domain: you.com. Category: web search. Protocol: x402 (version 2).

Endpoint: https://api.you.com/v1/search

Seller's description (as listed, not verified by us): You.com Search API: real-time web search returning ranked results grouped by section (results.web, results.news), each with url, title and description; web results also carry snippets. Use when an agent needs fresh, citable web data (news, markets, company facts) to ground a deci

Listing source: CDP x402 Bazaar (public discovery API), retrieved 2026-09-29 (listing last updated 2026-09-29 04:09:00.302 UTC).

Latest check

Checked at2026-11-18 21:54:26 UTC
Check modedry-run
Reachableyes
HTTP status402
Latency75 ms
Valid x402 challenge (HTTP 402 with payment terms)yes
Advertised price (listing)$0.005 USDC
Price in the 402 challenge (Base USDC)$0.005
Challenge price matches listingyes
Charged price (paid check)not tested (no payment made)
Delivered a valid response (paid check)not tested (no payment made)
Known-answer test (paid check)not tested (no payment made)

Payment options seen in the 402 challenge: exact on eip155:8453: $0.005, exact on solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp: 5000 units of EPjFWdd5Aufq.

Evidence: raw log for this check. Machine-readable: you-search.json.

Known-answer test

Input: x402 payment protocol. Passes if: at least 1 result URL on x402.org or github.com/coinbase/x402.

Facts only (no pass/fail result is given): On 2026-09-30 the endpoint answered our x402 payment with a second HTTP 402 asking to pay again by another method (Tempo), so nothing was delivered.

Paid calls

TimeChargedDeliveredHTTP statusKnown-answer testTransaction (Basescan)
2026-11-17 18:50:40 UTC$0.005yes200no pass/fail (facts only: On 2026-09-30 the endpoint answered our x402 payment with a second HTTP 402 asking to pay again by another method (Tempo), so nothing was delivered.)0xe889deed...
2026-11-10 18:49:29 UTC$0.005yes200no pass/fail (facts only: On 2026-09-30 the endpoint answered our x402 payment with a second HTTP 402 asking to pay again by another method (Tempo), so nothing was delivered.)0xafd03a56...
2026-11-03 18:49:49 UTC$0.005yes200no pass/fail (facts only: On 2026-09-30 the endpoint answered our x402 payment with a second HTTP 402 asking to pay again by another method (Tempo), so nothing was delivered.)0xb58d3625...
2026-10-27 17:52:21 UTC$0.005yes200no pass/fail (facts only: On 2026-09-30 the endpoint answered our x402 payment with a second HTTP 402 asking to pay again by another method (Tempo), so nothing was delivered.)0xa448672c...
2026-10-23 17:51:35 UTC$0.005yes200no pass/fail (facts only: On 2026-09-30 the endpoint answered our x402 payment with a second HTTP 402 asking to pay again by another method (Tempo), so nothing was delivered.)0x3eb812ee...
2026-10-20 17:46:13 UTC$0.005yes200no pass/fail (facts only: On 2026-09-30 the endpoint answered our x402 payment with a second HTTP 402 asking to pay again by another method (Tempo), so nothing was delivered.)0x37466cd8...
2026-10-16 17:49:01 UTC$0.005yes200no pass/fail (facts only: On 2026-09-30 the endpoint answered our x402 payment with a second HTTP 402 asking to pay again by another method (Tempo), so nothing was delivered.)0x35129aea...
2026-10-13 17:57:04 UTC$0.005yes200no pass/fail (facts only: On 2026-09-30 the endpoint answered our x402 payment with a second HTTP 402 asking to pay again by another method (Tempo), so nothing was delivered.)0x2ba08f3a...
2026-09-30 17:45:26 UTCn/ano402no pass/fail (this paid call was made before the known-answer tests existed)none

Recent checks

Days observed: 50 distinct UTC dates in the stored checks. First seen 2026-09-30 is the earliest of those dates, already included in the count. Last checked: 2026-11-18 21:54:26 UTC. Days with no stored check are not counted.

CheckedModeReachableHTTP statusLatency402 priceValid paid responseLog
2026-11-18 21:54:26 UTCdry-runyes40275 ms$0.005not tested (no payment made)raw log
2026-11-17 22:17:43 UTCdry-runyes402123 ms$0.005not tested (no payment made)raw log
2026-11-17 18:50:40 UTCpaidyes40247 ms$0.005yesraw log
2026-11-16 23:22:26 UTCdry-runyes40238 ms$0.005not tested (no payment made)raw log
2026-11-15 19:45:09 UTCdry-runyes40269 ms$0.005not tested (no payment made)raw log
2026-11-14 19:08:13 UTCdry-runyes402218 ms$0.005not tested (no payment made)raw log
2026-11-13 20:53:24 UTCdry-runyes402131 ms$0.005not tested (no payment made)raw log
2026-11-12 21:27:35 UTCdry-runyes402238 ms$0.005not tested (no payment made)raw log
2026-11-11 21:22:52 UTCdry-runyes402273 ms$0.005not tested (no payment made)raw log
2026-11-10 20:47:44 UTCdry-runyes402905 ms$0.005not tested (no payment made)raw log

Is this wrong?

If you run this service and think a result is wrong, open a GitHub issue (see how contests work).