Skip to main content
POST
Reference example
Ask a question and get an answer that Claude wrote after searching the live web. Send a normal Messages request — a messages array plus max_tokens — and the endpoint injects a fixed, server-pinned model and the web_search tool for you; you cannot override the model or add tools, which keeps cost bounded. Claude decides when to search (up to max_uses searches, default 5), reads the results, and answers with inline citations. The response is a standard Anthropic Messages object: content[] contains server_tool_use (the queries issued), web_search_tool_result (the sources found) and text blocks (the answer with citations), and usage.server_tool_use.web_search_requests reports how many searches were billed. Billing is pay-as-you-go: a per-search charge for each of web_search_requests plus the model’s own token cost; a failed search (HTTP 200 web_search_tool_result_error) is not billed. Use this when you want a written, cited answer grounded in current web content — for open-web research that returns ranked links and page text in one call use post_tavily_search instead, and for the OpenAI-model equivalent see post_openai_websearch_search.
First time? Point any MCP client at https://mcp.aisa.one/mcp — Claude Code, Codex, Cursor, VS Code and the rest. Authorization is OAuth: the client opens a browser, you click Allow once, and there is no key to paste. Your agent then reaches every endpoint through a few meta tools: search, list_categories, get_details and batch_quote are free, batch_use is billed per call. Setup per client is in Connect via MCP; the live tool list and what each call costs are on aisa.one/mcp.
Set this endpoint up in your agent →

Request contract

  • Method and path: POST /apis/v1/anthropic-websearch/search
  • Availability: disabled
This endpoint is disabled and cannot be called. Its historical request, schema and pricing declarations are retained for reference. Complete OpenAPI definition Effective request and pricing declaration (including authentication and referenced schemas):

Cost and request rules

Usage-based billing; Default request estimate: $0.3 USD (not a fixed price). Account-specific pricing and final settlement may differ. Published reference values are not an account-specific quote or a settled charge. For endpoints supporting X-AISA-Cost-Mode: quote, obtain a free quote for your exact request before execution; reconcile the settled cost with response metadata and Usage Logs. USD amounts use 1,000,000 integer micro-USD per dollar.
  • Default request reference estimate (USD): 0.3
  • Cost contract: response_components
  • Published reference multiplier: 1.0
  • Settlement evidence source: response_body
Currently disabled.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
max_tokens
integer
default:1024
required

Maximum number of tokens to generate in the answer. Required by the upstream Messages API.

Example:

1024

messages
object[]
required

Conversation messages, same format as the Anthropic Messages API. The user turn holds your question.

Example:
system
string

Optional system prompt to steer the answer's tone or format.

Response

A standard Anthropic Messages response. content[] interleaves the searches performed and the cited answer; usage.server_tool_use.web_search_requests is the billed search count.

content
object[]

Ordered blocks: server_tool_use (search queries), web_search_tool_result (sources), and text (the cited answer).

id
string
role
string
Example:

"assistant"

stop_reason
string
Example:

"end_turn"

type
string
Example:

"message"

usage
object