Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | --- |
| 2 | type: "guide" |
| 3 | title: "Perplexity AI authentication" |
| 4 | description: "Current API-key setup for the Perplexity AI toolkit." |
| 5 | category: "authentication" |
| 6 | visibility: "public" |
| 7 | timestamp: "2026-08-17T00:00:00Z" |
| 8 | tags: |
| 9 | - "perplexityai" |
| 10 | --- |
| 11 | # Perplexity AI authentication |
| 12 | |
| 13 | ## Perplexity AI uses the `generic_api_key` connection field |
| 14 | |
| 15 | The current `perplexityai` toolkit uses API-key authentication. Create the key |
| 16 | in Perplexity's console and provide it as `generic_api_key` during connection |
| 17 | initiation. The key is shown once by the provider, so store it in the |
| 18 | customer's secret manager and never send it to support. |
| 19 | |
| 20 | If a first-party Perplexity tool succeeds but an equivalent Proxy Execute call |
| 21 | returns 401 with the same connection, collect both Log IDs and the redacted |
| 22 | request path. That comparison distinguishes a proxy auth-injection problem from |
| 23 | an invalid provider key without asking the customer to rotate a working key. |