70trust / 100

Answer

by WebLens in Search & web

x402 APIPassing, checked 5 h ago

Grounded answer with inline [n] citations: searches the web, fetches sources, and answers strictly from them.

POST
https://api.weblens.dev/answer
Price
$0.05
per call in USDC
Uptime
95.2%
last 30 days
Response time
850 ms
1.1 s slowest 5%
Last check
Passed
5 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

POST https://api.weblens.dev/answer

Each call costs $0.05 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

POST https://api.weblens.dev/answer
content-type: application/json

{
  "query": "What is the x402 payment protocol?",
  "sources": 3
}

Parameters

ParameterTypeRequiredDescription
querystringYesThe question to answer
sourcesnumberNoHow many web sources to search, fetch, and cite Default: 3.

Example response

The provider's example. We can't check it without paying.

{
  "answer": "x402 is an open payment protocol built on HTTP 402 [1]. It settles USDC payments on Base [2].",
  "answeredAt": "2026-07-25T12:00:00.000Z",
  "citations": [
    {
      "index": 1,
      "title": "x402 Protocol",
      "url": "https://x402.org"
    }
  ],
  "confidence": 0.92,
  "query": "What is the x402 payment protocol?",
  "requestId": "req_answer123"
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.05.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://api.weblens.dev/answer' \
  -H 'content-type: application/json' \
  --data-raw '{"query":"What is the x402 payment protocol?","sources":3}'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://api.weblens.dev/answer' \
  -H 'content-type: application/json' \
  --data-raw '{"query":"What is the x402 payment protocol?","sources":3}' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.05 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.05" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.05 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.weblens.dev%2Fanswer&method=POST
const res = await pay("https://api.weblens.dev/answer", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "query": "What is the x402 payment protocol?",
    "sources": 3
  }),
});
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.05 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.05"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://api.weblens.dev/answer",
        json={
            "query": "What is the x402 payment protocol?",
            "sources": 3,
        },
    )
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
5 h agoPassed4021.1 s$0.05
10 h agoPassed402861 ms$0.05
15 h agoPassed402847 ms$0.05
20 h agoPassed402711 ms$0.05
25 h agoPassed402856 ms$0.05
Show 10 older checks
29 h agoPassed4021.1 s$0.05
34 h agoPassed402882 ms$0.05
38 h agoPassed402920 ms$0.05
43 h agoPassed402910 ms$0.05
47 h agoPassed402534 ms$0.05
2 days agoPassed402830 ms$0.05
2 days agoPassed402511 ms$0.05
3 days agoPassed4021.0 s$0.05
3 days agoPassed402850 ms$0.05
3 days agoPassed402735 ms$0.05