Agent platform

Stalkr is built for agents

Every supported workflow is exposed through one capability layer, then published as a versioned REST API and an authenticated MCP server. Webhooks push core events back to your systems.

REST API

Predictable HTTP endpoints and OpenAPI.

MCP server

Native tools for ChatGPT and MCP clients.

Webhooks

Signed, retried event delivery.

One capability contract

Stalkr currently exposes 44 agent operations covering projects, team access, keywords, mentions, categories, saved views, alerts, LinkedIn, usage, account settings, and webhooks. Each operation has one validation schema, permission scope, rate class, audit name, REST route, MCP tool, and generated reference page.

Feature parity by construction

New product workflows are added to the capability registry first. The dashboard, REST API, MCP catalog, OpenAPI document, and reference docs reuse that contract so agent support cannot become an afterthought.

Start in two minutes

REST

curl https://www.stalkr.ai/api/v1/projects \
  -H "Authorization: Bearer $STALKR_API_KEY"

MCP

Server URL: https://www.stalkr.ai/mcp
Authentication: OAuth 2.1 (recommended for ChatGPT)

Follow the complete quickstart →

Security and limits

Every resource lookup is resolved through the authenticated user’s workspace and project membership. Inaccessible project resources return not found, editor and owner roles are enforced on writes, OAuth uses PKCE, API keys are hashed, webhook secrets are encrypted, and webhook URLs are checked against private-network and redirect attacks.

Trial accounts can use the full agent surface. Machine-call rate limits are tighter on trial, while the existing keyword, mention, scan, provider, seat, and alert caps remain the source of truth.