What kinds of social data can Monocrawl's API return?

Updated

Monocrawl's API returns public social data across 70+ platforms through one key and one unified schema. The core data objects are profiles, posts, comments, reviews, products, and prices. If you need to monitor brands, track competitors, analyze feedback, or feed an AI agent, these are the categories you can pull. The API exposes 650+ endpoints over both REST and MCP, so the same data is reachable from a standard HTTP client or an agent that discovers endpoints itself.

Data objects you can request

Object What it covers Typical use
Profiles Account-level fields like handle, verification, follower count Competitor and influencer lookup
Posts Content published by an account, plus engagement Brand monitoring, content analysis
Comments Replies and discussion under posts Sentiment and feedback gathering
Reviews Ratings and review text from review platforms Customer intelligence
Products Listings and product records Price and catalog tracking
Prices Price values and changes over time Price tracking, competitive pricing

The platform list spans social, search, marketplace, review, and developer sources — for example TikTok, Reddit, YouTube, Instagram, X, LinkedIn, Facebook, Google Search, Amazon, eBay, Walmart, Etsy, Airbnb, Booking.com, TripAdvisor, GitHub, Spotify, the App Store, Google Play, and Trustpilot.

How the unified schema handles platform differences

Monocrawl's approach is "shared fields where they match, platform-specific data kept intact." Each response comes in one envelope, so you write the integration once and read common fields the same way regardless of source.

Take a profile request. TikTok and Instagram return different native shapes:

TikTok /profile
{ "unique_id": "northwind", "verified": true,
  "follower_count": 84200, "video_count": 312 }

Instagram /profile
{ "username": "northwind", "is_verified": true,
  "edge_followed_by": { "count": 1260000 }, "posts_count": 1480 }

With Monocrawl, the shared fields are normalized:

Monocrawl /profile
handle      northwind
verified    true
followers   84,200
Platform-specific · kept as returned
video_count 312
platform    tiktok
credits_used 1
cached      false

So handle, verified, and followers are consistent across platforms, while fields with no common equivalent (like video_count) stay as returned. Your code can then destructure the same way every time:

const { handle, verified, followers } = response.data;

This matters when you're pulling from many platforms at once: you don't maintain a separate parser per source for the fields you actually use.

Access methods: REST and MCP

  • REST — 650+ endpoints for direct HTTP calls from your app or backend.
  • MCP — connect once and let an agent discover the endpoints and pull the public-web data it needs. This is aimed at agent workflows where you don't want to hardcode every route.

Both sit behind the same API key and schema, so choosing one is about your consumer (a service vs. an agent), not about different data.

Operational details worth knowing

  • Credits: failed calls cost $0 — you pay for results. Cached repeats cost zero credits.
  • Response time: 2.1s median in Monocrawl's own benchmark.
  • Starting point: 150 free credits, with monthly plans and optional subscriber top-ups available.

What this means for your decision

If your need is public profiles, posts, comments, reviews, products, or prices across many platforms, and you want one schema instead of per-platform integrations, Monocrawl's coverage and normalization fit that job. If you only need one platform's data, a single-platform scraper may be simpler. If you're building an agent that should fetch data on its own, the MCP path is the relevant entry point. Check the specific platforms and endpoints you need against the platform list and API reference before committing, since coverage and field availability vary by source.