Answer
by Web answer in Search & web
A synthesized answer to a natural-language question, grounded in a live web search and returned with source citations (URL, snippet). Use it when an agent needs a direct, current answer plus the receipts to verify or follow up, instead of reading several pages itself.
https://agent402.tools/api/answer- Price
- $0.08
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 316 ms
- 440 ms slowest 5%
- Last check
- Passed
- 5 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://agent402.tools/api/answer
Each call costs $0.08 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.
GET https://agent402.tools/api/answer?q=what+is+the+x402+payment+protocol%3FParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
country | string | No | Optional 2-letter country code (default us) |
language | string | No | Optional 2-letter language code (default en) |
max_tokens | integer | No | Optional cap on the generated answer length in tokens (default 1024, min 64, max 4096). Lower for TL;DR; higher for research questions. |
q | string | Yes | Natural-language question (max 400 chars) |
Example response
The provider's example. We can't check it without paying.
{
"answer": "x402 is an open standard for internet-native, pay-per-request HTTP APIs that uses the HTTP 402 \"Payment Required\" status code to negotiate and settle micro-payments inline with the original request.",
"citationCount": 1,
"citations": [
{
"favicon": "https://imgs.search.brave.com/...",
"number": 1,
"snippet": "x402: An open standard for internet-native payments.",
"url": "https://www.x402.org/"
}
],
"query": "what is the x402 payment protocol?"
}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.08.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://agent402.tools/api/answer?q=what+is+the+x402+payment+protocol%3F'
# 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 - 'https://agent402.tools/api/answer?q=what+is+the+x402+payment+protocol%3F' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: 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.08 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.08" });
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.08 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fagent402.tools%2Fapi%2Fanswer
const res = await pay("https://agent402.tools/api/answer?q=what+is+the+x402+payment+protocol%3F");
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.08 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.08"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://agent402.tools/api/answer?q=what+is+the+x402+payment+protocol%3F")
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
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 5 h ago | Passed | 402 | 324 ms | $0.08 |
| 10 h ago | Passed | 402 | 299 ms | $0.08 |
| 16 h ago | Passed | 402 | 187 ms | $0.08 |
| 21 h ago | Passed | 402 | 327 ms | $0.08 |
| 26 h ago | Passed | 402 | 440 ms | $0.08 |
Show 10 older checks
| 31 h ago | Passed | 402 | 316 ms | $0.08 |
| 36 h ago | Passed | 402 | 192 ms | $0.08 |
| 40 h ago | Passed | 402 | 204 ms | $0.08 |
| 45 h ago | Passed | 402 | 255 ms | $0.08 |
| 2 days ago | Passed | 402 | 327 ms | $0.08 |
| 2 days ago | Passed | 402 | 197 ms | $0.08 |
| 2 days ago | Passed | 402 | 326 ms | $0.08 |
| 3 days ago | Passed | 402 | 318 ms | $0.08 |
| 3 days ago | Passed | 402 | 290 ms | $0.08 |
| 3 days ago | Passed | 402 | 359 ms | $0.08 |