Comparison

BitRouter is the only smart router and open marketplace built specifically for agents — open (Apache 2.0, locally deployable, permissionless registration and usage), intelligent (multi-provider routing, programmable fallbacks, runtime guardrails, sub-10ms overhead), and agent-native (KYA identity, autonomous x402/MPP payments, MCP/ACP gateway, reliability primitives for long-running loops).

Most existing tools fall into one of three categories. None covers all three properties at once.

vs Cloud SaaS routers (OpenRouter and similar)

Cloud SaaS routers — like OpenRouter — route requests across hundreds of models behind a hosted endpoint, optimized for human-facing apps.

• Self-hostable — Cloud SaaS routers are closed-source and cloud-only. BitRouter is Apache 2.0; run it anywhere as a single binary.
• Permissionless access — These services require account creation and credit card or crypto top-up. BitRouter's hosted option uses x402/Solana — no KYC, no geo-restrictions, agents pay per request.
• Agent-first features — Cloud SaaS routers have no agent firewall, no MCP/ACP gateway, and no skills registry. BitRouter is built around them.
• Lower latency — Sub-10ms routing overhead vs ~25–40ms typical for hosted routers.

vs Self-hosted proxies (LiteLLM and similar)

Self-hosted proxies — like LiteLLM — are open-source SDKs and Python proxies popular for backend services. They're BYOK and infra-heavy.

• Zero-ops — These proxies typically require Postgres, Redis, and Docker/K8s in production. BitRouter is one binary, no dependencies.
• Performance — Python-based proxies hit the GIL at scale; tail latency degrades under concurrent load. BitRouter's Rust async runtime keeps latency flat.
• Payments — Self-hosted proxies are BYOK only and have no payment handling. BitRouter's hosted option supports autonomous agent payments.
• Agent runtime — These proxies have no in-line content safety, no KYA identity, no skills registry. BitRouter does.

vs Generic API gateways (Portkey, Kong AI, AWS Bedrock Gateway, etc.)

Generic API gateways treat LLMs as just another upstream API. They typically offer logging, caching, rate limiting, provider failover, BYOK billing, and dashboards.

They don't offer:

• Agent identity or runtime model discovery
• Autonomous payment protocols (x402/MPP)
• MCP or ACP gateway functionality
• A skills registry for agent capabilities
• Sub-10ms native binary deployment

These gateways fit traditional API operations. BitRouter exists because autonomous agents need a different surface — runtime model selection, payment delegation, in-line safety, and a single open standard for tool and sub-agent discovery.