Get the weekly 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. No account.
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.
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 →Monitoring
Perplexity AI has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 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. Depending on jurisdiction and market position, antitrust or competition law authorities in the EU (European Commission, national competition authorities) and the U.S. (DOJ, FTC) may evaluate whether such provisions are applied anticompetitively. The provision does not directly implicate data protection law. 2) GOVERNANCE EXPOSURE: High. The provision grants Perplexity unilateral, discretionary authority to terminate API access based on competitive or reputational determinations without defining what constitutes 'competitive' or 'damaging to reputation.' Businesses that depend on the API for production services face material continuity risk. 3) JURISDICTION FLAGS: EU customers may evaluate this provision under the Digital Markets Act if Perplexity is designated as a gatekeeper, as gatekeepers face obligations regarding fair and non-discriminatory access to platform services. California governing law applies but does not provide Customer with a specific statutory remedy for discretionary API termination. 4) CONTRACT AND VENDOR IMPLICATIONS: This provision may constitute a significant risk factor in vendor due diligence for businesses building production applications on the Perplexity API. Contract negotiators may seek to limit the competitive use trigger or require objective criteria and notice periods before suspension. The agreement provides no cure period for competitive use determinations. 5) COMPLIANCE CONSIDERATIONS: Legal and product teams should assess whether current or planned Customer Applications could be characterized as competitive with Perplexity's own products, and document that assessment. Business continuity plans should account for the possibility of discretionary API Key deactivation. Procurement teams should evaluate whether contractual protections or alternative providers are necessary.
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.