Help center

Practical paths for setting up monitoring, reviewing evidence, tuning alerts, and escalating account questions.

Start free trial

Common workflows

These guides point to the shipped product surfaces instead of separate static docs.

Set up a workspace

Add named competitors, confirm high-signal source URLs, and invite the people who review the weekly digest.

Go to workflow →

Read a competitive brief

Start with the factual observations, then review the interpretation, suggested action, source URL, and confidence context.

Go to workflow →

Tune critical alerts

Keep broad email alerts for urgent pricing or launch movement, then narrow by competitor, keyword, or page type as signal quality improves.

Go to workflow →

Review source coverage

Use workspace data sources to confirm what is connected, what is stale, and which checks run in the background.

Go to workflow →

Use the v1 API

Workspace admins can create hashed bearer tokens and read competitors, events, and digests from the scoped v1 API.

Go to workflow →

API reference

Send `Authorization: Bearer <token>` with a key created by a workspace admin. Responses are scoped to that workspace and capped at 100 rows per request.

GET: /api/v1/openapi.json; Machine-readable OpenAPI 3.1 contract for the read-only v1 API.
GET: /api/v1/competitors; Competitor profiles and monitored source URLs for the key's workspace.
GET: /api/v1/events; Recent detected signals, source URLs, confidence, importance, and summaries.
GET: /api/v1/digests; Digest metadata, top actions, evidence-linked insights, and delivery timestamps.

Contact support

Send enough context for the team to reproduce the issue without asking for screenshots first.

Account or digest issue: Include the digest URL, alert URL, affected workspace, and what looked inaccurate or missing.
Security or rollout question: Use sales for source coverage, security review, plan limits, and team rollout questions.