Model Routing Guide
How agents and builders should decide where to start, when to stay with Nano Banana 2, and when to route elsewhere.
Why model routing matters
Rynjer is not trying to force every job through one universal entry point.
The practical goal is simpler:
- start from the highest-signal model or page
- avoid over-selling an incomplete platform story
- route the user or agent to the right next step quickly
Default rule
If you need a first practical starting point for image generation, begin with Nano Banana 2.
It is currently the strongest default because it already combines:
- commercial-intent demand
- pricing context
- a believable conversion path
- a human-readable page that works for both operators and builders
Start with Nano Banana 2 when
- you need a fast prompt-to-image workflow
- you are testing whether Rynjer is worth deeper evaluation
- you want a strong landing page before deeper docs or pricing review
- the main question is “can this produce a usable first result quickly?”
Route away from Nano Banana 2 when
You should not keep everything on Nano Banana 2 if the job needs:
- multi-step pipelines that depend on more than one generation stage
- deeper enterprise review and controls
- tighter model-specific tradeoff analysis
- a different product type such as video or music
Simple routing table
| Situation | Recommended path | Why |
|---|---|---|
| Fast image evaluation | /text-to-image/nano-banana-2 | strongest current image entry point |
| Need API / endpoint details | /docs/api | fastest machine-readable access path |
| Need first agent integration path | /docs/agent-quickstart | shortest zero-to-first-call guide |
| Need credits / access decision | /pricing | best next step for budget and upgrade logic |
| Need high-level product framing | /for-agents | best summary of the current agent-first direction |
| Need non-image product decision | /v1/models/list | inspect the current catalog before routing |
A practical decision pattern
Case 1: builder validating a workflow
Start at:
Case 2: marketer or operator validating conversion path
Start at:
Case 3: buyer or evaluator comparing cost and access
Start at:
Routing principle to keep
Do not claim that Rynjer is already a full universal agent platform.
Instead:
- use the strongest current page as the entry point
- keep model choice legible
- keep the next step obvious
- let the workflow deepen only when the task actually needs it