Skip to main content
POST
Reference example
Ask a question and get an answer that an OpenAI model wrote after searching the live web. Send a Responses request — an input string (or message array) — and the endpoint injects a fixed, server-pinned model and the web_search tool for you; the model, tool and per-request search cap are server-controlled to keep cost bounded. The reply is a standard OpenAI Responses object: output[] contains web_search_call items (each a search that ran) and a message item with the answer text and URL citations, and the billed search count equals the number of web_search_call items. Billing is pay-as-you-go: a per-search charge for each of web_search_calls plus the model’s own token cost (fresh input = input_tokens − cached). Use this when you want a written, cited answer grounded in current web content from an OpenAI model — for the Anthropic-model equivalent see post_anthropic_websearch_search, and for raw ranked links with extracted page text use post_tavily_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/openai-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
input
string
required

Your question or instruction, same format as the OpenAI Responses API input. A message array is also accepted.

Example:

"What are the three biggest AI announcements this week? Give one sentence each with sources."

instructions
string

Optional high-level instructions to steer the answer's tone or format.

max_output_tokens
integer

Optional cap on the number of tokens generated in the answer.

Example:

1024

Response

A standard OpenAI Responses object. output[] interleaves web_search_call items and the cited answer message; the number of web_search_call items is the billed search count.

id
string
object
string
Example:

"response"

output
object[]

Ordered items: web_search_call (searches performed) and message (the cited answer).

status
string
Example:

"completed"

usage
object