Prism

A Prism endpoint is a composite: one call fans out to several platforms in parallel, merges the results, and returns a single computed answer. You do not orchestrate the fan-out, the retries, or the merge yourself.

Base URL: /v1/prism/...

What a composite is

A normal endpoint reads one thing from one source. A composite answers a question that no single source can answer, by calling several of them and doing the reconciliation work in between.

Three properties follow from that, and all three change how you write the client:

1. A composite has legs, and a leg can fail without failing your call. Responses carry a coverage signal (legs[], sources_succeeded, coverage, or a confidence block, depending on the composite) telling you which sources answered. Read it before you read the numbers.
2. A composite is priced per call, not per leg. The price does not go up because a source was slow or a fan-out went wide, except where the request shape itself sets the width.
3. A composite returns the same unified schema as its parts. A profile inside a composite response is byte-identical to the same profile from its native endpoint, so one parser handles both.

When to use a composite instead of N calls

Reach for a composite when the answer needs cross-source reconciliation and you would otherwise write it yourself: deduplication across platforms, weighting one source against another, matching the same entity under two different ids, or holding a fan-out open while slow legs settle.

Stay on the per-platform endpoints when you want one source's raw data, when you need a field the composite does not surface, or when you are refreshing something you already hold. prism/lookup and prism/post-stats exist precisely for that last case and are priced accordingly.

How Prism is priced

Composites come in three pricing shapes.

The bulk endpoints are metered per item at each row's own platform rate, so a 50-handle profiles batch of TikTok handles is 50 credits while the same batch of LinkedIn handles is 250. Only successful rows are charged.

Quote ranges rather than floors when you budget: the roster below shows each composite's base tier price, which is the bottom of the range for the metered and param-derived ones.

For handle-audit, a public response-cache hit costs 0 credits. A non-200 execution failure after deduction receives a full refund, and request-validation errors happen before billing. If every leg fails, the whole call is refunded. Every successful HTTP 200 receives the full request-shaped charge even with partial evidence, and there is no partial refund on that path.

Quickstart

curl "https://www.socialcrawl.dev/v1/prism/handle-audit?handle=mrbeast" \
  -H "x-api-key: YOUR_API_KEY"

4. Read computed fields

Direct post and author endpoints inside a composite response may include the shared computed fields such as engagement_rate, language, and content_category. See Computed fields for formulas and null semantics.

Brand health

How is this brand doing right now?

share-of-voice is 20 credits per brand web-only and 40 per brand with social (the default), so the price is fixed by how many brands you pass and whether include contains social. Pass competitor to earned-media to see which outlets covered them and not you.

# Is the conversation moving against us, and by how much?
curl "https://www.socialcrawl.dev/v1/prism/crisis-radar?brand=Figma" \
  -H "x-api-key: YOUR_API_KEY"

Creators

Should we work with this person?

handle-audit and creator-card are 5 credits for up to 4 platforms and +1 per extra. Run handle-audit before you spend on the pull.

# 1. Vet the handle and get a cost projection before committing
curl "https://www.socialcrawl.dev/v1/prism/handle-audit?handle=mkbhd" \
  -H "x-api-key: YOUR_API_KEY"

# 2. If it scores well, run the full partnership check
curl "https://www.socialcrawl.dev/v1/prism/creator-vet?handle=mkbhd&platform=youtube" \
  -H "x-api-key: YOUR_API_KEY"

Commerce and apps

What do buyers actually say?

product-reviews tells you what buyers said. review-integrity tells you whether to trust the stars. app-reviews covers review text. apps-lookup compares the listings, and its title-match guard is what stops two apps sharing a name from being merged.

# Reviews for one product across marketplaces
curl "https://www.socialcrawl.dev/v1/prism/product-reviews?asin=B0DGHMNQ5Z" \
  -H "x-api-key: YOUR_API_KEY"

Developer ecosystem

How is this tool landing with engineers?

launch-echo is the single-moment view; devtool-pulse is the standing one. org-radar is 1 credit base plus 5 per repo expanded, up to 10 repos. Set repos to control it.

curl "https://www.socialcrawl.dev/v1/prism/org-radar?org=vercel&repos=3" \
  -H "x-api-key: YOUR_API_KEY"

AI visibility and research

A probe on ai-visibility is one prompt times one run times one engine, so a 5-prompt, 3-run, 2-engine sweep is 60 credits. The ceiling across the widest possible sweep is 1605, so set prompts, runs and engines deliberately, or use preset=quick|standard|deep, which sets runs and caps prompts for a flat probe budget. The engines are Perplexity Sonar and Grok, and appearance is detected deterministically via recognition tokens rather than by a model's judgement. Add include=web_baseline to see which AI-cited domains you do not yet rank on. No per-platform endpoint covers this.

# Start narrow: 1 engine, 1 run, a short prompt list
curl "https://www.socialcrawl.dev/v1/prism/ai-visibility?brand=SocialCrawl&topic=social%20media%20api&engines=perplexity&runs=1" \
  -H "x-api-key: YOUR_API_KEY"

Go-to-market, hiring, and Korea

Truth Social has no search, so truthsocial-pulse is the way to watch an account without chaining calls. On korea-gap the social leg is the default. Drop social from include if you only need the web comparison.

Per-object workhorses

The cheap ones you call constantly rather than once a week.

lookup sniffs the platform and resource, dispatches, and adds no surcharge: a social post routes to 1 credit, an Amazon product to 5. It takes ITEM links only, so a profile, channel or storefront URL is a free 400 pointing you at that platform's own /profile endpoint. The resolved block names the platform, endpoint, and archetype so an agent knows the shape that follows.

post-stats and profiles bill 1 credit on most platforms and 5 for Instagram and LinkedIn. Dead, errored, and unsupported URLs are refunded and never fail a post-stats batch, and only successful rows are charged on profiles. profiles supports instagram, tiktok, youtube, twitter, threads, twitch, snapchat, truthsocial, bluesky, kwai, linkedin, and facebook. That roster is this endpoint's own, and is unrelated to the universal-search fan-out.

comment-lookup takes each item as either { comment_url } or { platform, post_url, comment_id }, bills TikTok at 2 and Instagram at 5 (more with deep_scan), and holds at most 100 credits for the whole batch. Store each row's lookup.position_hint and pass it back next run to keep a daily refresh near the floor.

# One URL, whatever platform it is
curl "https://www.socialcrawl.dev/v1/prism/lookup?url=https://www.youtube.com/watch?v=dQw4w9WgXcQ" \
  -H "x-api-key: YOUR_API_KEY"

# Refresh engagement on a batch of posts
curl -X POST "https://www.socialcrawl.dev/v1/prism/post-stats" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "content-type: application/json" \
  -d '{"urls":["https://www.tiktok.com/@nasa/video/7259262686435118378","https://www.youtube.com/watch?v=dQw4w9WgXcQ"]}'

All endpoints

33 endpoints available.

Platform notes

• Composites use GET with query parameters, except the bulk endpoints (post-stats, profiles, comment-lookup), which take a POST JSON body.
• Several composites take an include CSV that switches optional legs on or off. On share-of-voice, korea-gap, creator-vet and video-intel that CSV also moves the price, so read it as a cost control rather than a display flag.
• Long-running composites can stream Server-Sent Events when you send Accept: text/event-stream, emitting each leg as it settles. This is the right mode for the 30-credit-and-up composites, which do real fan-out work before they answer.
• A leg can fail without failing your call. Read the coverage signal before the numbers.
• Responses follow the unified SocialCrawl schema, so a profile returned by a composite is byte-identical to the same profile from its native endpoint.

Next steps