If something goes wrong with the API and you suffer losses, Perplexity's financial responsibility is capped at the lower of $100 or what you paid them in the last three months.
This analysis describes what Perplexity AI's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision significantly limits the financial recourse available to developers who suffer business losses due to API failures, outages, or data incidents, even if those losses are substantially larger than the capped amount.
Interpretive note: Enforceability may be limited for claims involving gross negligence, GDPR data subject rights, or statutory causes of action that cannot be waived by contract.
Developers who experience significant business disruption or data incidents attributable to the Perplexity API have limited contractual ability to recover losses beyond a small fraction of fees paid, which may be materially inadequate for businesses with substantial API-dependent revenue.
How other platforms handle this
Except as stated in Section L.3.b, the liability of each party, and its affiliates and licensors, for any damages arising out of or related to these Terms (i) excludes damages that are consequential, incidental, special, indirect, or exemplary damages, including lost profits, business, contracts, re...
TO THE EXTENT PERMITTED BY LAW, THE TOTAL LIABILITY OF FITBIT, AND ITS SUPPLIERS AND DISTRIBUTORS, FOR ANY CLAIMS UNDER THESE TERMS, INCLUDING FOR ANY IMPLIED WARRANTIES, IS LIMITED TO THE AMOUNT YOU PAID US TO USE THE SERVICES (OR, IF WE CHOOSE, TO SUPPLYING YOU THE SERVICES AGAIN) DURING THE TWELV...
To the full extent permitted by law, craigslist, Inc., and its officers, directors, employees, agents, licensors, affiliates, and successors in interest ("CL Entities") (1) make no promises, warranties, or representations as to CL, including its completeness, accuracy, availability, timeliness, prop...
Monitoring
Perplexity AI has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 10 platforms.
"To the maximum extent permitted by applicable law, in no event will Perplexity's aggregate liability to you for any claims arising out of or related to these Terms or the API exceed the greater of one hundred dollars ($100) or the amounts paid by you to Perplexity in the three months preceding the claim.— Excerpt from Perplexity AI's Perplexity API Terms of Service
REGULATORY LANDSCAPE: Liability caps are standard in SaaS and API agreements and are generally enforceable under US contract law. However, they may not apply to claims arising from gross negligence, willful misconduct, fraud, or certain statutory violations. Under GDPR, data protection liability cannot be contractually waived entirely, and supervisory authorities or data subjects may have independent claims. The FTC and relevant state attorneys general retain enforcement authority irrespective of contractual liability caps. GOVERNANCE EXPOSURE: Medium. A $100 minimum floor is at the low end of liability caps observed in commercial API agreements. For high-volume enterprise users, the three-month fee cap may represent meaningful exposure, but for lower-tier users the $100 minimum may be the operative limit. Legal teams should assess whether this cap is compatible with obligations owed to their own customers. JURISDICTION FLAGS: EU/EEA users processing personal data may retain statutory claims under GDPR independent of this contractual cap. Some US states limit the enforceability of liability caps in consumer protection or data breach contexts. Financial services and healthcare-adjacent deployments may face sector-specific liability standards that supersede contractual caps. CONTRACT AND VENDOR IMPLICATIONS: Vendor risk assessments should note that the liability cap may be inadequate relative to the business risk of API dependency. Enterprise negotiations should seek higher caps or carve-outs for data incidents and willful misconduct. Insurance coverage analysis should account for the gap between potential losses and recoverable damages. COMPLIANCE CONSIDERATIONS: Legal teams should review whether this cap interacts with any statutory minimum liability standards applicable to their industry or jurisdiction. Data breach response planning should account for the possibility that contractual recovery from Perplexity may not cover notification or remediation costs. Downstream customer contracts should be reviewed to ensure they do not promise remedies that cannot be funded through recovery from the API provider.
Full compliance analysis
Regulatory citations, enforcement risk, and due diligence action items.
Free: track 1 platform + weekly digest. Watcher: 10 platforms + same-day alerts. No credit card required.
Professional Governance Intelligence
Need to monitor specific governance provisions?
Professional includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
This provision significantly limits the financial recourse available to developers who suffer business losses due to API failures, outages, or data incidents, even if those losses are substantially larger than the capped amount.
Developers who experience significant business disruption or data incidents attributable to the Perplexity API have limited contractual ability to recover losses beyond a small fraction of fees paid, which may be materially inadequate for businesses with substantial API-dependent revenue.
ConductAtlas has identified this type of provision across 5 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Perplexity AI.