Can an AI agent use Perplexity API?

Q: Can an AI agent pay for Perplexity API?

Payment not reached. No 402 on Perplexity's own hosts (unauth calls give 401; x402./mpp./agents. subdomains do not answer; no x-payment-info, no /.well-known/ucp, docs never mention x402/MPP). Documented Stripe Projects CLI provisions account, project, key and credits headless once a Stripe account has a payment method (on the docs, not exercised: no card). mpp.dev lists a third-party Locus proxy (perplexity.mpp.paywithlocus.com, real 402 WWW-Authenticate: Payment method=tempo intent=charge) that is not Perplexity's endpoint. Free consumer tier exists but sits behind the same Cloudflare challenge.

As of 6 Oct 2026, an AI agent can't use Perplexity API on its own: Cloudflare Turnstile on console sign-up.

Level 1 · Needs a personAgents can't get in on their own.

Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
Access: Can't sign up.
Use: Work not reached.
Pay: Payment not reached.
Leave: Leaving not reached.

To reach L2 · Gets in: let an agent sign up on its own.

With an account set up by a person: not measured yet.

What the levels mean

Visit Perplexity API Follow changes

Driven 6 Oct 2026Same level in 2 drives in a rowRules of 15 Oct 2026Claim this page

Written and checked by our agents from this drive's record. How we write.

Who gets in

Agents on a serverStopped before the sign-up page.
Signed agentsThe site opens.
Agents in a person's browserNot measured yet.

Sign-up page checked 12 Oct 2026. Signed agents: the ones Cloudflare verifies. Where agents come from

What an agent can do in Perplexity API.

On its own

Read all the product's technical documentation automatically, including a version made for AI tools.
Install the official command-line tool.
Start (but not finish) the technical handshake for getting a login token.

What it can't, and why

Create an account or get an API keyThe sign-up and login pages show a 'prove you're human' check that never let the agent through
Ask a question, upload a file, or generate an imageEvery one of these needs an account key, which could not be obtained
Pay for API credits as an agentNo automatic payment option on Perplexity's own site; the documented path needs a human with a credit card

Needs a person

No. Sign-up: needs a human. Sign-up is only in the web UI (console.perplexity.ai, passwordless email code). console.perplexity.ai and www.perplexity.ai answer our signed agent with a Cloudflare challenge (403 cf-mitigated: challenge); in the browser a 'Verify you are human' Turnstile that does not clear.

Official server · no call worked

Does Perplexity API have an MCP server, and can an agent connect to it?

Yes. Perplexity API has an official MCP server.

A new agent can't get in on its own: in the drive of 6 Oct 2026, our agent stopped at sign up (it needs a person). Through the MCP server, 0 of our agent's 2 attempts worked.

What the drive found

APIOpenAPIMCP · officialCLISDKllms.txt–Webhooks–Sandbox

Payment not reached

Can an AI agent pay for Perplexity API?

Payment not reached.

Stripe Projects a third party's
Card checkout

It has a free plan.

What would let agents pay on their own

Accept x402 or MPP on your API. Answer an unpaid call with 402 and a payment challenge, so an agent pays per call or buys credits without an account or a card.

No 402 on Perplexity's own hosts (unauth calls give 401; x402./mpp./agents. subdomains do not answer; no x-payment-info, no /.well-known/ucp, docs never mention x402/MPP). Documented Stripe Projects CLI provisions account, project, key and credits headless once a Stripe account has a payment method (on the docs, not exercised: no card). mpp.dev lists a third-party Locus proxy (perplexity.mpp.paywithlocus.com, real 402 WWW-Authenticate: Payment method=tempo intent=charge) that is not Perplexity's endpoint. Free consumer tier exists but sits behind the same Cloudflare challenge.

From the drive of 6 Oct 2026.

Not reached in this drive: the API key and deleting the account. Every checkpoint, in detail

For the team behind Perplexity API.

Where agents stop in Perplexity API today, and the fixes that get them further, highest impact first.

Stops at sign up

The fixes, highest impact first

Let verified agents through console Cloudflare rulesStep-by-step guide
Add device flow to the API OAuth serverStep-by-step guide
Offer a native agent payment rail

1 more fix

Serve the product MCP server card Step-by-step guide

Claim it free and reply next to the result.
A Drive, $49: your private report, with where agents stop, the evidence and the fixes that move your level.
Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month).

Get a Drive Claim it free

See the example report

Details

Your API, MCP server or CLI is the product? An Audit ($299) also checks every documented route, MCP tool and CLI command against your docs. Compare plans.

Already claimed it? Open it in your dashboard.

Rather not be driven? Block AgentDrivesAgent in robots.txt or write to us. We stop driving it ourselves; this page stays, with its date.

Embed the badge on your site

<a href="https://agentdrives.com/tools/perplexity" rel="nofollow"><img src="https://agentdrives.com/badge/perplexity.svg" alt="AgentDrives · Driven · L1 · Needs a person" height="24"></a>

Behind the level.

Our agent couldn't get into Perplexity API, so the work, its reliability and the crash test aren't measured. The part scores are what it could judge from the outside.

Part scores · level history · paid plans

Part scores

Agent-ready setup

llms.txt: found
OpenAPI: found
MCP server: found
CLI: found

Not measured in this drive: Holds up, Docs match (part of an Audit).

Level history

2 Oct 2026L1Needs a person
6 Oct 2026L1Needs a person

Needs a paid plan

Not counted in the level.

Needs a paid plan
Capability	Plan
Deep Research	Pro/Max or API credits
Model selection	Pro/Max or API credits
Model Council	Max
Video generation	Pro/Max
Perplexity Computer	Computer credits (Pro/Max)

For agents and builders.

The drive as data, every checkpoint and all 20 attempts.

How an agent connects · 4 tips

/api/tools/perplexity.json /tools/perplexity.mdMCP get_tool {"slug":"perplexity"}

Docs are excellent for agents: start at https://docs.perplexity.ai/llms.txt; every page has a .md URL and Accept: text/markdown works.
Everything needs an API key from console.perplexity.ai, which is behind Cloudflare: have a human create a project and key (no card needed to look, credits needed to call).
The hosted MCP server at https://api.perplexity.ai/mcp takes the API key as Bearer, or OAuth (CIMD or DCR) with consent on the console.
pplx auth login only stores an existing key; it does not sign you in.

Every checkpoint, in detail · 9 checkpoints

DocsHeadlessdocs.perplexity.ai/llms.txt and llms-full.txt, .md pages, Accept: text/markdown, 6 OpenAPI specs (30 operations) all fetched headless.
Sign upNeeds a humanSign-up is only in the web UI (console.perplexity.ai, passwordless email code). console.perplexity.ai and www.perplexity.ai answer our signed agent with a Cloudflare challenge (403 cf-mitigated: challenge); in the browser a 'Verify you are human' Turnstile that does not clear.
VerifyNot reachedNot reached: sign-up blocked by the Cloudflare challenge.
KeyNot reachedAPI keys are made in the console (behind the challenge). OAuth for the MCP server: DCR registration works headless, but /oauth/authorize redirects to console.perplexity.ai/oauth/consent, behind the same challenge. No device flow; Stripe Projects route needs a Stripe account with a card and a $10 credit purchase.
First callNot reachedNo key: /v1/agent, /search and the MCP server answer 401 invalid_api_key; pplx CLI says 'No API key configured'.
First actionNot reachedNo key, no account.
PayNot reachedNo 402 on Perplexity's own hosts (unauth calls give 401; x402./mpp./agents. subdomains do not answer; no x-payment-info, no /.well-known/ucp, docs never mention x402/MPP). Documented Stripe Projects CLI provisions account, project, key and credits headless once a Stripe account has a payment method (on the docs, not exercised: no card). mpp.dev lists a third-party Locus proxy (perplexity.mpp.paywithlocus.com, real 402 WWW-Authenticate: Payment method=tempo intent=charge) that is not Perplexity's endpoint. Free consumer tier exists but sits behind the same Cloudflare challenge.
CancelNot reachedNo plan or credits were bought. API is prepaid credits (nothing recurring by default); consumer Pro/Max cancellation not reachable.
DeleteNot reachedNo account was created. One DCR OAuth client remains registered at api.perplexity.ai; no documented way to delete it.

The attempt log · 20 attempts

Attempt log
Capability	Route	Result	Evidence
docs: Find docs index	api	done ✓	https://docs.perplexity.ai/llms.txt 200 text (35947 bytes, H1 '# Perplexity', ## OpenAPI Specs section); llms-full.txt 3.4 MB; 6 OpenAPI specs (openapi.json 3.1.0 with 22 ops; gateway specs 3.0.3), 30 operations total
markdown docs: Accept: text/markdown on docs page	api	done ✓	GET docs.perplexity.ai/docs/getting-started/quickstart with Accept: text/markdown -> 200 content-type: text/markdown; vary: rsc, accept-encoding, Accept, User-Agent; Link header rel=llms-txt, mcp-server-card, agent-card, agent-skills. .md URLs also serve markdown (e.g. /docs/admin/signing-in.md)
MCP server/discover: POST server/discover (2026-07-28) to https://api.perplexity.ai/mcp	mcp	blocked ✓	401 application/json {"error":{"message":"Invalid API key provided...","type":"invalid_api_key","code":401}}; WWW-Authenticate: Bearer resource_metadata="https://api.perplexity.ai/.well-known/oauth-protected-resource". PRM 200 JSON (authorization_servers https://api.perplexity.ai); AS metadata has client_id_metadata_document_supported: true and registration_endpoint (DCR); grants authorization_code, refresh_token only (no device flow)
Computer MCP server/discover: POST server/discover to https://www.perplexity.ai/rest/computer/mcp	mcp	blocked ✓	401 WWW-Authenticate: Bearer error=invalid_token, resource_metadata=https://www.perplexity.ai/.well-known/oauth-protected-resource/rest/computer/mcp (200 JSON, scope asi:query). /.well-known/oauth-authorization-server on www: registration_endpoint (DCR), no client_id_metadata_document_supported, grants authorization_code/refresh_token
cards and preferences: Server cards, A2A card, AI catalog, robots Content-Usage	api	partial ✓	api.perplexity.ai/mcp/server-card 404; www/.well-known/ai-catalog.json 404 (HTML); www agent-card.json 404. docs.perplexity.ai/.well-known/mcp/server-card.json 200 JSON = 'Perplexity Docs MCP' (Mintlify docs search server); docs agent-card.json 200 JSON protocolVersion 0.3; docs agent-skills/index.json 200. www robots.txt: no Content-Usage/Content-signal lines; docs robots.txt: 'Content-Signal: ai-train=yes, search=yes, ai-input=yes' (Cloudflare Content Signals form). No Content-Usage header on www (homepage returns 403 cf-mitigated: challenge)
pay step probes: 402 probes, registries, docs text	api	done ✓	Unauth POST api.perplexity.ai/v1/agent and /search -> 401 invalid_api_key (no 402, no PAYMENT-REQUIRED/Payment challenge). x402./mpp./agents.perplexity.ai: no response. No x-payment-info in any OpenAPI; /.well-known/ucp 404. llms-full.txt: 0 hits for x402/MPP/USDC/L402. x402 Bazaar: no Perplexity resource. mpp.dev lists 'perplexity' integration: third-party (serviceUrl perplexity.mpp.paywithlocus.com; real 402 WWW-Authenticate: Payment method=tempo intent=charge from Locus, not Perplexity's domain). Documented: Stripe Projects 'stripe projects add perplexity/api' creates account+project+key, $10 minimum credit purchase charged to Stripe payment method; console Billing via Stripe card.
sign up for API Portal: Open console.perplexity.ai and Continue with email (passwordless code) as the agent's inbox	api	blocked ✓	same on https://www.perplexity.ai/ (home of the consumer app)
sign up for API Portal: Same, in the real browser (pw)	browser	blocked ✓	console.perplexity.ai and www.perplexity.ai both stay on 'Just a moment...' with a visible Cloudflare 'Verify you are human' Turnstile widget after 15 s (shots 002, 004).
OAuth for remote MCP: Register OAuth client and start authorization code flow for https://api.perplexity.ai/mcp	api	blocked ✓	POST https://api.perplexity.ai/oauth/register -> 201 client_id dcr… (DCR works headless). GET /oauth/authorize (PKCE S256, resource=https://api.perplexity.ai/mcp) -> 302 Location https://console.perplexity.ai/oauth/consent?request=… which is behind the same Cloudflare challenge. AS metadata offers only authorization_code/refresh_token (no device flow, no agent_auth block)
Stripe Projects provisioning: Check stripe projects add perplexity/api route	cli	skipped	docs/getting-started/integrations/stripe-projects.md: 'You do need a payment method on your Stripe account' and 'Creating a new Perplexity API project prompts for a $10 minimum credit purchase'
Search the web from the terminal with the Perplexity CLI: pplx search web 'latest stable Rust release' -n 2	cli	blocked ✓	pplx 2026.07.30 installed headless via documented install.sh (checksum OK). Without a key: {"error":{"code":"AUTHENTICATION","message":"No API key configured. Run `pplx auth login`, set the PERPLEXITY_API_KEY ...","hint":...}}. `pplx auth login` only stores an existing key (no sign-in flow)
Ask a question and get a cited, real-time web answer: Ask 'latest stable Rust release' via POST /v1/agent preset fast, or the perplexity.ai search box	api	blocked ✓	POST https://api.perplexity.ai/v1/agent without key -> 401 invalid_api_key; no key obtainable (sign-up behind Cloudflare Turnstile on console.perplexity.ai); web app www.perplexity.ai -> 403 cf-mitigated: challenge, in browser too
Generate an image/asset from a text prompt: Generate an image in the perplexity.ai composer	api	blocked ✓	POST https://api.perplexity.ai/v1/agent without key -> 401 invalid_api_key; no key obtainable (sign-up behind Cloudflare Turnstile on console.perplexity.ai); web app www.perplexity.ai -> 403 cf-mitigated: challenge, in browser too
Upload a file and ask questions about its contents: Upload a text file to POST /v1/agent or perplexity.ai attachment	api	blocked ✓	POST https://api.perplexity.ai/v1/agent without key -> 401 invalid_api_key; no key obtainable (sign-up behind Cloudflare Turnstile on console.perplexity.ai); web app www.perplexity.ai -> 403 cf-mitigated: challenge, in browser too
Run Deep Research: Try Run Deep Research	none	plan_gated	capabilities.json plan: paid (Pro/Max (consumer) or API credits); API is prepaid credits (docs pricing: pay-as-you-go, Tier 0 $0); Computer MCP docs: 'Computer usage is billed against your Perplexity account credits'. Not reachable anyway: sign-up blocked by Cloudflare Turnstile
Select a preferred AI model: Try Select a preferred AI model	none	plan_gated	capabilities.json plan: paid (Pro/Max (consumer) or API credits); API is prepaid credits (docs pricing: pay-as-you-go, Tier 0 $0); Computer MCP docs: 'Computer usage is billed against your Perplexity account credits'. Not reachable anyway: sign-up blocked by Cloudflare Turnstile
Run Model Council: Try Run Model Council	none	plan_gated	capabilities.json plan: paid (Max); API is prepaid credits (docs pricing: pay-as-you-go, Tier 0 $0); Computer MCP docs: 'Computer usage is billed against your Perplexity account credits'. Not reachable anyway: sign-up blocked by Cloudflare Turnstile
Generate a short video: Try Generate a short video	none	plan_gated	capabilities.json plan: paid (Pro/Max); API is prepaid credits (docs pricing: pay-as-you-go, Tier 0 $0); Computer MCP docs: 'Computer usage is billed against your Perplexity account credits'. Not reachable anyway: sign-up blocked by Cloudflare Turnstile
Use Perplexity Computer: Try Use Perplexity Computer	none	plan_gated	capabilities.json plan: paid (Pro/Max Computer credits); API is prepaid credits (docs pricing: pay-as-you-go, Tier 0 $0); Computer MCP docs: 'Computer usage is billed against your Perplexity account credits'. Not reachable anyway: sign-up blocked by Cloudflare Turnstile
delete account: Delete our account	none	skipped	No account was created (sign-up blocked). One OAuth client registered via DCR at api.perplexity.ai/oauth/register (client_id dcrGCxjy…); no documented endpoint to delete a DCR client