Legal

API and MCP server terms

The rules for using the catalogue API, the account API and the MCP servers, for customers, developers and the agents they authorize.

  • 5 min read
  • Last updated November 18, 2026

These terms govern the use of Ex2’s catalogue API, account API and MCP servers. They supplement the general terms of service and the acceptable use policy.

A1 - Purpose and acceptance

A1.1 - These terms govern the use of the public catalogue API, the account API, Ex2’s MCP servers and the documents that describe them (together, “the API”).

A1.2 - Using the API, creating a token or authorizing an application means accepting these terms, which add to the general terms of service and to the acceptable use policy.

A1.3 - The API is provided free of charge. Orders, renewals and plan changes made through the API are billed at the site’s rates.

A2 - Access

A2.1 - Catalogue. The catalogue API and its MCP server are public, read-only and need no account. The plans and prices they give are those of the site at the time of the answer.

A2.2 - Account. The account API and its MCP server answer only an application the CUSTOMER authorized by signing in at Ex2, or a personal token the CUSTOMER created in their account.

A2.3 - Ex2 grants the CUSTOMER, and the developer of the application they authorize, a personal, non-exclusive and revocable right to use the API, to manage the CUSTOMER’s services at Ex2 and for nothing else.

A3 - Permissions, tokens and security

A3.1 - The CUSTOMER chooses what to allow, area by area: billing, domain names, DNS, email, sites, WordPress, backups, export, SSH keys, tickets, unblocking an IP address. Nothing beyond reading is allowed by default.

A3.2 - The CUSTOMER may limit a permission to a single service or a single domain name, and withdraw it at any time from the page of their connections. Withdrawal takes effect immediately.

A3.3 - A token is worth the CUSTOMER’s signature. The CUSTOMER keeps it secret, publishes it neither in a code repository nor on a page, and revokes it as soon as they suspect it is compromised.

A3.4 - Ex2 never discloses through the API an account password, the content of a ticket or the transfer code of a domain name. That code is sent to the registrant’s email address.

A4 - Applications and artificial intelligence agents

A4.1 - What an application or an agent does with the CUSTOMER’s authorization is done by the CUSTOMER and binds them: orders, cancellations, DNS changes, deletions.

A4.2 - The CUSTOMER chooses their applications and agents and answers for them. Ex2 does not control their instructions, does not recommend them and is not liable for their mistakes.

A4.3 - An order made through the API accepts the general terms in the version the call names. The application sends it only after the CUSTOMER has agreed.

A4.4 - An order, a renewal or a plan change creates an invoice the CUSTOMER pays themselves. If the CUSTOMER has set a monthly spending limit for a connection, that connection may pay an invoice within the limit, never beyond it.

A4.5 - Operations that buy, cancel or release a domain name carry an idempotency key: the same key produces the operation only once. Operations carried out cannot be undone through the API.

A5 - Forbidden uses

A5.1 - The API may not be used to: access a third party’s account without their authorization; get around limits, permissions or checks; look for vulnerabilities without Ex2’s written agreement; reserve domain names in bulk or probe their availability for speculation; overload the service.

A5.2 - An application may not be presented as Ex2’s own, or as approved by Ex2, without its written agreement.

A5.3 - The developer of an application uses the account data received through the API only to give the CUSTOMER the service they asked for. The developer does not sell it, does not keep it longer than necessary and deletes it at the CUSTOMER’s request.

A6 - Usage limits

A6.1 - The account API accepts 120 requests per minute and per connection. The domain availability search is limited per IP address. The limits in force are those of the Developers page.

A6.2 - Beyond them, the API answers with an error and the application waits before trying again. Ex2 may adjust the limits to protect the service.

A7 - Log and data

A7.1 - Every call to the account API is written to a log the CUSTOMER can read: the date, the connection, the operation and the identifier of the object concerned, never the values sent. Ex2 keeps this log for 180 days.

A7.2 - This log is evidence of what a connection asked for, unless proven otherwise.

A7.3 - Ex2 counts the calls to the public API per day, without personal data. The privacy policy applies to the rest.

A8 - Availability and changes

A8.1 - The API is provided as is. The availability guarantee of Article 19 of the general terms does not apply to it.

A8.2 - Within a version, Ex2 adds fields, operations and tools without renaming or removing any. The application must ignore the fields it does not know.

A8.3 - Ex2 announces the withdrawal of a version or an operation at least 90 days ahead on the Developers page, except in a security emergency or under a legal obligation.

A8.4 - Some operations are open on part of the servers or extensions only. The API says so in its answer.

A9 - Suspension

A9.1 - Ex2 may suspend without notice a connection, a token or an application that breaches these terms, threatens the security of the service or of an account, or repeatedly exceeds the limits. Ex2 informs the CUSTOMER.

A9.2 - Suspending the API does not affect the CUSTOMER’s hosted services, which they keep managing from the client area.

A10 - Ownership and liability

A10.1 - The API, its documentation and Ex2’s trademarks remain Ex2’s property. The CUSTOMER’s data remains theirs.

A10.2 - Ex2 is not liable for damage caused by an application or an agent the CUSTOMER authorized, by a disclosed token, or by an operation that matches what an authorized connection asked for.

A10.3 - For the rest, the limitation of liability of Article 7 of the general terms applies to the API.

A11 - Common provisions

A11.1 - Changes to these terms, the governing law, disputes and the final provisions are those of Articles 20 to 22 of the general terms of service.

Back to top ↑

Do you have any question?

Contact our support