Advisor

​

Overview

• The top-level model is the executor.
• advisor.model is the model it may consult.
• In auto mode, the executor decides whether advice is useful.
• In required mode, NanoGPT requires one valid consultation attempt before the executor can return its final answer.
• The executor and advisor must resolve to different model IDs.

​

Chat Completions example

curl https://nano-gpt.com/api/v1/chat/completions \
  -H "Authorization: Bearer $NANOGPT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gpt-4o-mini",
    "messages": [
      {
        "role": "user",
        "content": "Review this database migration plan and identify the riskiest assumption."
      }
    ],
    "stream": false,
    "advisor": {
      "model": "anthropic/claude-opus-4.8",
      "mode": "auto"
    }
  }'

​

Responses API example

curl https://nano-gpt.com/api/v1/responses \
  -H "Authorization: Bearer $NANOGPT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gpt-4o-mini",
    "input": "Review this database migration plan and identify the riskiest assumption.",
    "stream": false,
    "advisor": {
      "model": "anthropic/claude-opus-4.8",
      "mode": "required"
    }
  }'

​

Advisor request object

​

Mode semantics

​

Auto

​

Required

• advisor_required_consultation_missing
• advisor_required_consultation_invalid
• advisor_phase_timeout
• advisor_failed

​

Billing

• If no consultation occurs in auto mode, only the executor call is billed normally.
• If consultation occurs, the initial executor turn, advisor turn, and final executor continuation are separate model calls.
• Every completed model call is billed at its applicable platform model rate.
• Completed earlier phases remain billable if a later phase fails.
• Advisor therefore usually increases both total cost and latency when consultation occurs.

​

Privacy

​

Initial limitations

• Use POST /api/v1/chat/completions or POST /api/v1/responses.
• Be non-streaming (stream omitted or false).
• Use an executor model with function tool-calling support.
• Select one explicit advisor model that resolves differently from the executor.
• Use a platform-billed pay-as-you-go API key.

• Client tools, tool_choice, parallel_tool_calls, legacy functions/function_call, or max_tool_calls, even when empty or disabled.
• Structured output through Chat Completions response_format/structured_outputs or a non-text Responses text.format.
• Fusion.
• Context Memory or memory model suffixes.
• Server-side web search, URL scraping, or YouTube transcript enhancements.
• BYOK headers or body configuration.
• Paid inline moderation headers.
• Subscriptions.
• Accountless x402 or L402 payment.
• Private Mode.
• Responses background: true.

​

Response metadata

• id
• mode
• executor_model
• advisor_model
• requested
• consulted
• successful
• consultation_count
• max_uses
• status
• Per-phase usage
• Per-phase pricing when available

• not_used: an auto executor answered without consultation.
• completed: consultation returned usable advice and the executor produced its continuation.
• failed: consultation was attempted but did not return usable advice; the executor could still produce a final continuation.

​

Timeouts and failure behavior

• An advisor-phase timeout fails open after a valid consultation request and gives the executor a tool result explaining that advice was unavailable.
• An initial-executor or final-continuation timeout terminates the request with advisor_phase_timeout.
• A failed consultation is not retried automatically.

​

TypeScript SDK