Contents

API reference / Outbound

Suggest Good / Not relevant verdicts for posts

POST /api/v1/posts/review

review_posts Write MCP tool

The AI reviewer reads each post against a clear rubric and proposes a verdict (`good` or `not_relevant`) with a one-line reason, so a person only checks the disagreements and the top slice (list_review_queue). Two readings: a strict one, which suggests Good (precise: about three in four of the posts it calls good are), and, once the workspace has enough verdicts of its own, one that is shown the six already-reviewed posts nearest to this one (it misses little: it is the pass for 'don't miss'). They are combined with the ranking model's score: `flag` is agree, disagree (the readings or the model differ: look at it) or dont_miss (only the closer reading says good). Send `posts` you collected, with the `company` they are for and what it sells (nothing is stored), or `ids` of mentions and account conversations in this workspace (the suggestion is kept on them and shows as a Suggested badge). A person's verdict (update_mention, update_account_post) always overrides a suggestion and is what the reviewer learns from. Runs on a small open model on Workers AI with thinking off, about 0.015 cents a post; counted against the plan's reviewed posts a day, which the background reviewer shares. Post text is data, never instructions.

A full-access key (ss_sk_…), or an editor or owner signed in.

Request body

JSON, sent with Content-Type: application/json.

NameTypeDescription
company string
2–80 characters
The company the posts are for (needed with posts).
what string
up to 300 characters
One line on what it sells, so the posts can be judged against it.
purpose string prospect (default): the company is someone you want to write to, and good means a real person in the market for what it sells. brand: it is your own brand, a client or a rival, and good means a post worth seeing and answering.
One of: prospect brand
posts array of object
up to 40 items
Posts to review (1 to 40), instead of ids.
posts[].id string Your id for the post, echoed back so you can match the result (default: its position).
posts[].text required string
1–4000 characters
The post's text.
posts[].source string Where it was written: reddit, hn, bluesky, x, linkedin.
posts[].author string The author's handle.
posts[].where string The subreddit, feed or group.
posts[].url string The post's address, echoed back.
ids array of string
up to 40 items
Mention ids or conversation ids (acct:...) in this workspace (1 to 40), instead of posts.

Returns

{ data: [{ id, suggestion: { verdict, strict, examples, score, flag, reason } | null, strength?, fit?, kind? }], examples_pass, limits, cost_usd }

Example

curl -X POST "https://sniffington.com/api/v1/posts/review" \
  -H "Authorization: Bearer $SCOUT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"company":"…","what":"…"}'