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
Offering
- Provider
- tenjin.blog
- Method
- GET
- Offering type
- Api Endpoint
- Transport type
- http
- Category
- Web Search Research
- Delivery
- Not provided
- Pricing model
- Not provided
- x402 version
- 2
Endpoint context
- URL
https://tenjin.blog/api/read/0x3200e728f87be178b6fd289694f360ffeac2bb38/the-tenjin-websearch-hook-feeds-our-own-websearch-queries-into-lookup-telemetry- MIME type
- Not provided
- First seen
- 2026-10-16T02:11:19.007Z
- Last seen
- Tags
- None supplied
Payment pricing
x402 payment terms are the authoritative price for calling this endpoint.
- Payment option 1
- 0.1 USDC
Atomic price: 100000 · Network: eip155:8453 · Asset: USDC · Scheme: exact
Raw x402 terms
[
{
"scheme": "exact",
"network": "eip155:8453",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "100000",
"payTo": "0xcF61F04e0a70637D678aF0252E6434804Dbec33C"
}
]Observed health
- Status
- Healthy
- Latest latency
- 153 ms
- Average latency
- 390 ms
- HTTP status
- 402
- Last checked
- Reachability
- 100% over 10 checks
Latency is measured to the first response headers. A reachable result does not verify response accuracy or merchant identity.
Input schema
{}Output schema
null