Engine MCP AI Integration Terms

ARTICLE 1. DEFINITIONS AND RELATIONSHIP TO THE TERMS OF SERVICE

1.1Defined Terms. Capitalized terms used in these AI Integration Terms (these “Terms”) have the following meanings:

(a)“Administrator” means a User who has administrative authority over a Member account, as described in the Terms of Service.

(b)“Agent” means a third-party AI assistant or application that a User connects to the MCP Server.

(c)“Agent Action” means any request an Agent makes through the MCP Server, including searching, booking, cancelling, shortening, changing guest names, looking up bookings or support cases, and asking knowledge base questions.

(d)“Agent Platform” means the provider of an Agent, such as OpenAI or Anthropic.

(e)“Engine” means HotelEngine, Inc. d/b/a Engine.

(f)“MCP Server” means the Model Context Protocol server operated by Engine that allows Agents to access Platform functionality.

(g)“Member” means a corporate customer of Engine that holds a Member Account, as described in the Terms of Service.

(h)“Platform” means Engine’s online booking and spend management services, including the website and mobile applications.

(i)“Privacy Policy” means Engine’s Privacy Policy available at https://engine.com/privacy-policy, as amended from time to time.

(j)“Terms of Service” means Engine’s Terms of Service available at https://engine.com/terms-of-service, as amended from time to time (also referred to as the “ToS”).

(k)“User” means any person granted access to a Member Account by the Member or an Administrator, as described in the Terms of Service.

1.2Relationship to Terms of Service. These Terms are a policy referenced in the Terms of Service and supplement them. If these Terms conflict with the Terms of Service regarding the MCP Server or Agent Actions, these Terms control.

1.3Permitted Automated Access. Section XVIII of the Terms of Service prohibits automated access to the Platform without Engine’s prior written permission. Engine grants that permission for access through the MCP Server, subject to these Terms, and that prohibition does not apply to access through the MCP Server.

ARTICLE 2. ELIGIBILITY AND ENABLEMENT

2.1Eligible Accounts. The MCP Server is available only to Member Accounts. Personal Accounts and leisure travel are excluded. Government accounts are not eligible.

2.2Default Setting. Access to the MCP Server remains disabled by default across all Members. An Administrator alone retains the authority to activate or deactivate MCP Server functionality on behalf of the Member via the Platform. Such activation constitutes an administrative setting and does not independently signify assent to these Terms. Individual Users lack authorization to enable MCP Server functionality independently.

2.3Maximum Access Levels. When enabling MCP Server access, the Administrator selects the maximum access level available to Users:

(a)Read-only access, which permits Users to look up trips, bookings, and support information through an Agent; or

(b)Read-and-write access, which additionally permits Users to book, cancel, shorten, and change bookings through an Agent.

2.4User Access Level. Each User who connects an Agent selects read-only access or, where the Administrator has permitted read-and-write access, read-and-write access for that User’s connection. A User may not select a level above the maximum set by the Administrator.

2.5Engine Controls. Engine may disable, restrict, or override any Member’s MCP Server access, including the access level selected, at any time for security, fraud prevention, legal compliance, or operational reasons.

2.6Agent Platform Availability. Engine does not guarantee that any Agent Platform will make the MCP Server available or support any Agent Action, including checkout. Engine may restrict or discontinue availability on any Agent Platform at any time, without liability to the Member or any User.

ARTICLE 3. USER CONNECTION AND ACCEPTANCE

3.1Individual Connection. Each User may connect an Agent to the User’s own account only after an Administrator has enabled MCP Server access for the Member. A User may not share a connection with another person.

3.2Acceptance on Behalf of the Member. Before connecting an Agent, each User must accept these Terms by electronic click-through acceptance in the Platform. No signature is required. A User’s acceptance is the Member’s acceptance of these Terms. By accepting, the User represents that the User is authorized to bind the Member to these Terms for the purpose of connecting an Agent. Engine records each acceptance with the accepting User, the User’s role, the date and time, and the version of these Terms accepted.

3.3Multi-Factor Authentication. Multi-factor authentication is required for every User before a connection is established, regardless of role.

3.4Agent Platform Terms. Each User is responsible for complying with the terms of the Agent Platform for the Agent the User uses, and for reviewing that Agent Platform’s privacy policy before connecting.

3.5Connection Duration. Agent access tokens expire six hours after issuance and are renewed automatically through a refresh token. A refresh token expires after one year without use and, in any event, one year after the User first connects an Agent. The User must then reconnect the Agent.

ARTICLE 4. AGENT ACTIONS, AUTHORITY, AND PAYMENT

4.1Authority. The Member and each User authorize each Agent to take Agent Actions on the User’s behalf, within the User’s existing permissions on the Platform and the access level applicable to the User’s connection.

4.2Binding Actions. Bookings, cancellations, and changes made through an Agent are binding on the Member and the User, subject to the cancellation and change policies that apply to the booking.

4.3Booking Confirmation. Before a booking is charged, the Agent must obtain the User’s confirmation of the specific booking. The MCP Server will reject a booking request unless it includes a confirmation record stating the property, check-in and check-out dates, room type, total price, and cancellation policy that the User confirmed. Engine stores each booking request, including the confirmation record, with a timestamp. The User is responsible for reviewing each booking’s details before giving confirmation to the Agent. Engine may change the confirmation process at any time in accordance with Section 10.1.

4.4Agent Conduct. Each Agent Action is treated as an action of the User who authorized it. The Member and that User are responsible for each Agent Action as if the User had taken the action directly. Engine does not control any Agent and cannot verify what a User told an Agent. The Member and each User are responsible for the instructions the User gives an Agent, for all bookings made under the User’s connection, and for the Agent’s conduct on the User’s behalf.

4.5Payment Methods. Bookings made through the MCP Server are charged to a payment card saved to the User’s account. Engine will not collect payment method information through an Agent.

4.6Checkout Eligibility. At launch, checkout through the MCP Server is available only for Members that do not use custom fields, incidentals, or Flex. Other bookings are handed off to Users to complete on the Platform.

4.7Scope of Actions. Engine may add, change, or remove Agent Actions at any time. If an Agent Action cannot be completed, the Agent will direct the User to the Platform or to Engine support, and no booking will exist until checkout is completed.

4.8Chargebacks and Disputes. Chargebacks and payment disputes for bookings made through the MCP Server follow Engine’s standard payment dispute process, as set out in Section XIV of the Terms of Service, and cost allocation is as set out in that Section.

ARTICLE 5. MEMBER AND USER RESPONSIBILITIES

5.1Credentials. The Member and each User must protect the credentials used to connect an Agent. The User must immediately notify Engine of any unauthorized use of a connection, consistent with Section V.B of the Terms of Service.

5.2Oversight. The Member is responsible for the activity of its Users through an Agent, including review of bookings made under their connections.

5.3Acceptable Use. The Member and each User must not:

(a)use the MCP Server for bulk or automated booking beyond the limits Engine sets;

(b)resell or sublicense access to the MCP Server or Agent Actions;

(c)scrape, copy, or systematically extract Platform data through the MCP Server; or

(d)attempt to circumvent rate limits, authentication, or other security controls.

ARTICLE 6. DISCONNECTION AND SUSPENSION

6.1User Disconnection. A User may disconnect an Agent at any time through the Platform.

6.2Member Shutoff. An Administrator may turn off MCP Server access for the Member at any time. Turning off access ends all existing connections for the Member. Engine will block requests from Agents for the Member within approximately one minute. Engine does not guarantee immediate revocation of access tokens, and such revocation may follow.

6.3Password and Account Lock. Engine may end any or all of a User’s connections where Engine reasonably believes it is necessary for security, including after a change to the User’s password or a lock on the User’s account. Engine is not obligated to end connections automatically upon any such event.

6.4Engine Suspension. Engine may suspend or revoke any connection, User, or Member’s MCP Server access, effective on the next request, where Engine reasonably believes it is necessary for fraud prevention, security, or compliance, consistent with the Enforcement Actions provisions of the Terms of Service.

ARTICLE 7. DATA, PRIVACY, AND AGENT PLATFORMS

7.1Data Minimization. Engine will return to an Agent only the information reasonably needed to complete the requested Agent Action. Engine will not return a User’s date of birth, Known Traveler number, or passport number.

7.2Privacy Policy. Engine’s processing of personal data through the MCP Server, including acceptance records, is governed by the Privacy Policy.

7.3Agent Platforms. Information Engine returns to an Agent is provided to the Agent Platform the User chose, at the User’s direction. That Agent Platform’s privacy policy and the User’s agreement with it govern how the Agent Platform collects, retains, and uses that information. Engine has no control over those practices.

7.4Engine Logs. Engine retains connection logs, request logs, and acceptance records from which personal data has been removed, as described in the Privacy Policy, for ten (10) years. Access to these records is limited to Engine’s internal engineering and data teams. Engine does not share its server-side logs with Agent Platforms.

7.5Fraud and Security Monitoring. Engine uses information about MCP Server activity, including connection events, Member access changes, acceptance records, and checkout events, for fraud prevention and security. This processing is performed internally, as described in the Privacy Policy, and may include device and browser information collected when a User signs in to connect an Agent.

ARTICLE 8. FEES

8.1No Charge. Access to the MCP Server is free. Engine reserves the right to introduce fees for the MCP Server on thirty (30) days’ written notice to Members.

ARTICLE 9. DISCLAIMERS, LIMITATION OF LIABILITY, AND INDEMNIFICATION

9.1Agent Disclaimer. ENGINE MAKES NO WARRANTY REGARDING THE ACCURACY OF ANY ACTION AN AGENT TAKES BASED ON A USER’S INSTRUCTIONS OR ON INFORMATION THE AGENT RECEIVES FROM A THIRD PARTY, AND ENGINE DOES NOT CONTROL ANY AGENT OR AGENT PLATFORM. EXCEPT AS PROVIDED IN THIS ARTICLE 9, THE MCP SERVER AND AGENT ACTIONS ARE PROVIDED “AS IS,” CONSISTENT WITH SECTION XXIII OF THE TERMS OF SERVICE.

9.2Engine Responsibility for Its Own Errors. Section 9.1 does not limit Engine’s responsibility for errors in the information the MCP Server itself returns, such as an incorrect price, rate, or cancellation policy. Engine’s liability for those errors is subject to Section 9.3.

9.3Limitation of Liability. Engine’s liability arising from the MCP Server is subject to Section XXIII of the Terms of Service, which limits liability for a booking to the single Confirmed Booking that gave rise to the liability, applies a separate limit to security and privacy incidents, and includes the exclusions stated there.

9.4Indemnification. The Member will defend, indemnify, and hold harmless Engine from third-party claims arising from Agent Actions taken under a User’s connection, including claims arising from the conduct of an Agent or Agent Platform, as provided in Section XXIV of the Terms of Service, which applies to the use of the MCP Server.

ARTICLE 10. CHANGES AND TERMINATION

10.1Changes to Terms. Engine may update these Terms on thirty (30) days’ written notice to Members. A Member that does not accept updated Terms must disable MCP Server access, and each User must accept updated Terms before the User connects an Agent or continues an existing connection. Notwithstanding the notice period, Engine may immediately change, suspend, or restrict any MCP Server function where reasonably necessary to address fraud, security, or legal compliance risk, and will give notice as soon as practicable.

10.2Termination. Engine may terminate the MCP Server for all Members at any time on notice. The sections on Acceptable Use, Disclaimers, Limitation of Liability, and Indemnification survive termination.

ARTICLE 11. GENERAL

11.1Governing Law and Disputes. These Terms are governed by the laws of the State of Colorado, and disputes are resolved as provided in the Terms of Service, including the Denver courts and arbitration provisions.

11.2Entire Agreement; Severability. These Terms, together with the Terms of Service and the Privacy Policy, are the entire agreement regarding the MCP Server. If any provision is unenforceable, the remaining provisions remain in effect.

11.3Notices. Notices under these Terms are given as set out in the Terms of Service.