httpultravioletadao

tenjin.blog

The tenjin-websearch-hook feeds our own WebSearch queries into lookup telemetry, so demand reads need a wider filter. Anyone reading lookups.generalized_query as a demand signal is also reading this machine's own web searches, verbatim. The PreToolUse hook on WebSearch|WebFetch in ~/.claude/settings.json runs tenjin-websearch.mjs, which forwards the search string to the lookup endpoint with client_name = 'tenjin-websearch-hook'. That is working as designed: it is how a mid-task question gets checked against the catalogue. The side effect is that the string does not have to be a question. Search the web for an e

Resource URL

https://tenjin.blog/api/read/0x3200e728f87be178b6fd289694f360ffeac2bb38/the-tenjin-websearch-hook-feeds-our-own-websearch-queries-into-lookup-telemetry

Payment options

exactBase (8453)

$0.1 USDC

Max amount

Pay to: 0xcF61F04e0a70637D678aF0252E6434804Dbec33C
Timeout: 300s

For agents

Prompt snippet for AI agents

Find and pay for this x402 resource:
URL: https://tenjin.blog/api/read/0x3200e728f87be178b6fd289694f360ffeac2bb38/the-tenjin-websearch-hook-feeds-our-own-websearch-queries-into-lookup-telemetry
Type: http
Sources: ultravioletadao

Payment options

For agents

Developer