SocialCrawl

Perplexity

Web-grounded research via Perplexity Sonar — natural-language questions, real source citations

Perplexity

Web-grounded research via Perplexity Sonar. Ask natural-language questions, get a synthesised answer plus the URLs Sonar cited as evidence. 1 endpoint available.

Base URL: /v1/perplexity/...

Perplexity uses the same authentication and credit model as every other SocialCrawl endpoint — pass your x-api-key header, pay 1 credit per call, get a unified response envelope. The fact that the upstream is the Vercel AI Gateway → Perplexity Sonar is invisible to you.

Best for freeform questions like "what is the latest funding round for Anthropic?" or "summarise this week's biggest LLM releases" that need fresh, web-grounded answers — the kind of question a structured social-media call cannot answer.

Getting Started

1. Run a research query

curl "https://api.socialcrawl.dev/v1/perplexity/research?query=what+is+the+capital+of+france" \
  -H "x-api-key: sc_your_api_key_here"

2. Read the answer + sources

{
  "success": true,
  "platform": "perplexity",
  "endpoint": "/v1/perplexity/research",
  "data": {
    "answer": "Paris is the capital of France.",
    "sources": [
      {
        "url": "https://en.wikipedia.org/wiki/Paris",
        "title": "Paris - Wikipedia"
      }
    ]
  },
  "credits_used": 1,
  "credits_remaining": 99,
  "request_id": "req-a1b2c3d4e5f6",
  "cached": false
}

data.sources is always an array. Empty arrays are legal — Sonar may answer one-line factual questions without citing.

Endpoints

EndpointPathCredit Tier
Web research via Perplexity Sonar/v1/perplexity/researchstandard (1cr)

Response Shape

Both fields are always present on success:

FieldTypeNotes
data.answerstringSonar's natural-language reply, grounded in the live web sources it found.
data.sources{ url, title? }[]URL citations Sonar used to ground the answer. Order matches Sonar's emitted order.

Notes

  • All endpoints use GET method with query parameters
  • Authentication via x-api-key header
  • Responses follow the unified SocialCrawl envelope (success, data, credits_used, credits_remaining, request_id, cached)
  • Refunded automatically on upstream failure (502 UPSTREAM_ERROR) — you are never out-of-pocket on a transient blip
  • Computed-fields enrichment (engagement_rate, language, etc.) does not apply — this endpoint returns research output, not social content
Perplexity | Socialcrawl