Skip to main content
POST
Explain Search Results
Explain a result set you already fetched. Unlike the three search endpoints this one takes a JSON body: search_id (required — the id returned by post_scholar_search_web, post_scholar_search_scholar or post_scholar_search_mixed), plus detail_level (BRIEF / MODERATE / DETAILED), language, and response_mode. ⚠️ Use response_mode: NON_STREAMING. It returns {"message": "…"} as JSON, measured at about 2 KB. The COMPLETE and INCREMENTAL modes emit server-sent events in which each event repeats the whole answer so far — the identical explanation measured 177 KB that way, roughly 90 times larger, and a tool call cannot consume a stream incrementally anyway. It only ever explains an existing search; it cannot run one.

Example

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/scholar/search/explain
  • Availability: enabled
  • Request URL template: https://api.aisa.one/apis/v1/scholar/search/explain
Complete OpenAPI definition Effective request declaration (including authentication and referenced schemas):

Cost and request rules

Request pricing. Default request estimate: $0.01 USD. The final charge depends on actual usage. Your account price may differ; use a request quote where supported.

Authorizations

Authorization
string
header
required

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

Body

application/json
search_id
string
required

ID of the search to explain

detail_level
enum<string>
default:MODERATE

Level of detail in the explanation

Available options:
BRIEF,
MODERATE,
DETAILED
language
string
default:en

Language code for the explanation (e.g., en, zh, ar)

Example:

"ar"

response_mode
enum<string>
default:NON_STREAMING

Format of the explanation response. COMPLETE and INCREMENTAL stream server-sent events; NON_STREAMING returns a JSON response.

Available options:
COMPLETE,
INCREMENTAL,
NON_STREAMING

Response

Successful explanation response. COMPLETE/INCREMENTAL stream text/event-stream; NON_STREAMING returns application/json.

JSON explanation response returned when response_mode is NON_STREAMING.

message
string
required

Generated explanation text.