Trust
Router One is in the request path of customer applications, so the things below need to be load-bearing: how numbers are measured, what data we hold, how we fall back when an upstream fails, and what the contractual terms are. Each card links to the canonical page for that topic.
Last updated:
Facts & methodology
Facts
Stable product facts for search engines, AI answer engines, and due diligence.
Open →Methodology
Index of how latency, pricing, retention, and availability numbers across the site are measured.
Open →Verify the served model
A reproducible checklist for testing any LLM API — Router One included — for model swapping and exit-scam red flags.
Open →Product boundaries
What Router One is and is not — a unified LLM API gateway, nothing more.
Open →Data & security
Availability & performance
Availability & SLA
Uptime measurement, same-model failover, and an SLA with service credits under annual enterprise agreements only.
Open →Status
Public incident state, covered components, and rolling 90-day status history.
Open →Smart routing
Exact-model routing, model="auto" tiers, failover triggers, what shows up in your trace.
Open →China latency benchmark
p50 and timeout rate across Beijing, Shanghai, Shenzhen, with the measurement date posted.
Open →Pricing, billing & terms
Pricing methodology
No hidden markup on the pay-as-you-go token line. Wallet billing and subscription plans are live. RMB conversion and channel fees are shown at checkout.
Open →Stablecoin payment option
USDT/USDC on Tron, BSC, Ethereum, Polygon, Base, Arbitrum for stablecoin treasury workflows.
Open →Terms of service
Service description, account responsibilities, acceptable use, payment, disclaimers.
Open →Refund policy
Purchased credits are non-refundable once credited, except for billing errors or where required by law; bonus credits and channel fees are not refundable.
Open →Still have questions?
Email support@router.one or reach out via our contact page. Enterprise contracts can extend or adjust any of the items above under NDA.