Unverified50% confidenceFactExact time
The Muse Wonder API always reasons, and passing reasoning_effort as none returns an HTTP 400 error.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/16/2026
First Seen
Valid until: 1/14/2027
Sources
Related Entities
Related Claims
UnverifiedIn the Responses interface of the Muse Wonder API, reasoning.summary can be set to auto, concise or detailed to request a reasoning summary; summaries are not guaranteed, may return an empty array, and the raw reasoning content is never returned.71% similarUnverifiedMuse Wonder's zero data retention policy disables server-side state, background requests, file uploads, and web search.63% similarUnverifiedDuring the above outage, Anthropic's Messages API requests were unaffected, and model inference itself continued to run as usual.61% similarUnverifiedMuse Wonder's background: true queues the response and returns status: queued, and lifecycle events can be polled via GET /v1/responses/{id}?stream=true; stream: true is not supported on POST, the request body limit is 1 MiB, and cancellation is done via POST /v1/responses/{id}/cancel.61% similarUnverifiedWhen the session history contained web search results that the API could not decrypt, every request previously returned a 400 error; the new version adds fault-tolerant handling for this.61% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1042936API
curl https://kongchang.com/api/v1/knowledge/claims/1042936MCP
get_claim(id=1042936)