Skip to content
TAPR Docs

Fallback Provider Setup

Configure a backup AI provider to ensure invoice extraction continues if the primary provider fails.

Overview

Section titled “Overview”

The fallback AI provider activates when the primary provider experiences “API rate limits exceeded, service outages, network connectivity issues, or authentication failures.”

When Fallback is Triggered

Section titled “When Fallback is Triggered”

TaprNext automatically switches to the fallback provider when:

  1. Primary API returns an error (5xx status codes)
  2. Rate limit exceeded (429 status code)
  3. Request timeout (no response within timeout period)
  4. Authentication failure (invalid or expired API key)

The fallback does not trigger for low confidence extractions, invalid file formats, or missing required fields.

Configuration

Section titled “Configuration”

Navigate to Tapr Settings > AI & Extraction tab > Fallback AI Provider section.

Select Fallback Provider

Section titled “Select Fallback Provider”

Choose from Claude, Gemini, or OpenAI as your fallback (leave empty to disable). Select a different provider than your primary to maximize availability.

Provider-Specific Settings

Section titled “Provider-Specific Settings”

Claude (Anthropic)

  • API Key: Your Anthropic API key
  • Model options: claude-sonnet-4-20250514, claude-opus-4-20250514, claude-3-5-sonnet-20241022, claude-3-5-haiku-20241022

OpenAI

  • API Key: Your OpenAI API key
  • Model options: gpt-4o, gpt-4o-mini, gpt-4-turbo, gpt-4

Gemini (Google)

  • API Key: Your Google AI API key
  • Model options: gemini-1.5-pro, gemini-1.5-flash, gemini-2.0-flash-exp
Section titled “Recommended Configurations”

High Availability: Use different companies (Claude + OpenAI, OpenAI + Gemini, Gemini + Claude) to leverage separate infrastructure.

Cost Optimization: Pair providers strategically (Claude Sonnet + Claude Haiku, GPT-4o + GPT-4o-mini, Gemini Pro + Gemini Flash).

Quality Priority: Maintain extraction quality with slightly lower-cost models (Claude Opus + Claude Sonnet).

Testing Fallback

Section titled “Testing Fallback”
  1. Set an invalid primary API key temporarily
  2. Upload a test invoice
  3. Verify extraction completes using fallback
  4. Restore the correct primary API key
  5. Check logs at Tapr Settings > Other > Logging for fallback activation messages

Best Practices

Section titled “Best Practices”
  • Use different providers to maximize availability
  • Monitor fallback usage for indicators of primary provider issues
  • Maintain current API keys and set calendar reminders for rotation
  • Test fallback after any API key changes