BY CLICKING “I ACCEPT,” “AGREE,” OR ANY SIMILAR BUTTON OR CHECKBOX, REQUESTING, RECEIVING, ACTIVATING, OR USING AN ACCESS KEY, TOKEN, OR OTHER CREDENTIAL FOR THE SERVICE, OR OTHERWISE ACCESSING THE SERVICE, CLIENT AGREES TO BE BOUND BY ALL OF THE TERMS AND CONDITIONS OF THIS CONNECTOR AGREEMENT. IF CLIENT DOES NOT AGREE, OR THE INDIVIDUAL ACCEPTING LACKS AUTHORITY TO BIND CLIENT, CLIENT MUST NOT REQUEST, RECEIVE, ACTIVATE, USE, OR PERMIT ANY PERSON OR SYSTEM TO USE THE SERVICE.

This Connector Agreement is entered into by and between LexBlog, Inc. (“LexBlog”), and the Client accessing the Content available via the LexBlog Service to which this Connector Agreement pertains. This Connector Agreement governs the implementation, access, and use by Client of the Service, and is hereby incorporated into and made a part of the LexBlog Terms of Service located at https://www.lexblog.com/terms-of-service/ (collectively with this Connector Agreement, the “Agreement”). If there is a conflict or ambiguity between this Connector Agreement and the Terms of Service, this Connector Agreement will control with respect to matters specifically within its scope and in all other instances, the LexBlog Terms of Service shall control. The parties agree as follows:   

  1. Definitions.
    1. “AI Agent” means any system, including but not limited to large language models and autonomous or semi-autonomous software agents, that can initiate and orchestrate requests to the Service without direct human review of such requests.
    2. “Content” means any articles, publications, abstracts, metadata, or other materials that are owned or controlled by LexBlog or by any third‑party publishers, aggregators, or rights holders, and which are made accessible to Client via the Service. 
    3. “MCP Client” means any software, system, or tool capable of discovering and invoking MCP tools exposed by the Service. 
    4. “Permitted Users” means Client’s employees, contractors, or agents, and any MCP Clients or AI Agents under Client’s control, each of which to the extent they are authorized to access the Service solely for Permitted Uses in accordance with this Agreement. 
    5. “Service” means the interfaces, endpoints, and related functionality made available by LexBlog that enable Client to access Content, including (i) any application programming interfaces (“APIs”), software development kits, or web services; and (ii) any Model Context Protocol (“MCP”) servers, tools, or compatible interfaces, together with any successor protocols or integration mechanisms.
    6. “TDM” means text and data mining via any automated process of copying, analyzing, or extracting information from Content, in whole or in part, for purposes including but not limited to training, fine‑tuning, evaluating, or validating machine learning or AI models; building publicly available or public-facing search indexes or embeddings; or constructing new, or supplementing existing, datasets which are or will be publicly available or public-facing.
    7. “Updates” means any updates, bug fixes, patches, or other error corrections to the Service that LexBlog generally makes available free of charge to all Clients of the Service.
  2. License. 
    1. License Grant. Subject to the terms and conditions of this Agreement, LexBlog hereby grants Client a limited, revocable, non-exclusive, non-transferable, non-sublicensable right during the term of the Agreement to access and use the Service solely in order to retrieve, use, reproduce, store and display Content made available hereupon, for Client’s own human scholarly research, education, and non‑commercial internal reference purposes, provided that Client may include Content with the original author’s identification and attribution in or upon internal research tools and work product which are made specifically available on a per-client basis (the “Permitted Uses”).    
    2. Use by MCP Client and AI Agents. Client may configure MCP Clients and AI Agents under its control to access the Service, provided that: (i) each such MCP Client or AI Agent uses credentials issued to Client; and (ii) Client ensures that all requests initiated by such systems comply with the Permitted Uses and all restrictions in this Agreement. Without limitation, Client is responsible for all acts and omissions of its MCP Clients, AI Agents, and Permitted Users as if they were Client’s own actions. 
    3. Restrictions. Client shall not use the Service or any Content available thereupon for any purposes beyond the Permitted Uses. Without limiting the foregoing and except as expressly set forth in this Agreement, Client shall not at any time, and shall not permit others to: (i) reproduce, download, store, or redistribute Content, in whole or in substantial part, except as strictly necessary for transient caching within the Service or to display Content to a Permitted User; (ii) provide Content, or any portion thereof, to any third party except as expressly allowed under the Agreement; (iii) use the Service in a manner that circumvents, disables, or attempts to bypass any technical or contractual access controls, rate limits, or AI/TDM opt‑out mechanisms implemented by LexBlog or by any third-party publishers or licensors; (iv) initiate, nor permit MCP Clients or AI Agents to initiate, automated or scripted access patterns that are inconsistent with normal, interactive scholarly use (e.g., systematic downloading of journal backfiles, sequential harvesting of all articles in a collection); (v) use the Service or Content in any manner or for any purpose that infringes, misappropriates, or otherwise violates any intellectual property right or other right of any person, or that violates any applicable law; (vi) use the Service or Content to replicate or attempt to replace, in whole or in part, any of LexBlog’s own commercial offerings or products; or (vii) make available in any form or manner any Content absent the original author’s identification and attribution in the same form as is made available via the Service, regardless of whether for internal or external use or whether Client charges a fee for the same. LexBlog may impose and enforce rate limits, concurrency caps, and other technical safeguards across both API and MCP channels, and may throttle or suspend access that appears to constitute bulk extraction or misuse. 
    4. Additional Restrictions on AI Training, TDM, and Commercialization. In addition to and notwithstanding any other term or condition of this Agreement, Client shall not, and shall ensure that its Permitted Users, MCP Clients, and AI Agents do not: 
      1. No AI Training: (i) use Content, in whole or in part, for training, fine‑tuning, evaluating, validating, or otherwise developing any machine learning, AI, or statistical models; (ii)perform TDM on Content for any purposes other than the Permitted Uses; or (iii) otherwise create or maintain datasets, embeddings, or similar subsets derived from Content for AI training or model development purposes. 
      2. No Competitive Activities: (i) develop, train, or operate any commercial information service, knowledge base, or retrieval system that replicates or competes with the LexBlog Library; or, (ii) provide any fee‑bearing or revenue‑generating service that is primarily composed of or reliant upon Content; provided, for avoidance of doubt, that Clients may include Content in or upon internal research tools and client deliverables and work product even where Client charges a fee for the same. 
      3. Caching: To the extent MCP Clients or AI Agents cache or store Content or responses for technical reasons (e.g., short‑term caching to render a response), such storage must be: (i) strictly transient and no longer than technically necessary; and (ii) limited to fulfilling the specific interactive request initiated by a Permitted User; provided, for avoidance of doubt, that Clients may cache or store Content strictly as necessary to include the same in or upon internal research tools and work product even where Client charges a fee for the same. Client shall not under any circumstances, aggregate such cached outputs to build new datasets or models.
    5. Opt-Out Rights. LexBlog expressly reserves all rights to opt out of AI training, TDM, and similar uses of Content under applicable law, including any statutory text‑and‑data mining exceptions. Client acknowledges and agrees that it shall not rely on any such exceptions to justify AI training or TDM with respect to Content accessed via the Service, unless separately agreed in writing with LexBlog. 
    6. Reservation of Rights. LexBlog reserves all rights not expressly granted to Client in this Agreement. Except for the limited rights expressly granted under this Agreement, nothing in this Agreement grants to Client or any third party, by implication, waiver, estoppel, or otherwise, any intellectual property rights or other right, title, or interest in or to the Service or any of the Content. 
  3. Client Responsibilities. 
    1. Client is responsible and liable for all uses of the Service and Content resulting from access provided by Client, directly or indirectly, whether such access or use is permitted by or in violation of this Agreement. Any act or omission by any Permitted Users that would constitute a breach of this Agreement if taken by Client will be deemed a breach of this Agreement by Client. Client shall take reasonable efforts to make Permitted Users aware of the provisions of this Agreement as applicable to their direct use of the Service and Content and shall cause all Permitted Users to comply with such provisions.
    2. Client shall comply with all terms and conditions of this Agreement, all applicable laws, rules, and regulations, and all guidelines, standards, and requirements that may be made available by LexBlog from time to time. Client shall monitor the use of the Service by Client’s Permitted Users for any activity that violates applicable laws, rules, and regulations or any terms and conditions of this Agreement, including any fraudulent, inappropriate, or potentially harmful behavior, and promptly restrict further access to and use of the Service by any offending users. 
    3. Client will use commercially reasonable efforts to safeguard the Service from infringement, misappropriation, theft, misuse, or unauthorized access. Client will promptly (in any event, within 24 hours) notify LexBlog if Client becomes aware of any infringement of any intellectual property rights in the Service and will fully cooperate with LexBlog in any legal action taken by LexBlog to enforce LexBlog’s intellectual property rights.
  4. Intellectual Property Rights. Client acknowledges that, as between Client and LexBlog, LexBlog owns all right, title, and interest, including all intellectual property rights, in and to the Service and the Content. If Client or any of Client’s Permitted Users sends or transmits any communications or materials to LexBlog by mail, email, telephone, or otherwise, suggesting or recommending changes to the Service, including without limitation, new features or functionality relating thereto, or any comments, questions, suggestions, or the like (“Feedback”), all such Feedback is and will be treated as non-confidential. Client hereby assigns to LexBlog on Client’s behalf, and on behalf of Client’s Permitted Users, all right, title, and interest in, and LexBlog is free to use, without any attribution or compensation to Client or any third party, any ideas, know-how, concepts, techniques, or other intellectual property rights contained in the Feedback, for any purpose whatsoever, although LexBlog is not required to use any Feedback. 
  5. Term and Termination.
    1. Term. This Agreement begins on the earlier of the date Client first accesses the Service or agrees to this Agreement, and will remain effective for a period of 30 days subject to automatic renewals for successive monthly terms, unless earlier terminated pursuant to this Agreement’s express provisions or Client gives LexBlog written notice of non-renewal prior to the expiration of the then-current term (the “Term”).
    2. Termination; Suspension. 
      1. LexBlog may suspend this Agreement, any rights granted herein, and Client’s access under this Agreement, in its sole discretion, for a breach of these terms by Client, with or without prior notice to Client. 
      2. Either party may terminate this Agreement, effective on written notice to the other party, if the other party breaches this Agreement, and such breach: (i) is incapable of cure; or (ii) being capable of cure, remains uncured 10 days after the non-breaching party provides the breaching party with written notice of such breach.
    3. Effect of Expiration or Termination. Upon expiration or termination of this Agreement for any reason all licenses and rights granted to Client under this Agreement will also terminate and Client must cease all further access and use of the Service. Any terms that by their nature are intended to continue beyond the expiration or termination of this Agreement will survive termination. 
  6. Support; Upgrades. This Agreement does not entitle Client to any support for the Service. During the Term, LexBlog will provide Client all Updates which are made generally available in its discretion, all of which shall be subject to the terms and conditions of this Agreement. Client acknowledges that LexBlog may predicate ongoing access of the Service on a requirement for Client to obtain and use the most recent version of the Service.  
  7. Entire Agreement. This Connector Agreement is a binding electronic agreement. Client agrees that its electronic acceptance, including acceptance by clicking a checkbox or button, requesting or activating credentials, or accessing the Service after being presented with this Connector Agreement, constitutes Client’s agreement to be bound by the Agreement to the same extent as a handwritten signature. LexBlog may maintain electronic records of Client’s acceptance, including the date and time of acceptance, account or organization information, applicable version of the Agreement, IP address, and associated Credential issuance or activation information, and such records will be admissible to the extent permitted by applicable law. This Connector Agreement is incorporated into and forms a part of the LexBlog Terms of Service. Except as expressly modified or supplemented by the terms of this Connector Agreement with respect to access to and use of the Service and Content, all terms and conditions of the LexBlog Terms of Service, including but not limited to those terms and conditions pertaining to warranties, disclaimers, indemnities, and liability, remain in full force and effect and shall apply to Client’s and its Permitted Users’ use of the Service and Content under this Connector Agreement. In the event of any conflict or inconsistency between this Connector Agreement and the Terms of Service, this Connector Agreement shall govern solely with respect to the subject matter described herein, and the Terms of Service shall govern in all other respects.