Terms of service
Effective 2026-06-02 · Revision 1 (draft)
Scope
These terms govern your use of the Xanadu hosted dispatcher endpoint at xanadu.run/mcp, the marketing pages at xanadu.run/*, and any API endpoints we serve under that domain. The open-source dispatcher (the Python package and the Docker image) is governed by the LICENSE file in the source repository (MIT).
Use of the hosted dispatcher
You agree to dispatch only against agents and tasks that are lawful in your jurisdiction. You agree not to attempt to bypass per-tenant budget caps, identifier collisions, or rate limits. We reserve the right to terminate sessions or tenants that violate the acceptable use policy at /legal/aup.
Billing
Hosted dispatcher tenants are billed via Stripe at month-end against the structured ledger. Disputed charges should be reported within 30 days to billing@xanadu.run. The underlying ledger is append-only and customer-readable through the ledger_summary MCP tool; that ledger is the source of truth for invoicing.
Service level
We provide reasonable-effort availability for the hosted endpoint. Status is published live at /status. We do not commit a contractual SLA on the public beta; design-partner contracts contain enforceable terms in the master services agreement.
Termination
You may terminate use at any time by removing the dispatcher from your .mcp.json. We may terminate access for non-payment, AUP violation, or law-enforcement order (subject to the security and threat-model pages’ constraints on what is possible).
Disputes
Governing law: Switzerland for the operating Stiftung. Dispute venue: Zürich. The master services agreement for design partners supersedes this paragraph.
Changes
We will note changes to this page with a revision number and a diff-style summary at the top. Material changes will be emailed to known billing contacts.
This page is a draft. The binding contract for design partners is the executed master services agreement. For questions email hello@xanadu.run.