Catalog

Perplexity API

Perplexity data through one normalized API - per-request USD pricing, no subscriptions, and automatic failover on redundant endpoints.

Endpoints1Providers2From · search$2.00/1k req · BadgerFull breakdownRead docs
Uptime
99.51%
30d · 205 calls
Requests
205
30d · weekly, last 12 wks
Response
16.0s
median · 30d
POST

Search

Most used
/v1/run/perplexity.searchperplexity.search
Ask Perplexity a web-grounded question and receive an answer with source citations.
205 /mo
â–¼37.4%
99.51%
16018ms p50
2
from$2.00/1k req
Badger

About the Perplexity API

Every provider prices each endpoint independently, so the table shows the cheapest per endpoint. Open one to compare all providers.

Measured performance

What the Perplexity API actually does

Every call through AnyAPI over the last 30 days, counted here rather than promised.

99.5%
of calls succeeded (205 calls)
Succeeded on first lane 81.0%Recovered by failover 18.5%Failed 0.5%
Response time (204 calls)
Typical (p50)
16.0s
Half of requests finish within 16.0s
p99 response time
111.4s
p99 response time: 99% of requests finish within 111.4s

FAQ

About the Perplexity API

The AnyAPI Perplexity API returns Perplexity data as normalized JSON across 1 endpoint: search. You call one endpoint per job with a single key, and AnyAPI routes each request across 2 sources, falling back automatically when one fails. Pricing is in US dollars, from $2 per 1,000 requests, with no subscription and no monthly minimum. Over the last 30 days, 99.5% of Perplexity calls through AnyAPI succeeded, with a median response time of 16.0 seconds across 205 measured calls.

Pricing is in US dollars, from $2 per 1,000 requests, with no subscription and no monthly minimum. You fund one USD wallet and each call draws it down. Some failed wallet-funded requests incur processing charges that we pass through at cost, with no markup; the error response shows the amount charged.

One endpoint: search. Every one takes the same authentication and returns the same normalized response shape, so reaching a second Perplexity endpoint is a change of URL and nothing else.

Over the last 30 days, 99.5% of Perplexity calls through AnyAPI succeeded, with a median response time of 16.0 seconds across 205 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.