API & AI CONNECTOR ADDENDUM

Version: api-ai-addendum-1.0 Effective: 2026-10-30

This Addendum supplements the ten31tracker Terms of Service ("Terms") and applies when Customer enables API keys, webhooks, or the Model Context Protocol (MCP) connector (together, the "Developer Features").

  1. Authorization. By creating an API key or registering a webhook, an authorized Customer administrator represents that they have authority to bind Customer and that Customer authorizes ten31tracker to disclose Customer Data accessible under the selected scopes to any client that presents that key, including third-party applications and generative AI assistants Customer chooses to connect.

  2. Customer as controller; ten31tracker as processor for the connection. For Developer Features, Customer determines the purposes of connecting third-party tools. ten31tracker processes and transmits Customer Data to those tools solely as instructed by Customer’s key, scopes, and webhook configuration. Customer is responsible for the third party’s collection, use, retention, training, and security practices.

  3. Third-party AI and apps. Developer Features may be used with software ten31tracker does not own or control. ten31tracker does not endorse those tools, does not supervise their models or prompts, and has no obligation arising from Customer’s use or inability to use them. Customer’s use of third-party tools is at Customer’s own risk.

  4. No warranty on AI outputs. Drafts, summaries, deadline calculations, and other outputs produced by third-party AI tools using data from ten31tracker — including any draft identification notice text returned by MCP — are provided without warranty. They are not legal, tax, or financial advice; they are not a signed identification; and they do not satisfy Treas. Reg. §1.1031(k)-1 by themselves. Customer must have qualified personnel review every output before relying on it.

  5. Attorney-client confidentiality and professional duties. Where Customer is a lawyer, law firm, or qualified intermediary subject to professional rules, Customer remains solely responsible for confidentiality, competence, communication, and informed consent obligations (including those discussed in ABA Formal Opinion 512 (2024) and applicable state rules). Connecting an AI tool that may retain or train on prompts is Customer’s decision; ten31tracker does not obtain client informed consent on Customer’s behalf.

  6. Key and secret security. Customer must store API keys and webhook signing secrets as credentials, disclose them only to intended systems, rotate or revoke them on suspected compromise, and use the minimum scopes necessary. Customer is responsible for all activity under its keys unless caused by a vulnerability in the Service itself.

  7. Suspension. ten31tracker may suspend Developer Features for a firm or key that presents a security risk, exceeds rate limits, or violates the Terms or this Addendum, with notice when practicable.

  8. Indemnity. Customer will defend and indemnify ten31tracker LLC and its officers, directors, and employees against third-party claims arising from (a) Customer’s or its agents’ use of Developer Features; (b) any third-party AI or application Customer connects; (c) Customer’s failure to obtain required consents; or (d) outputs Customer publishes or acts on after receiving them through Developer Features.

  9. Liability. Subject to the Exceptions in the Terms, ten31tracker’s aggregate liability arising from Developer Features is limited as stated in the Terms’ Liability Cap. In no event is ten31tracker liable for third-party AI errors, model hallucinations, unauthorized key use by Customer’s agents, or missed exchange deadlines following Customer’s reliance on third-party outputs.

  10. Conflict. If this Addendum conflicts with the Terms on Developer Features, this Addendum controls. Capitalized terms not defined here have the meaning in the Terms.