# Perplexity setup for PopMCP

Nothing has to be typed into PopMCP. You click Authorize with Perplexity, sign in, choose the API organization to bill and approve PopMCP. There is no developer app or callback URL to set up. Under More options you can paste an API key instead of signing in, and add the Enterprise Analytics and audit log keys.

- Auth: OAuth authorization
- Setup time: 2 min
- API base URL: https://api.perplexity.ai
- Credentials screen: https://console.perplexity.ai/project/keys
- Provider docs: https://docs.perplexity.ai/docs/getting-started/quickstart

## Approval required before this works

No one reviews you, but the API runs on credits bought in advance. A Perplexity subscription and API credits are separate things, so check the API organization has credits before you connect.

- Typical wait: None. Credits are available as soon as you buy them.
- Cost: Pay as you go, from Perplexity's pricing page. As a guide, 1,000 Search API requests cost $5 and Agent API runs bill per token and per tool call. PopMCP adds nothing to this.
- Blocked until approved: Asking, research, search, embeddings and batches. Keys are blocked when credits run out. Connecting and listing models still work, so you can set up first.
- Works meanwhile: Connect Perplexity in PopMCP and list the models. Both are free.

## Before you begin

- A Perplexity account with an API organization, which you create in the API portal at console.perplexity.ai
- To sign in: you must be an admin of that API organization
- API credits on that organization, because every question and search is billed to them. Credits are bought in advance on the Billing page
- Pop-up blockers must allow the Perplexity sign-in window to open
- Only if the AI should change anything: an owner or admin in PopMCP to allow write actions

## Get your credentials

### 1. Make sure your API organization has credits

Open the [API portal](https://console.perplexity.ai) and sign in. If you have never used the API, fill in your organization's details under Settings, then open Billing, add a card and buy some credits. Questions and searches are billed to these credits, and keys stop working when they run out. Turning on auto top-up avoids that. If your organization already has credits, skip this step.

Screen: https://console.perplexity.ai/project/billing

### 2. Start the connection from PopMCP

Open the Perplexity connector in PopMCP and click Authorize with Perplexity. There are no fields to fill in: no API key, no developer app and nothing to register.

### 3. Sign in, choose the organization and approve

The sign-in window opens on console.perplexity.ai. Sign in with your regular Perplexity account, choose the API organization to bill, and approve PopMCP. The connection can call the API for that organization. It cannot create API keys, see your balance or manage the organization.

### 4. Or use an API key instead

Prefer not to sign in? In the API portal open API keys and generate a key. It starts with `pplx-` and is shown only once, so copy it straight away. In PopMCP open More options, paste it and connect.

Screen: https://console.perplexity.ai/project/keys

### 5. Add the Enterprise keys if you have them

Optional, for Perplexity Enterprise organizations. To let the AI read your organization's usage, an org admin turns on Analytics API in the Perplexity web app under the organization's Computer settings, then selects Generate key. To let it read audit events, an org admin turns on audit logging, then creates a key under organization settings, Enterprise APIs, Audit API. Paste them in PopMCP under More options before you click Authorize. Each key works only for its own data.

### 6. Check it is connected

The Perplexity card in PopMCP reads Connected. Asking questions and searching work straight away, and they spend credits even on a read-only connection. New connections start read-only, so changing skills, files or batches and using connectors wait until an owner or admin allows write actions in PopMCP.

## Fields PopMCP asks for

- How you connect (connectionType): Click Authorize, sign in to Perplexity, choose the API organization to bill and approve. You need to be an admin of an API organization with credits.
- API key (instead of signing in) (apiKey): Only if you prefer not to sign in. Generate one on the API Keys page of the Perplexity API portal. It is shown once.
- Analytics API key (Enterprise) (analyticsKey): Optional, to read your organization's usage. An org admin generates it in the Perplexity web app under the organization's Computer settings, Analytics.
- Audit log API key (Enterprise) (auditKey): Optional, to read audit events. An org admin creates it under organization settings, Enterprise APIs, Audit API. Audit logging must be on.

## Scopes requested

- perplexity_api
- offline_access

## Verify

The Perplexity card in PopMCP shows Connected. Asking the AI for the connection profile (`perplexity_connection_profile`) shows how it signed in and which Enterprise keys are on, and listing models (`perplexity_list_models`) is free and returns model ids rather than an authorization error.

## Troubleshooting

### The sign-in window never opens

Cause: A pop-up blocker is stopping the Perplexity sign-in window.

Fix: Allow pop-ups for PopMCP in your browser and click Authorize with Perplexity again.

### The sign-in page asks you to create an organization

Cause: You are not an admin of an API organization that can pay for usage.

Fix: Create one in the API portal, or ask an admin to connect, then start the connection again.

### "Perplexity refused this sign-in"

Cause: Your login is not an admin of the organization you chose, or the sign-in could not be used.

Fix: Sign in as an admin, or paste an API key under More options instead.

### "Perplexity did not accept that API key"

Cause: The key was copied in part or revoked, or an Analytics or audit log key was pasted in the API key field.

Fix: Generate a new key on the API keys page and paste it. Enterprise keys go in their own fields.

### The AI says the account is out of credits

Cause: Keys are blocked once the credit balance runs out.

Fix: Buy more credits on the Billing page, and turn on auto top-up if you want this not to happen again.

### A long research task comes back as still running

Cause: Deep research can take several minutes, longer than one tool call waits.

Fix: Nothing is wrong. Ask the AI to check again: it picks the result up by its id without starting or paying for the task again.

### Rate limit errors while the AI checks on research

Cause: New accounts get one Agent API request a second, and checking on a task counts. Limits rise with credits purchased.

Fix: Wait a moment and ask again. Your usage tier is on the Pricing page of the API portal.

### The AI says a connector or MCP tool needs write access

Cause: Those tools can change things in other services, so a read-only connection refuses them.

Fix: An owner or admin can allow write actions on this connection in PopMCP.

### Orchestrator tools answer 403

Cause: The Orchestrator API is in private preview, and your account is not in it.

Fix: Use the question and research tools instead, or ask Perplexity for access.

---

Source: https://www.docs.popmcp.com/docs/integrations/perplexity/