AgentSidekick

Coverage gap: Model Routing

Coverage gap · HypothesisOverall 57.3 / 100 DERConfidence Low DERCalculated

Only 47 indexed products match "Model Routing" by keyword DER, inside a much larger parent category. This is a hypothesis, not a validated market: demand was inferred from the parent and discounted, and a missing record is not proof that anyone wants it. Score 57.3 of 100, confidence Low, as of 2026-11-21.

Not indexed by search engines: coverage-gap hypothesis: demand is a proxy, not measured.

Score breakdown

Contribution = weight × component score. The contributions add up to the overall score.

ComponentWeightScoreScore (0–100)ContributionKind
Demand0.2552.00.25 × 52.0 = 13.00Heuristic
Competition gap0.2066.00.20 × 66.0 = 13.20Measured
Monetisation0.2065.00.20 × 65.0 = 13.00Heuristic
Growth (relative)0.1528.00.15 × 28.0 = 4.20Measured
Feasibility0.1060.00.10 × 60.0 = 6.00Heuristic
Distribution0.1079.00.10 × 79.0 = 7.90Measured
Overall1.0057.30 → 57.3

Solid bars are measured components; dashed outlines are rules of thumb. The full formula is on the radar page.

Confidence: Low

Rule: every coverage gap is Low.

What would raise it

  • Confidence for coverage gaps is fixed at Low: demand is inferred from the parent category. It would rise only with a direct demand measurement for this capability (none is connected), or with researcher review of products the keyword rules missed.

The opportunity

All text in this section is generated by rule from the record. It is a starting point, not research.

Description
Picking the right model per request with fallbacks. Few indexed products offer it, although the surrounding category (Model Gateways & Routing) is large.DER
Problem
Only 47 indexed products match "Model Routing", against 431 in Model Gateways & Routing overall.DER
Target users
Teams already using agents for model gateways & routingHEU
Product form
MCP server, agent skill or pluginHEU
Revenue model
Not assessedHEU
Complexity
Not assessedHEU
Competition level
HighDER
Subject
Model Routing (capability)

Evidence for

4 row(s) from opportunity_evidence.

  • DemandHeuristicHEUvalue 798,807

    The parent category Model Gateways & Routing holds 431 products with 798,807 combined GitHub stars (86th percentile of subcategories). Interest in the parent is only a proxy — demand for this exact capability was not measured — so the percentile is discounted by 40% to 52.

    /categories/agent-infrastructure/models-gateways/model-gateways/

  • Competition gapMeasuredDERvalue 47

    47 indexed products match this capability by keyword.

    /capabilities/model-routing/

  • MonetisationHeuristicHEU

    Rule of thumb by ecosystem (Agent Infrastructure); no pricing data behind it.

  • DistributionMeasuredDERvalue 37

    37 of 47 tracked agent platforms document MCP support.

    /platforms/

Evidence against

3 row(s) from opportunity_evidence.

  • Competition gapHeuristicHEU

    Classification is keyword-based: products that offer this without naming it are not counted, so the real gap may be smaller.

  • Growth (relative)MeasuredDERvalue 167

    167 launches in the parent category in the last 90 days versus 85 in the previous 90.

  • FeasibilityHeuristicHEU

    Technical feasibility was not assessed for this capability; a neutral 60 is used.

Existing products

All Model Routing products

The most notable profiled products matching this capability (up to 8). 47 indexed in total.

plano

Infrastructureby katanemoHEU

7.1k GitHub starspushed 28d agoApache-2.0

otari

Infrastructureby mozilla-aiHEU

959 GitHub starspushed todayApache-2.0

10x

Agent projectby ntegralsHEU

1.4k GitHub starspushed 10mo agoMIT

wesight

Agent skillby freestyleflyHEU

975 GitHub starspushed 13d agoMIT

SandBase

MCP serverby sandbaseaiSRC

186 GitHub starspushed 10d agoApache-2.0

ai-runtime-lab

Infrastructureby Ali-hey-0HEU

183 GitHub starspushed 4mo agolicence unknown

Where it could be distributed

All platforms

37 of 47 tracked agent platforms document MCP support CUR, so one MCP server could reach all of them. No pairing has been tested.

ContinueOpenCodeClaude CodeCodexGemini CLIZedOpenHandsClineWarpgooseQwen CodeRoo Code+25 more

Channels: Official MCP Registry listing, plugin marketplaces for Claude/Cursor/Codex, and the integration vendor's own app directory where one exists. HEU

Data coverage

Indexed products
47DER
With a full profile
8+DER
Launches, last 90 days
16 vs 12 in the 90 beforeSRC
Segment calculated
Score calculated

Risks and counterarguments

  • This is a hypothesis: demand is inferred from the parent category, not measured.
  • A low count can mean low demand rather than an unmet need — a missing record is not proof of a market.
  • Keyword classification under-counts products that do not name this capability.
  • Classification is keyword-based: products that offer this without naming it are not counted, so the real gap may be smaller.
  • 167 launches in the parent category in the last 90 days versus 85 in the previous 90.
  • Technical feasibility was not assessed for this capability; a neutral 60 is used.

Assumptions

What has to be true for the score to mean anything.

  • Interest in the parent category (combined GitHub stars) stands in for demand for this capability; the proxy is discounted by 40%.
  • Keyword classification finds the products that offer this capability; products that do not name it are not counted.
  • Monetisation and feasibility are not assessed beyond a fixed rule of thumb.
  • A platform that documents MCP support can run any MCP server; no pairing has been tested.

How to verify this yourself

  1. No direct demand query exists for this capability; the demand figure comes from the parent category's GitHub stars.
  2. Check the supply on the Model Routing page, and search the catalogue for products that offer it without naming it.
  3. Download the record with all evidence: /api/dataset/opportunities.json.

All opportunities · Methodology · Report an error

Page data last updated .