API reference

Platform Status API

Per-provider health over the last 15 minutes: request counts, error rate, p50/p95 latency and an up/degraded/unknown state per upstream provider.

Read as Markdown Use with an AI agent

Endpoint

GET/v1/statuslive · provenfree

Try in Playground

Parameters

Query parameters

Useful optional inputs

dry_run — Read a free estimate before fetching sources or scheduling paid work.
Zero credits; cache status and availability are snapshots rather than guarantees.

Name	Required	Description	Example
`dry_run`	no	Read a zero-credit estimate without fetching sources, running AI, or reserving credits. Cache status is a snapshot, not a guarantee at execution. Accepted values: 1, 0, true, false. Case, spaces, hyphens and underscores are interchangeable.	`1`

Examples

Make the request

curl

curl "https://www.monocrawl.com/v1/status" \
  -H "x-api-key: mn_your_key_here"

TypeScript

typescript

const key = process.env.MONOCRAWL_API_KEY;
if (!key) throw new Error('Set MONOCRAWL_API_KEY on your server.');
const res = await fetch(
  "https://www.monocrawl.com/v1/status",
  { headers: { "x-api-key": key } },
);
const body = await res.json();

if (!body.success) {
  // one error shape for every endpoint — see /docs/errors
  throw new Error(`${body.error.type}: ${body.error.message}`);
}

console.log(body.data, "credits left:", body.credits_remaining);

Python

python

import os
import requests

res = requests.get(
    "https://www.monocrawl.com/v1/status",
    headers={"x-api-key": os.environ["MONOCRAWL_API_KEY"]},
    timeout=60,
)
body = res.json()

if not body["success"]:
    # one error shape for every endpoint — see /docs/errors
    raise RuntimeError(f"{body['error']['type']}: {body['error']['message']}")

print(body["data"], "credits left:", body["credits_remaining"])

Response

Response fields and example

This example is illustrative, not a captured live response. Variable-cost operations may settle a charge different from the list price below. A successful response puts the platform payload in data and reports the exact credits used, remaining balance, request id and cache status beside it.

200 · application/json

{
  "success": true,
  "platform": "status",
  "endpoint": "/v1/status",
  "data": {
    "generated_at": null,
    "updated_at": null,
    "latency_scope": null,
    "window_minutes": 0,
    "cache_schema_version": null,
    "latency_excludes": [],
    "platforms": [],
    "upstream_versions": null
  },
  "credits_used": 0,
  "credits_remaining": 99,
  "request_id": "req_…",
  "cached": false
}

The example is illustrative and shows a documented subset of data. The fields below are optional across supported sources; nullable fields can also be absent. Preserve unknown values and accept additional fields.

Schema basis: reviewed response shaper. See schema coverage and validation limits.

Download the data JSON Schema. Validate response.data, not the whole envelope. A valid shape does not establish that every field or source record was returned.

Field inside data	Type	Meaning
`generated_at`	`string \| null`	generated at
`updated_at`	`string \| null`	updated at
`latency_scope`	`string \| null`	latency scope
`window_minutes`	`number \| null`	Nested response fields; optional unless explicitly documented.
`cache_schema_version`		Operation-specific JSON value; inspect the status and requested operation before reading it.
`latency_excludes`	`array \| null`	Nested response fields; optional unless explicitly documented.
`platforms`	`array \| null`	Nested response fields; optional unless explicitly documented.
`platforms[].platform`	`string \| null`	platform
`platforms[].state`	`string \| null`	state
`platforms[].health`	`string \| null`	health
`platforms[].requests`	`number \| null`	requests
`platforms[].errors`	`number \| null`	errors
`platforms[].p50`	`number \| null`	p50
`platforms[].p95`	`number \| null`	p95
`platforms[].circuit_health`	`object \| null`	Nested response fields; optional unless explicitly documented.
`upstream_versions`		Operation-specific JSON value; inspect the status and requested operation before reading it.

Core response fields reviewed from the public response shaper. Fields vary by requested options; additive fields remain allowed.

No recent traffic means unknown, not a guarantee of availability.

Failures use the typed error envelope. A confirmed uncharged or refunded failure reports zero; a pending reconciliation can report an unknown charge. Read credits_used and error.details.billing_status, and keep request_id for recovery. Response contract · Error reference

Platform Status API

Query parameters

Make the request

Response fields and example

Useful next calls

First call in under a minute