Monocrawl documentation

What you get

The whole contract, at a glance

Authentication

x-api-key: mn_…

One account key works across the catalogue.

Request path

GET /v1/{platform}/{endpoint}

The same predictable URL shape everywhere.

Response envelope

success · data · request_id

One parser handles every platform response.

Billing rule

Failed request · 0 credits

The response tells you exactly what was used.

Make your first call OpenAPI specification →

First request

A real call is one curl

Put your key in the header and choose a platform operation. The response carries the data, the exact charge, the remaining balance and a request id for support.

terminal · then 200 application/json

$ curl "https://www.monocrawl.com/v1/github/profile?handle=torvalds" \
    -H "x-api-key: mn_your_key_here"

{
  "success": true,
  "platform": "github",
  "endpoint": "/v1/github/profile",
  "data": { "handle": "torvalds", "followers": 234567, … },
  "credits_used": 1,
  "credits_remaining": 99,
  "request_id": "req_4f2b8c1d09ae37b562",
  "cached": false
}

This example uses github/profile. See the response contract for every field.

Why Monocrawl

Why use a unified API?

Building against dozens of sources directly means separate authentication, pagination, rate limits, error vocabularies and response formats. Monocrawl collapses those differences behind one interface.

Platform-specific fields stay in data, while operational fields stay consistent. That means the same retry, billing, cache and error-handling code works across the catalogue.

600 / min

Rate limit per key

Concurrent requests

Requests per batch

Platform coverage

Popular data platforms

73 external data platforms have recorded successful requests through currently eligible providers. That evidence is historical, not a current health check. These are ten commonly used starting points.

Platform	Proven operations	Reference
Instagram	26	View →
YouTube	25	View →
X	15	View →
TikTok	29	View →
Reddit	9	View →
LinkedIn	25	View →
Facebook	16	View →
GitHub	12	View →
App Store	8	View →
Google Play	8	View →

See all platform coverage

Go deeper

Open the right reference when you need it

Quickstart

Create an account, collect the key and make a real request.

Browse endpoints

Search every wired operation and open its focused reference page.

Choose an endpoint

Start with the job you need to do, not a platform catalogue.

Build a workflow

Pasteable multi-step examples with costs read from the registry.

Frequently asked questions

The short answers

Where can I check the registered endpoints?+

The free GET /v1/utility/endpoints response is authoritative. It contains active registry operations, their list prices and parameter schemas. Registration does not guarantee current upstream availability.

What happens when an upstream fails?+

Production returns a typed error and charges 0 credits. It never silently substitutes sample data. Read the error reference.

Can I build against something that is not wired yet?+

Yes—call the same route under /sandbox. Samples are explicitly marked synthetic: true, cost nothing and never appear on /v1.

Where should I start?+

Use the Quickstart for your first request, then search the endpoint directory when you know what data you need.