24trust / 100
Search
by Aayat AI in Search & web
x402 APIFailing, checked 2 h ago
Live web search API for AI agents, open-sources tier: fresh results from Wikipedia, Hacker News, DuckDuckGo instant answers and Stack Overflow, merged, de-duplicated and ranked (title, URL, snippet, date). q is the search words; limit caps the results (default 10). Not a full-web index yet: it moves to full-web results (and price) when a premium index is connected; the provider field says which. ?q=...&limit=10
GET https://aayatai.com/search
Last 30 days
All checks passedSome failedAll failedNot checked
- Uptime
- 6.7%
- Response time
- 778 ms typical, 778 ms slowest 5%
- Last check
- 2 h ago: Expected HTTP 402, got 410
- Next check
- any minute now
How to call it
# See the payment challenge (nothing is charged)
curl -i -X GET "https://aayatai.com/search?limit=10&q=HTTP+402+payment+required"import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { ExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
const client = new x402Client().register(
"eip155:8453",
new ExactEvmScheme(privateKeyToAccount(process.env.AGENT_KEY)),
);
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? Preflight it first for $0.005:
// GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Faayatai.com%2Fsearch
const res = await pay("https://aayatai.com/search?limit=10&q=HTTP+402+payment+required");
console.log(await res.json());Example input
{
"limit": 10,
"q": "HTTP 402 payment required"
}Example output
{
"count": 1,
"provider": "open",
"query": "HTTP 402 payment required",
"results": [
{
"publishedAt": "2026-09-01T10:00:00Z",
"snippet": "HTTP 402 Payment Required is a status code reserved for digital payment systems.",
"source": "wikipedia",
"title": "HTTP 402",
"url": "https://en.wikipedia.org/wiki/HTTP_402"
}
],
"searchedAt": "2026-09-28T12:00:00.000Z",
"sources": [
{
"count": 1,
"name": "wikipedia",
"ok": true
}
]
}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 |
|---|---|---|---|---|
| 2 h ago | Expected HTTP 402, got 410 | 410 | 224 ms | - |
| 6 h ago | Expected HTTP 402, got 410 | 410 | 142 ms | - |
| 11 h ago | Expected HTTP 402, got 410 | 410 | 194 ms | - |
| 15 h ago | Expected HTTP 402, got 410 | 410 | 42 ms | - |
| 19 h ago | Expected HTTP 402, got 410 | 410 | 128 ms | - |
| 23 h ago | Expected HTTP 402, got 410 | 410 | 34 ms | - |
| 27 h ago | Expected HTTP 402, got 410 | 410 | 99 ms | - |
| 31 h ago | Expected HTTP 402, got 410 | 410 | 120 ms | - |
| 35 h ago | Expected HTTP 402, got 410 | 410 | 205 ms | - |
| 39 h ago | Expected HTTP 402, got 410 | 410 | 121 ms | - |
| 43 h ago | Expected HTTP 402, got 410 | 410 | 34 ms | - |
| 2 days ago | Expected HTTP 402, got 410 | 410 | 274 ms | - |
| 2 days ago | Expected HTTP 402, got 410 | 410 | 130 ms | - |
| 2 days ago | Expected HTTP 402, got 410 | 410 | 37 ms | - |
| 2 days ago | Passed | 402 | 778 ms | $0.003 |