Multisage Skill

Query the Multisage API for multi-expert AI answers. Multisage sends your question to Claude, GPT, and Gemini simultaneously, then synthesizes their responses into a single, well-rounded answer — highlighting where they agree, disagree, and what unique insights each provides.

Prerequisites

The multisage CLI must be installed globally:

CODEBLOCK0

An API key is required. Get one at https://multisage.ai/settings (under "API Keys").

API Key Setup (Do This First)

Before running any multisage command, you must ensure MULTISAGE_API_KEY is available in your shell. The env var is often NOT inherited automatically — check and load it explicitly:

CODEBLOCK1

If you get a timeout or authentication error, the most likely cause is a missing API key — always verify it's set before debugging further.

Running from Claude (Important)

When running multisage from Claude or any non-interactive context, always use the -q flag to suppress the interactive spinner (doesn't render in tool output).

Redirect output to a file with > instead of piping through tee, which can cause issues in non-TTY contexts:

CODEBLOCK2

Standard Query

For most questions, run a standard query. This consults all three AI providers and returns a synthesized answer with stage breakdown:

CODEBLOCK3

The default output shows each stage: quick answer, expert synthesis, and debate (if the experts disagree). This costs 1 credit.

Deep Research

For questions that need thorough, in-depth analysis — research topics, complex technical questions, literature reviews — use deep research mode. This launches 3 parallel deep research sessions (one per provider) and synthesizes the results:

CODEBLOCK4

Deep research costs 5 credits and takes 5-25 minutes. The CLI streams progress updates as each provider completes. You can detach with Ctrl+C and check results later.

Output Options

Flag	What it does
INLINECODE5	Suppress spinner (always use from Claude)
INLINECODE6

Show everything: quick answer, individual expert responses, synthesis, debate | | --final-only | Show only the final synthesized answer (skip stages) | | -j, --json | Output as structured JSON | | --deep-research | Use deep research mode (5 credits, 5-25 min) |

Combine flags as needed. For example, -f -q gives full output without a spinner. -j gives structured JSON (useful if you need to parse the response programmatically).

Managing Deep Research

Deep research runs asynchronously. If you start one and need to check on it later:

CODEBLOCK5

The threadId is printed when you start a deep research query.

When to Use Which Mode

• - Standard (multisage -q "...") — Good for most questions. Quick (30-90 seconds), costs 1 credit. Best for factual questions, advice, comparisons, code help.
• Deep Research (multisage -q --deep-research "...") — For thorough analysis. Each provider does its own deep research with web search, then results are cross-referenced and synthesized. Best for research topics, technical deep-dives, market analysis, literature reviews.

Typical Usage from Claude

CODEBLOCK6

Response Structure

The API returns:

• - answer — Final synthesized answer
• INLINECODE16 — List of expert names (or full details with -f)
• INLINECODE18 — Credits consumed (1 for standard, 5 for deep research)
• INLINECODE19 — Initial quick answer before expert consultation
• INLINECODE20 — Synthesized answer incorporating all expert perspectives
• INLINECODE21 — Debate section highlighting disagreements (null if experts agree)

Limits and Errors

• - Questions are truncated to 1000 characters
• 5-minute timeout for standard queries
• API keys must start with INLINECODE22
• Rate limit: 10 requests/minute, 3 concurrent

Status	Meaning
401	Invalid or missing API key
402

Insufficient credits — purchase at https://multisage.ai/pricing | | 429 | Rate limited or too many concurrent requests (check Retry-After header) | | 500 | Server error — try again |

Troubleshooting

Timeout errors are almost always caused by a missing API key — the CLI makes an unauthenticated request that hangs instead of returning a clean error. Fix: verify MULTISAGE_API_KEY is exported (see API Key Setup above).

Diagnostic checklist (run these before retrying):
CODEBLOCK7