router.taxi
PrivacyAccount

Effective August 3, 2026

Terms of Service

These Terms of Service (“Terms”) are a binding agreement between you and Belweave for your use of router.taxi (“Router”), including its website, PWA, accounts, messaging agent, native clients, REST API, MCP server, provider handoffs, private Android vaults, and commerce features.

Please read before using Router. Router is an independent technology interface, not a ride provider, transportation carrier, dispatcher, emergency service, bank, or payment network. Live prices and automated actions depend on third parties and may be delayed, incomplete, changed, or unavailable. A ride is not booked unless the ride provider itself confirms it.

1. Acceptance and eligibility

By accessing or using Router, you agree to these Terms and the Privacy Policy. If you do not agree, do not use Router. You must be at least 18, have legal capacity to agree, and meet the age, account, payment, and eligibility rules of every provider you use. If you use Router for an organization, you represent that you may bind it. Additional written terms may apply to paid, enterprise, pilot, or production-commerce access.

Router is currently an invite-only beta. You may submit an email address or create or authenticate a Clerk identity to request access, but authentication is not approval. We may manually review, approve, deny, defer, limit, or revoke access based on capacity, safety, reliability, abuse prevention, legal requirements, or product fit. Submission does not guarantee admission or a response by a particular time.

2. What Router does

Router may provide route planning, coverage discovery, estimated and connected live quotes, ranked transportation options, provider deep links, messaging workflows, agent tools, provider-account connections, remote-device execution, purchase approvals, checkout attempts, and status evidence. Features and providers vary by route, account, device, client, and availability.

A result labeled “estimate,” “planning estimate,” or similar is a model, not a provider offer. A result labeled “live” reflects data captured from a provider at a stated or recent time but may change immediately. Pickup times, trip times, coverage, vehicle types, accessibility, promotions, taxes, tolls, fees, surge, and final price are controlled by the provider. Rankings are informational and may reflect price, time, availability, preferences, or incomplete data.

3. Third-party transportation services

Ride, taxi, autonomous-vehicle, delivery, transit, and other providers are independent third parties. Their terms, privacy notices, safety standards, eligibility rules, cancellation policies, insurance, dispute processes, and charges govern your transaction with them. Displaying a provider, mark, estimate, deep link, or connected quote does not imply affiliation, sponsorship, endorsement, availability, or that Router acts as that provider's agent.

You are responsible for checking the provider's final pickup and destination, ride product, rider count, accessibility, safety details, price, payment method, and terms before confirming. Contact the ride provider for vehicle, driver, lost-item, cancellation, refund, safety, and transportation disputes. Do not use Router for an emergency. Call 911 or the appropriate emergency service.

4. Accounts and authorized agents

You are responsible for accurate account information and all activity under your account, sessions, linked phone number, devices, and API keys. Protect credentials, use unique device security, grant only the scopes needed, and promptly revoke suspected exposure. A bearer API key, linked Messages conversation, enrolled device token, or active Clerk session is treated as your authorization within its permissions unless we have received and processed notice that it is compromised.

If you authorize an AI agent, application, employee, family member, or other person to use Router, you are responsible for defining and monitoring that authority. Router may rely on a clear instruction delivered through an authenticated surface, including an instruction to compare, approve a ceiling, hand off, or attempt checkout. You must review automated outputs and maintain human oversight appropriate to the financial, location, and safety consequences.

5. Provider connections and private Android vaults

Provider connections may use tokens, provider-hosted sign-in, a native client, or an isolated remote Android environment. You authorize Router to store and refresh connection state and, when you request it, to start, stop, restore, stream, and automate the assigned environment to retrieve quotes or attempt a supported action. You may connect only an account you own or are expressly authorized to use.

Private Android vaults are a developing feature. Boot, restore, streaming, Google Play services, provider app behavior, anti-abuse controls, remote input, and snapshots may fail or take time. Stopping compute ordinarily preserves state; deleting, unlinking, or losing a vault may require sign-in again. Do not use a vault to bypass provider safeguards, geographic restrictions, or terms. We may suspend, recycle, or delete a vault for security, capacity, inactivity, legal, or provider-compliance reasons, with notice where reasonably feasible.

6. Quotes, handoffs, and booking status

A deep link or “Open” action only transfers route information to a provider. It does not prove that a booking occurred. A purchase approval, payment token, checkout attempt, screenshot, or Router receipt also does not by itself prove a booking. Router reports a ride as booked only when it receives or observes a provider confirmation. Provider systems may return ambiguous, delayed, or inconsistent results; when uncertain, verify directly in the provider app before retrying so you do not create duplicate rides.

Router may reserve a reasonable authorization buffer above a displayed quote so a small fare refresh does not interrupt checkout. The approval screen or agent message should disclose the maximum ceiling. The provider may still present a different final amount, and you should decline or cancel if it is unacceptable.

7. Payments and Prava

Supported commerce uses Prava or another disclosed payment service to create a purchase-specific approval and one-time credential. You authorize Router to transmit that credential to the selected merchant only for the approved purchase and ceiling. Router is designed not to fall back to a pre-existing provider payment method during a labeled one-time-credential flow. You must not proceed if the approval details are wrong.

Sandbox transactions are tests. Sandbox cards may be intentionally declined, have no real funds, and must not be used for an actual ride. A simulated fleet quote does not dispatch a vehicle. Production payment access, where enabled and clearly labeled, can create real financial and transportation consequences. You remain responsible for the provider's actual charge, cancellation fees, tips, tolls, adjustments, refunds, taxes, and disputes. Payment authorization can expire or fail, and neither Router nor Belweave is a bank or issuer.

8. Messaging, OpenAI, API, and MCP

Carrier and messaging fees may apply. Messages can be delayed, reordered, duplicated, misdelivered, or visible on shared devices. Natural-language interpretation may use OpenAI and can be wrong; Router's deterministic checks reduce but do not eliminate that risk. Confirm ambiguous addresses and prices before authorizing action.

Router may use an AI classifier to identify a limited recovery state on an eligible, stalled provider quote screen. AI does not authorize a purchase, solve a provider verification challenge, or control arbitrary device input. Router's allowlisted automation and the provider's own confirmation remain authoritative.

Developer interfaces may change, be rate-limited, or return partial data. Do not expose keys in client code, public repositories, prompts, logs, or chat messages. You may cache results only as permitted by applicable law, these Terms, provider terms, and response metadata. You may not misrepresent an estimate as live, a handoff as booked, or a Router result as provider-verified when it is not.

9. Acceptable use

You may not use Router to:

  • violate law, these Terms, or an applicable provider agreement;
  • access another person's account, location, messages, device, or payment authority without permission;
  • create fraudulent, abusive, unsafe, duplicate, or unwanted bookings;
  • bypass security, provider safeguards, rate limits, access controls, or payment restrictions;
  • probe, scrape, reverse engineer, interfere with, overload, or introduce malicious code into Router or connected systems, except where law expressly permits security research;
  • resell or commercially exploit Router, its data, or its interfaces without written permission; or
  • use Router to discriminate, stalk, harass, surveil, or endanger anyone.

We may investigate, rate-limit, block, revoke, preserve evidence, or report conduct when reasonably necessary to protect the service, users, third parties, or law.

10. Intellectual property

Router, its software, design, text, selection and arrangement of data, documentation, models, APIs, workflows, and branding are owned by Belweave or its licensors and are protected by intellectual-property and unfair-competition laws. Subject to these Terms, we grant you a limited, personal, revocable, non-exclusive, non-transferable license to use the service for its intended purpose. No other rights are granted. “router.taxi,” Belweave marks, and associated trade dress may not be used without written permission.

Third-party names and marks belong to their owners. Feedback you voluntarily provide may be used by us without restriction or payment, but this does not transfer ownership of your pre-existing material or personal information.

11. Privacy

Our Privacy Policyexplains how Router handles information and where third-party processing occurs. You are responsible for giving any notice and obtaining any consent required before submitting another person's information or using Router on their behalf.

12. Availability, changes, and beta features

Router may add, remove, suspend, limit, or change features, providers, models, integrations, prices, quotas, or requirements at any time. Experimental, beta, sandbox, and pilot features may be incomplete and are offered for evaluation. We do not promise uninterrupted access, any particular provider or route, preservation of remote-device state, backward compatibility, or a service-level commitment unless a separate signed agreement says otherwise.

13. Disclaimers

TO THE MAXIMUM EXTENT PERMITTED BY LAW, ROUTER IS PROVIDED “AS IS” AND “AS AVAILABLE.” BELWEAVE AND ITS AFFILIATES, LICENSORS, AND SERVICE PROVIDERS DISCLAIM ALL EXPRESS, IMPLIED, AND STATUTORY WARRANTIES, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, ACCURACY, AVAILABILITY, SECURITY, AND QUIET ENJOYMENT. WE DO NOT WARRANT THAT ROUTER, A QUOTE, ROUTE, PROVIDER, VEHICLE, REMOTE DEVICE, MESSAGE, PAYMENT, OR BOOKING WILL BE AVAILABLE, ACCURATE, SAFE, TIMELY, UNINTERRUPTED, OR ERROR-FREE.

Some jurisdictions do not allow certain disclaimers, so some of the above may not apply to you. Nothing in these Terms waives a right that cannot legally be waived.

14. Limitation of liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW, BELWEAVE, ROUTER, AND THEIR AFFILIATES, PERSONNEL, LICENSORS, AND SERVICE PROVIDERS WILL NOT BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES; LOST PROFITS, DATA, GOODWILL, OR OPPORTUNITY; OR DAMAGES ARISING FROM TRANSPORTATION, PERSONAL INJURY, A THIRD PARTY, AN INCORRECT ROUTE OR PRICE, A MISSED OR DUPLICATE RIDE, ACCOUNT ACCESS, DEVICE STATE, OR AN UNAUTHORIZED OR FAILED TRANSACTION, EVEN IF ADVISED OF THE POSSIBILITY. THEIR TOTAL LIABILITY FOR ALL CLAIMS RELATING TO ROUTER WILL NOT EXCEED THE GREATER OF $100 OR THE AMOUNT YOU PAID DIRECTLY TO BELWEAVE FOR ROUTER DURING THE 12 MONTHS BEFORE THE EVENT.

These limits apply to the fullest extent permitted and do not exclude liability that applicable law does not allow us to exclude.

15. Indemnity

To the extent permitted by law, you will defend, indemnify, and hold harmless Belweave, Router, and their affiliates and personnel from third-party claims, damages, losses, and reasonable fees arising from your misuse of Router, violation of these Terms or law, infringement of rights, unauthorized account or payment activity, or data you submit. This obligation does not apply to the extent a claim resulted from our own unlawful conduct.

16. Suspension and termination

You may stop using Router at any time. We may suspend or terminate access, keys, messaging links, or provider vaults if we reasonably believe there is abuse, risk, nonpayment, inactivity, a legal or provider requirement, or a material breach. Provisions that by their nature should survive do survive, including ownership, disclaimers, liability limits, indemnity, disputes, and accrued obligations.

17. Governing law and disputes

Unless applicable consumer law requires otherwise, these Terms are governed by the laws of the Commonwealth of Virginia, without regard to conflict-of-law rules. You and Belweave consent to the exclusive jurisdiction of the state and federal courts serving Loudoun County, Virginia. Before filing a claim, please contact us and allow 30 days for an informal resolution. Either party may seek urgent equitable relief for security or intellectual-property harm.

18. General terms

These Terms and incorporated policies are the entire agreement about Router unless a signed agreement says otherwise. If a provision is unenforceable, it will be limited to the minimum extent necessary and the rest will remain effective. Our failure to enforce a provision is not a waiver. You may not assign these Terms without our consent; we may assign them in connection with a reorganization, financing, sale, or transfer of Router. Electronic notices and records satisfy writing requirements where law permits.

19. Changes and contact

We may update these Terms as Router changes. We will post the revised version and effective date and provide additional notice when required. Continued use after the effective date constitutes acceptance to the extent permitted by law. Questions can be sent to support@router.taxi.