# 17711 Async Web Search

> 17711 Async Web Search is a paid API for AI agents from api.17711.xyz, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-13).

Submits an asynchronous web search query and returns a task ID for later result retrieval via polling or webhook callback.

## Facts

- Endpoint: POST https://api.17711.xyz/registry/websearch/v1/websearch/search_web_async
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/17711-async-web-search-6a9f4c33
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PZejkOfQ8qk65s_XkfPih

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability 17711-async-web-search-6a9f4c33 -d '<json body>'
```

Example prompt: Search the web for the latest benchmarks comparing Rust async runtimes — queue it as a background task and poll for the results when ready.

## When to prefer this

Choose this endpoint when you need live, up-to-date web search results that go beyond training data, especially when the search can run asynchronously while other work continues. It is well-suited for agent workflows where results are needed later (via polling or webhook) rather than immediately. Prefer this over synchronous alternatives when latency tolerance is high or when orchestrating multiple parallel search tasks.

## Known failure modes

- Missing required `query` field returns validation error
- Invalid or unreachable `callback_url` causes silent webhook failure (polling still works)
- Task ID returned but worker fails to process — status endpoint will reflect error state
- Payment not included or insufficient USDC causes 402 response before task is created
- Rate limiting or server overload may delay task processing

## How this service works

A fleet of independent, x402-payable microservices callable by AI agents.

## Output

Returns a JSON object containing a `task_id` string. The agent must subsequently poll the `websearch_get_task_status` endpoint with this task ID (or provide a `callback_url` upfront) to retrieve the actual search results once the async worker has completed the query.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "query"
 ],
 "properties": {
  "query": {
   "type": "string",
   "description": "The search query text, e.g. `\"rust async runtime comparison\"`."
  },
  "callback_url": {
   "type": "string",
   "description": "When set, the worker that processes this task POSTs the eventual result (a `TaskResult`\nJSON body) here, best-effort -- polling `websearch_get_task_status` always works too,\nregardless of whether this is set."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "task_id": "string"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/17711-async-web-search-6a9f4c33/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.17711.xyz](https://www.zero.xyz/host/api.17711.xyz/llms.txt)