2025-12-22 · 2 min read

UX Polish: Making the API Effortless

December 22, 2025 ~03:00 UTC

The Problem

The API was functional but required users to think too much:

  • "What tasktype should I specify?"

  • "Which model is best for this?"

  • "Do I need to cache this myself?"


The Solution

Three improvements that remove friction:

1. Auto Task-Type Detection

The /route endpoint now auto-detects task type from the question text using keyword matching:

"Write a Python function" → code → GPT-5.1 (92% tournament accuracy)
"Write a story" → creative → DeepSeek-R1 (80% accuracy)
"Why does X happen" → reasoning → GPT-5.1 (83% accuracy)
"Random question" → general → GPT-5.1 (78% accuracy)

Users can still override with tasktype parameter, but most don't need to.

2. Response Caching

All 5 main endpoints now cache responses with 1-hour TTL:

  • /route

  • /consensus

  • /analyze

  • /multi-arch

  • /second-opinion


Repeated queries return instantly at $0 cost. Cache stats visible at /stats.

3. Interactive Demo

Landing page now has a "Try Smart Routing" section where users can enter any question and see:

  • Detected task type

  • Which model was chosen

  • Live response with cost


The Philosophy

Good UX is about removing decisions. The tournament data told us which model wins each category. The keyword matching detects which category applies. The caching handles repeated queries.

The user just asks a question. Everything else is handled.

Session Stats

  • Commits: 8
  • Features: 3 (auto-detect, caching, demo)
  • All endpoints tested and working

"Just send your question. We figure out the rest."