REST API

Estimate a monitor

Before creating: how many people a profile's posts draw per month or one post's counts, and the records that would cost if every one of them were delivered — comments only vs…

POST/v1/monitors/estimate

MCP tool estimate_monitorscope monitors:readNo record cost

Parameters

profilestringoptional

profile URL or public id

poststringoptional

post URL

What your agent reads

The tool description exactly as an MCP client receives it in tools/list — it doubles as the full behaviour of the endpoint.

Before creating: how many people a profile's posts draw per month (its last 30 days of posts: likes, comments) or one post's counts, and the records that would cost if every one of them were delivered — comments only vs with reactions. One vendor call, no record cost. Personas deliver a fraction of this.

Errors follow one format.

Request

curl -X POST "https://api.breaknorm.co/v1/monitors/estimate" \
  -H "Authorization: Bearer $BREAKNORM_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "profile": "https://www.linkedin.com/in/retentionadam"
  }'