POST · mentions:write

Mark mention irrelevant

Permanently remove an irrelevant mention from its project, optionally preserve context as relevance feedback, prevent re-ingestion, and credit eligible current usage. Daily limits: Free 3, Starter 10, Pro 30, and Scale 100 successful markings per workspace per UTC day.

Destructive

REST

POST/api/v1/mentions/:mentionId/irrelevant

curl "https://www.stalkr.ai/api/v1/mentions/:mentionId/irrelevant" \
  --request POST \
  --header "Authorization: Bearer $STALKR_API_KEY" \
  --header "Content-Type: application/json" \
  --header "Idempotency-Key: unique-operation-key"

MCP

Tool name: mark_mention_irrelevant

The MCP tool accepts the same input schema and returns the same structured { data, meta } result as REST.

Input

reason

string

Optional context about why this mention does not belong to the project; used as relevance feedback

mentionIdrequired

string

idempotencyKey

string

Unique key used to safely retry this write operation

Safe retries

Pass idempotencyKey to the MCP tool or Idempotency-Key to REST when retrying this write.

Authorization

Required scope: mentions:write.

Scope authorization is followed by resource authorization. Project operations check current membership and the minimum role required by the underlying workflow.

Related resources

REST conventions · MCP setup · Errors and limits