# Capacity Routing API

*/Opportunities/Capacity_Routing_API*

## Opportunity Overview

**Wedge**: Target high-throughput consumer AI tools where margin pressure and token limits are severe, requiring constant model switching to remain profitable. Win this segment first to generate the request volume necessary to map real-time network conditions. Expand into enterprise B2B SaaS by introducing compliance-based routing, directing localized user requests exclusively to region-specific host endpoints.
**Timing**: The proliferation of comparable foundation models creates a viable multi-provider environment, while frequent provider-side rate-limiting makes dynamic fallback mandatory for production uptime. Applications now require millisecond-level model switching to maintain core functionality.
**Why This I C P**: High-volume AI software developers face immediate financial penalties and user churn from upstream LLM latency or outages, compelling them to buy a routing solution rather than build complex load-balancing infrastructure in-house.
**Size Of Prize**: ~40,000 commercial AI deployment teams × ~$12,000 annual spend on API middleware and gateway tooling = ~$480M addressable prize.
**Gap Narrative**: AI application developers face frequent rate limits, varied latencies, and regional outages across LLM and compute providers. They require a unified routing layer that directs requests to the optimal endpoint based on real-time availability and cost. Current implementations rely on brittle, hard-coded fallback logic that fails during widespread provider degradation.
**Defensibility**: Defensibility compounds through global latency and outage telemetry. Every routed request updates the shared map of provider health, making the routing engine strictly faster and more reliable than any individual application's internal fallback logic. Once embedded as the primary LLM gateway, the API achieves workflow lock-in via high infrastructure switching costs.
**Why This Thesis**: An API approach fits the infrastructure-layer problem directly, operating synchronously within the developer's existing request pipeline to execute millisecond-level load balancing without human intervention.

## Opportunity Linked Thesis

**Thesis**: [Software](/Theses/Software)

## Opportunity Linked I C P

**Icp**: [Logistics Provider](/CompanyTypes/Logistics_Provider)

## Opportunity Market Sizing

_Illustrative — target and order-of-magnitude estimate figures, not an achieved track record (this Thing is concept-stage)._

**S A M**: ~$600-900M North American mid-market 3PLs and freight brokerages
**S O M**: ~$15-35M
**T A M**: ~50k global mid-market to enterprise logistics providers x ~$40k-60k/yr API routing spend = ~$2-3B
**Growth Rate**: ~12-18%/yr, driven by tightening freight margins and the transition from manual dispatching to automated digital freight matching
**Paid Comparable Spend**: ~$60k-120k/yr per firm on manual dispatcher labor, legacy TMS routing add-ons, and fragmented load board data feeds

## Opportunity Incumbents

- [Twilio TaskRouter](/Products/Twilio_TaskRouter) — Tool
- [AWS API Gateway](/Products/AWS_API_Gateway) — Tool
- [Kong API Gateway](/Products/Kong_API_Gateway) — Tool
- [HAProxy](/Products/HAProxy) — Open-Source
- [Envoy Proxy](/Products/Envoy_Proxy) — Open-Source
- [Custom Load Balancer](/Products/Custom_Load_Balancer) — DIY
- [In-House Routing Service](/Products/In-House_Routing_Service) — DIY

## Opportunity Win Conditions

**Kill Thresholds**:
- Median API integration time exceeds 45 days
- Dispatcher manual override rate remains above 60 percent at Day 30
- Day 60 account retention falls below 60 percent
- Customer acquisition cost exceeds $8,000 during the first 90 days
**Leading Metrics**:
- Time-to-first-production-API-call in days
- Percentage of total daily spot loads routed automatically
- Dispatcher manual override rate per load
- Carrier acceptance rate on API-tendered loads
- API latency per routing request in milliseconds
**What Proves Right**: Freight brokerages deploy the API into their existing transportation management systems within 14 days and route over 40 percent of their daily spot freight through the automated endpoints. Customers sustain a $4,000 per month access fee and expand their API usage volume month-over-month instead of reverting to manual dispatch teams. Dispatchers accept the API carrier matches directly, yielding an override rate below 15 percent on automated tenders.
**What Proves Wrong**: Legacy transportation management systems require more than 30 days of custom engineering to consume the endpoints, stalling initial deployments. Dispatchers override the API carrier selections more than 50 percent of the time because they do not trust the algorithmic matches or find better rates via manual phone calls. Brokerages cancel their contracts before day 60 because the API fails to secure freight capacity faster than their existing manual load board workflows.

## Opportunity Build Profile

**Hardest Part**: Maintaining sub-second latency while querying fragmented, constantly changing third-party capacity databases and running complex geospatial routing algorithms. If the API times out or returns stale capacity, the transaction fails entirely.
**Min Viable Scope**: An API that handles single-node, point-to-point capacity matching for one specific asset class in one geographic region. Leave out multi-stop routing, live tracking, and automated payments to focus strictly on returning the cheapest available capacity ID.
**Cold Start Problem**: The API has zero value without a critical mass of pre-integrated capacity providers on the supply side. Break this by hard-integrating 3-5 massive regional fleets first and selling exclusively to demand sources that match those specific geographies.
**Time To First Value**: 1-2 sprints of developer integration gated by the customer mapping their internal demand payload to the API schema
**Data Moat Available**: true
**Technical Difficulty**: High

## Neighborhood

### Where the gap lives

- [Culinary Staff](/Occupations/Culinary_Staff) — latent gap · Occupations
- [Payload Operations](/Departments/Payload_Operations) — latent gap · Departments
- [Firm Managing Partner](/JobTypes/Firm_Managing_Partner) — latent gap · JobTypes

### Incumbent in

- [Kong Gateway](/Products/Kong_Gateway) — incumbent in · Products
- [AWS API Gateway](/Products/AWS_API_Gateway) — incumbent in · Products
- [Custom Load Balancer](/Products/Custom_Load_Balancer) — incumbent in · Products
- [Envoy Proxy](/Products/Envoy_Proxy) — incumbent in · Products
- [HAProxy](/Products/HAProxy) — incumbent in · Products
- [In-House Routing Service](/Products/In-House_Routing_Service) — incumbent in · Products
- [Twilio TaskRouter](/Products/Twilio_TaskRouter) — incumbent in · Products

### Applies thesis

- [Logistics Provider](/CompanyTypes/Logistics_Provider) — applies thesis · CompanyTypes

### Embodies

- [Software](/Theses/Software) — embodies · Theses

### Similar Opportunities

- [Distributed Load Router](/Opportunities/Distributed_Load_Router) — similar · Opportunities
- [Dynamic LLM Routing for AI Startups](/Opportunities/Dynamic_LLM_Routing_for_AI_Startups) — similar · Opportunities
- [Provider Abstraction Gateway](/Opportunities/Provider_Abstraction_Gateway) — similar · Opportunities
- [Outage Mitigation Gateway](/Opportunities/Outage_Mitigation_Gateway) — similar · Opportunities
- [AI for AI for Software Publishers as a Service API](/Opportunities/AI_for_AI_for_Software_Publishers_as_a_Service_API) — similar · Opportunities
- [Compute Arbitrage Engine](/Opportunities/Compute_Arbitrage_Engine) — similar · Opportunities
- [Context Cache](/Opportunities/Context_Cache) — similar · Opportunities
- [Fleet Dispatch API](/Opportunities/Fleet_Dispatch_API) — similar · Opportunities
- [Browser Compute Router](/Opportunities/Browser_Compute_Router) — similar · Opportunities
- [Escalation Routing API](/Opportunities/Escalation_Routing_API) — similar · Opportunities
- [AI Pattern Programming](/Opportunities/AI_Pattern_Programming) — similar · Opportunities
- [Dynamic Routing for Pallet Networks](/Opportunities/Dynamic_Routing_for_Pallet_Networks) — similar · Opportunities
- [Token Compression Proxy](/Opportunities/Token_Compression_Proxy) — similar · Opportunities
- [Proactive SLA Manager](/Opportunities/Proactive_SLA_Manager) — similar · Opportunities
- [Outage Mitigation Gateway](/Skills/Systems_Evaluation/Opportunities/Outage_Mitigation_Gateway) — similar · Opportunities
- [Predictive Load Balancer](/Opportunities/Predictive_Load_Balancer) — similar · Opportunities
- [Dynamic Route Optimization](/Opportunities/Dynamic_Route_Optimization) — similar · Opportunities
- [Request Routing Fabric](/Opportunities/Request_Routing_Fabric) — similar · Opportunities
- [Generative Compound API](/Opportunities/Generative_Compound_API) — similar · Opportunities
- [Wholesale Route Arbitrage](/CompanyTypes/Reseller_CLECs/Opportunities/Wholesale_Route_Arbitrage) — similar · Opportunities