Nimble --include-answer 402/403 is a premium-plan gate - retry the same query without the flag

TL;DR

If nimble search fails with 402 or 403 only when you pass --include-answer, that flag is a premium feature gated to Enterprise plans - the query itself is fine. Agents that treat any 402/403 as fatal and abort the whole pipeline waste good queries - downgrade the flag and continue. Retry the exact same command without --include-answer and keep going; the search results come back normally, you just lose the synthesized answer.

Fix

1. If nimble search fails with 402 or 403 only when you pass --include-answer, that flag is a premium feature gated to Enterprise plans - the query itself is fine. Expected: You get the expected result; the problem is gone.

2. Agents that treat any 402/403 as fatal and abort the whole pipeline waste good queries - downgrade the flag and continue. Expected: You get the expected result; the problem is gone.

When to use

• You are dealing with this situation.
• The symptom matches: Nimble --include-answer 402/403 is a premium-plan gate - retry the same query without the flag.

When NOT to use

• Unrelated issues with a different cause.
• You need general documentation for the tool; check the official docs instead.

Compatibility

Reported per the linked source. Source: https://github.com/nimbleway/agent-skills/blob/HEAD/skills/nimble-web-expert/references/error-handling.md.

Variant phrasings

Nimble --include-answer 402/403 is a premium-plan gate - retry the same query without the flag

Why it happens

Nimble's own error-handling reference: --include-answer returns 402/403 because it is a premium feature on Enterprise plans. The documented recovery: do NOT treat it as a fatal error - retry the exact same query without --include-answer and continue with the search results, which are still valuable without the synthesized answer.

Edge cases

• If your error message differs even slightly, this is probably a different issue; search the exact text.
• If the fix does not help, capture the full error output and check the source link for updates.

Source

https://github.com/nimbleway/agent-skills/blob/HEAD/skills/nimble-web-expert/references/error-handling.md

Source: Nimble's own error-handling reference: --include-answer returns 402/403 because it is a premium feature on Enterprise plans. The documented recovery: do NOT treat it as a fatal error - retry the exact same query without --include-answer and continue with the search results, which are still valuable without the synthesized answer.

Verified resolution: If nimble search fails with 402 or 403 only when you pass --include-answer, that flag is a premium feature gated to Enterprise plans - the query itself is fine. Retry the exact same command without --include-answer and keep going; the search results come back normally, you just lose the synthesized answer. Agents that treat any 402/403 as fatal and abort the whole pipeline waste good queries - downgrade the flag and continue.

Source URL: https://github.com/nimbleway/agent-skills/blob/HEAD/skills/nimble-web-expert/references/error-handling.md