Monitors API

List monitor findings

The findings a subject or feed monitor has recorded, newest first: each with its platform, author, link, posted time, relationship to the subject and the purpose filters it matched. A finding is recorded once per monitor, however many runs see it.

Read as Markdown Use with an AI agent

Endpoint

GET/v1/monitors/findingslive · provenfree

Try in Playground

Monitor relevance

Optional filtering and saved matching results

Use relevance_enabled, relevance_prompt and exclusions on creation or update. Monitor reads return the settings; findings return retained matches and evidence; runs show processing and undecided counts. Dashboard, API and MCP share the same backend. Follow the setup and pagination examples, uncertainty guide or Claude/MCP example.

Parameters

Query parameters

Name	Required	Description	Example
`id`	yes	Monitor id	`mon_0f2c8b1d4e6a7c9b0d1e2f3a`
`unseen`	no	Only findings not yet marked as seen	`true`
`run_id`	no	Only findings first recorded by this run	`42`
`limit`	no	Page size, 1-200 (default 50)	`50`
`cursor`	no	Opaque cursor from the previous page
`mark_seen`	no	Mark the returned findings as seen	`true`
`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.	`1`

Examples

Make the request

curl

curl "https://www.monocrawl.com/v1/monitors/findings?id=mon_0f2c8b1d4e6a7c9b0d1e2f3a" \
  -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/monitors/findings?id=mon_0f2c8b1d4e6a7c9b0d1e2f3a",
  { 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/monitors/findings?id=mon_0f2c8b1d4e6a7c9b0d1e2f3a",
    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": "monitors",
  "endpoint": "/v1/monitors/findings",
  "data": {
    "items": [],
    "count": 0,
    "cursor": null,
    "has_more": false,
    "unseen": 0
  },
  "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
`items`	`array \| null`	Nested response fields; optional unless explicitly documented.
`items[].id`	`string \| null`	id
`items[].monitor_id`	`string \| null`	monitor id
`items[].kind`	`string \| null`	kind
`items[].title`	`string \| null`	title
`items[].text`	`string \| null`	text
`items[].url`	`string \| null`	url
`items[].platform`	`string \| null`	platform
`items[].first_seen_at`	`string \| null`	first seen at
`items[].last_seen_at`	`string \| null`	last seen at
`items[].seen_at`	`string \| null`	seen at
`items[].feedback`	`string \| null`	feedback
`items[].data`		Operation-specific JSON value; inspect the status and requested operation before reading it.
`count`	`number \| null`	Nested response fields; optional unless explicitly documented.
`cursor`	`string \| null`	Nested response fields; optional unless explicitly documented.
`has_more`	`boolean \| null`	Nested response fields; optional unless explicitly documented.
`unseen`	`number \| null`	Nested response fields; optional unless explicitly documented.

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

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

List monitor findings

Optional filtering and saved matching results

Query parameters

Make the request

Response fields and example

More Monitors reference

First call in under a minute