79 Total

Key Facts · in the document’s own words

What does Together AI limit its aggregate liability to?
“excluding customer's payment obligations, any aggregate liability in excess of the amounts paid by customer during the twelve (12) months preceding the claim”
Version CA-V-002838, captured May 21, 2026 · live source ↗
Our reading, not the document’s words
Together AI limits its aggregate liability to the amounts paid by the customer during the twelve months preceding the claim, excluding the customer's payment obligations.
What must the customer authorize?
“You authorize the Company to replenish your account by charging a minimum or the higher average monthly usage to Customer's payment instrument each time Customer's account balance falls below the replenishment threshold.”
Version CA-V-002838, captured May 21, 2026 · live source ↗
Our reading, not the document’s words
Together AI requires the customer to authorize automatic charges to their payment instrument — for a minimum amount or the higher average monthly usage — each time the account balance falls below the replenishment threshold.
What will Together AI defend the customer against?
“The Company will defend Customer against any claim...alleging that the use of the Services as permitted hereunder infringes or misappropriates a United States patent, copyright, or trade secret...”
Version CA-V-002838, captured May 21, 2026 · live source ↗
Our reading, not the document’s words
Together AI will defend the customer against any third-party claim alleging that the customer's permitted use of the Services infringes or misappropriates a United States patent, copyright, or trade secret.
Does Together AI exclude liability for indirect, special, incidental, consequential, or punitive damages?
“Limitation of Liability Except for a party's indemnification obligations, gross negligence, willful misconduct, or infringement or misappropriation of the other party's intellectual property rights, to the maximum extent permitted under applicable law, under no legal theory...will either party be liable to the other under this agreement for (a) any indirect, special, incidental, consequential, or punitive damages, including damages for loss of use, lost profits...”
Version CA-V-002838, captured May 21, 2026 · live source ↗
Our reading, not the document’s words
Together AI excludes liability to the other party for any indirect, special, incidental, consequential, or punitive damages — including damages for loss of use and lost profits — under any legal theory.
What are payment obligations?
“Except as otherwise specified herein or in such order form, payment obligations are non-cancelable and non-pro-ratable for partial months, and fees paid are non-refundable.”
Version CA-V-002838, captured May 21, 2026 · live source ↗
Our reading, not the document’s words
Together AI requires that payment obligations are non-cancelable and non-pro-ratable for partial months, and that fees paid are non-refundable.
What does Together AI cap its indemnification obligation at?
“Such indemnification shall be limited to $1,000,000 (one million dollars).”
Version CA-V-002838, captured May 21, 2026 · live source ↗
Our reading, not the document’s words
Together AI caps its indemnification obligation at one million dollars.
Stay ahead of the changes
Track Together AI and hear on the next check after its terms change. We check daily where we can, and show you where we can't.
Summary
Generated by a model from the captured document; not read by a person

This document sets the rules for using Together AI's Services and determines who is responsible for what. You own your content and outputs, but you cannot use the Services to compete with Together AI or to submit financial, medical, or sensitive personal data. Your payments cannot be refunded and Together AI can automatically charge your payment method when your balance runs low, so unexpected charges are possible.

Analysis

This Agreement establishes the terms under which customers access and use Together AI's Services, setting out substantive obligations on both sides. Together AI grants customers use of the Services subject to prohibitions on competitive use, benchmarking, and transmission of financial, medical, or sensitive personal data. Customers exclusively own their Content and Output as against Together AI, while Together AI provides an indemnification commitment — capped at one million dollars — covering third-party U.S. intellectual property claims arising from permitted use. Together AI's aggregate liability is capped at amounts paid in the twelve months preceding a claim, and all consequential, indirect, and punitive damages are mutually excluded. Payment obligations are non-cancelable and non-refundable, automatic replenishment charges are required, and customers have no unilateral right to terminate the Agreement without Together AI's express written consent.

What this means for you

As a user, you exclusively own the content you submit and the outputs you receive, but you bear full responsibility for ensuring you never submit financial, medical, or sensitive personal data through the Services. Your fees are non-refundable and non-cancelable, and you must authorize automatic recurring charges that can scale up to match your higher average monthly usage. If you have a dispute with Together AI, your financial recovery is limited to amounts you paid in the prior twelve months, with no ability to claim lost profits or other consequential losses. You cannot exit the Agreement on your own — Together AI's express written consent is required to cancel or terminate.

Institutional Analysis
Stay ahead of the changes

Institutional analysis available with Insight

Which mapped governance frameworks each document engages, tied to the specific provisions that engage them.

1 important change detected

3 versions captured · Latest change detected by ConductAtlas: May 2026

What changed Together AI added explicit language clarifying payment processing timelines for credits and prepaid balances funded via ACH, wire transfer, or other delayed-settlement methods. The updated terms state that such credits will not be available for use until the company has received and confirmed clearance of the underlying funds, and that the company is not responsible for delays in service access resulting from payment clearing times or for failed, reversed, or returned payments. This establishes that users funding accounts through slower payment methods may experience delays before their credits become usable.
Why this matters The updated terms clarify that credits funded through ACH, wire transfer, or other delayed-settlement payment methods will not be available for use until the company has received and confirmed clearance of the underlying funds. The agreement also states that the company is not responsible for any delays in service access resulting from payment clearing times, or for failed, reversed, or returned payments. Users should expect that service access may be delayed when funding accounts through slower payment methods.
View full change record →
Clauses withheld

We withheld clauses we had published from this document. Each withholding is recorded in our correction log:

Featured provisions
Generated by a model from the captured document; not read by a person

Complete Provision Index

Every distinct legal provision identified in this document. Featured provisions appear above with analysis.

79 provisions
12 featured
19 clause types
Export Controls & Sanctions 1
Refunds & Chargebacks 1
Developer / API Restrictions 1
Stay ahead of the changes

Monitoring

Together AI has updated this document before. Monitor includes alerts from a daily check, structured change summaries, and monitoring for up to 20 platforms.

Stay ahead of the changes

Governance Intelligence

Need provision-level monitoring and regulatory mapping? Insight includes governance timelines, drift analysis, and full provision tracking.

Cross-platform context

See how other platforms handle Aggregate liability cap at twelve months fees and similar clauses.

Compare across platforms →
Archival ProvenanceSource & Archival Record
This version captured May 21, 2026 00:49 UTC
Last successful capture October 15, 2026 00:47 UTC
Capture Method Automated scheduled archival capture
Document ID CA-D-000477
Version ID CA-V-002838
SHA-256 (extracted text, extractor v5) 9e9ea76773684a7f7fa638013066cf69791dd808dea7080bb80ce5c60a2da6fa
✓ Snapshot stored Archived-bytes anchor not yet recorded

Governance Monitoring

Monitor governance changes across the platforms you rely on.

Structured alerts for policy changes, governance events, and provision updates across 343 platforms.

Start monitoring → Compare plans