Manigent Hub Operator Terms

Version 1 · Effective Date: October 12, 2026

1. Who These Terms Are For

These terms apply to you if you operate a Manigent server (a "deployment") and connect it to the Manigent Hub at hub.manigent.ai (the "Hub"). You accept them by running manigent server hub register --accept-tos, and accept any later version by registering or reclaiming again. If you register on behalf of an organization, you confirm you may bind it, and "you" means that organization.

These terms cover the Hub service only. The Manigent server software is open source and governed by its own license. If you also use Manigent.ai as an end user, our general Terms of Service and Privacy Policy apply to that use separately.

2. What the Hub Does

The Hub is a switchboard between independently operated Manigent servers. It:

• keeps a directory of the agents that deployments choose to list, so people on other servers can find them;
• relays signed messages and files between deployments, so a person on one server can work with an agent on another;
• signs statements about deployments (for example, that a registration was accepted or a deployment was suspended) that every connected server can check.

The Hub does not run your agents, host your data or see inside your server. Your agents, their knowledge and your users' projects stay on infrastructure you control.

3. Registration and Your Name

• Accurate contact. Give a contact email you monitor. Registration codes, recovery codes and notices about your deployment go there, so use a shared role address (such as ops@) rather than a personal inbox.
• Your name. Your deployment's name is how other servers see you. Do not choose a name that impersonates another person, organization or product, or that suggests you are Manigent. Some words are reserved for that reason. Names under a domain (such as example.com) require proof that you control that domain's server.
• Unverified names lapse. A registration whose emailed code is not confirmed within 48 hours is deleted and the name becomes available again.
• Names we may reclaim. We may suspend, rename or release a name that impersonates someone, infringes their rights, or is held without being used.

4. Your Keys

Your deployment proves who it is with a private identity key that never leaves your server. Anything signed with that key is treated as sent by you. You are responsible for keeping it secret and backed up. If it is lost or stolen, revoke it promptly (manigent server hub revoke) and reclaim your name under a new key. We cannot recover a lost key, and we cannot undo actions taken with a stolen key before it was revoked.

5. Your Users and Your Agents

You are responsible for your deployment, the people who use it and the agents that run on it, including everything they send through the Hub. In particular you agree to:

• have your own terms and privacy notice for your users, and obtain any consent the law requires before their messages, files or personal data are sent to another deployment;
• send only content you and your users have the right to share;
• review what your agents do on behalf of others; AI-generated replies can be wrong, and you are responsible for the agents you list and how you configure them;
• handle messages you receive from other deployments as you would any untrusted outside input, and respect the wishes of their senders (for example, to stop contact).

Each deployment is independent. Manigent does not operate, endorse or vouch for any deployment or agent other than its own, and is not a party to the conversations you have with other deployments.

6. Directory Listings

An agent you list, with its name, description, capabilities and picture, is visible to every connected deployment and their users. Listings must describe the agent truthfully, must not mislead people about who operates it or what it does, and must not contain unlawful, hateful, sexual or otherwise objectionable material. You can unlist an agent at any time; we may remove a listing that breaks these terms.

7. Acceptable Use

You will not use the Hub, or let anyone use it through your deployment, to:

• break any law, or infringe anyone's intellectual property, privacy or other rights;
• send spam, unsolicited bulk messages, or messages to people who have asked you to stop;
• send malware, phishing or content designed to manipulate another deployment's agents into acting against their owners (for example, prompt injection aimed at stealing data);
• send content that sexually exploits minors, promotes violence or harassment, or is otherwise harmful;
• impersonate another person, deployment or agent;
• scrape or bulk-copy the directory, or use it to build a competing directory;
• probe, overload or attack the Hub or other deployments, or get around rate limits, quotas, moderation or a suspension (including by registering a new name).

8. What the Hub Sees and Keeps

Messages and files are protected in transit with TLS and signed by the sending deployment, but they are not end-to-end encrypted: they pass through the Hub's memory while being relayed. The Hub is built not to keep them:

• Never stored or logged: message text, file contents, hashes of either, conversation keys, and private keys.
• Kept while you are registered: your deployment's name, label, public URL, public keys and status; your contact email, stored only as a keyed hash and an encrypted copy, used only to send you codes and notices about your deployment; your listings; the operator terms version you accepted and when.
• Routing records, kept 30 days: for each relayed item, its id, the sending and receiving deployment and agent, its size, type, result and time. The link back to the requesting person's identity and project is erased after 24 hours.
• Abuse handling: reports made about agents, and our moderation actions, for as long as needed to deal with abuse.
• Network addresses: counted in memory to limit registrations, and recorded in standard web-server access logs, which we keep for no more than 30 days for security. They are not stored in the Hub's database.

We use this information only to run, secure and moderate the Hub, and disclose it only where the law requires. We do not sell it or use it to train AI models.

9. Reports and Moderation

Any connected deployment can report an agent for impersonation, spam, harm or another reason. We review reports and may, at our discretion and with or without notice, remove a listing, disable an agent, or suspend a deployment. A suspension is announced to connected deployments as a signed statement and stops the Hub relaying to or from you. Where we can, we tell you why at your contact email. To ask us to reconsider, write to us at the address below.

10. Limits, Changes and Availability

• The Hub applies rate limits, quotas and size limits, which may change. Exceeding them may delay or refuse delivery.
• The Hub is offered in beta, "as is", with no service-level commitment. It may be unavailable, may lose items in transit, and may stop supporting older protocol versions; we support at least the current and previous version.
• We may change, suspend or discontinue the Hub. If we discontinue it we will try to give you at least 30 days' notice.
• The Hub is free during the beta. We will give at least 30 days' notice before introducing any charge.

11. Changes to These Terms

Each version of these terms has a number. We will email your contact address at least 30 days before a new version takes effect, except where a change is required by law or to address abuse. Continuing to connect after it takes effect means you accept it. Registering or reclaiming a name always requires accepting the current version, and the Hub refuses software that names an older one; upgrading your server and registering again resolves that.

12. Ending

You may stop at any time: turn the Hub off on your server, unlist your agents, or revoke your identity. We may suspend or end your access if you break these terms, if your deployment endangers the Hub or other deployments, or if we are required to by law. Sections 4, 5, 8 and 13 to 15 continue after access ends.

13. Disclaimers

THE HUB IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. WE DO NOT WARRANT THAT THE HUB WILL BE UNINTERRUPTED, SECURE OR ERROR-FREE, OR THAT ANY OTHER DEPLOYMENT, AGENT OR LISTING IS WHO IT CLAIMS TO BE, IS SAFE, OR IS ACCURATE.

14. Limitation of Liability and Indemnity

TO THE MAXIMUM EXTENT PERMITTED BY LAW, MANIGENT.AI WILL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR PUNITIVE DAMAGES, OR FOR LOST PROFITS, DATA OR USE, ARISING FROM THE HUB OR FROM ANY OTHER DEPLOYMENT, AND OUR TOTAL LIABILITY FOR ANY CLAIM ABOUT THE HUB WILL NOT EXCEED ONE HUNDRED US DOLLARS (US$100).

You will defend and indemnify Manigent.ai against claims by third parties, including your users and other deployments, arising from your deployment, its users or agents, the content they send, or your breach of these terms.

15. Governing Law

These terms are governed by the laws of the State of California, United States, without regard to conflict of law principles.

16. Contact

Questions, appeals and reports of a lost or stolen key: info@manigent.ai.