This provision authorizes Perplexity to terminate API access and deactivate API Keys for a Customer Application if Perplexity determines the application is competitive with Perplexity or likely to damage Perplexity's reputation, in addition to standard AUP and security violation triggers.
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
The competitive use and reputational harm triggers in this provision are discretionary determinations made by Perplexity without an objectively defined standard. This creates operational dependency risk for businesses that have integrated the Perplexity API into production applications, as access may be terminated without a specific rule violation.
Expands termination rights beyond previous 'without cause' language to include competitive use as explicit grounds, giving Perplexity unilateral power to terminate competitors using their API.
View full change record →Under this clause, Perplexity may deactivate API Keys for applications it determines are competitive with its own services or damaging to its reputation, which could result in loss of API access for downstream business users without a predefined trigger or cure period.
Cross-platform context
See how other platforms handle Competitive Use Suspension Trigger and similar clauses.
Compare across platforms →"Without limitation of its other rights hereunder or at law, if Perplexity determines that a Customer Application is unlawful, unethical, inconsistent with the technical or security requirements set forth in the API Documentation, inconsistent with the AUP, interfering with the operation or integrity of the Services, competitive with Perplexity, or likely to damage Perplexity's reputation or otherwise bring Perplexity into dispute, Perplexity may terminate the license under Section 2.1(ii) in respect of such Customer Application and deactivate the relevant API Key(s).Excerpt from Perplexity AI's Perplexity API Terms of Service
1) REGULATORY LANDSCAPE: This provision may engage FTC Act Section 5 standards on unfair commercial practices if the competitive use trigger is applied in a manner that disadvantages competitors.
Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.
Get the research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.
The competitive use and reputational harm triggers in this provision are discretionary determinations made by Perplexity without an objectively defined standard. This creates operational dependency risk for businesses that have integrated the Perplexity API into production applications, as access may be terminated without a specific rule violation.
Under this clause, Perplexity may deactivate API Keys for applications it determines are competitive with its own services or damaging to its reputation, which could result in loss of API access for downstream business users without a predefined trigger or cure period.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Perplexity AI.