Skip to main content
Orient yourself in 30 seconds. Each row is one endpoint; click through for the full parameter reference. For deeper context on conventions (dates, ordering, pagination), see Conventions & gotchas.

Organization & setup

Reports

Answer Engine Insights report endpoints are POST requests scoped by category_id and return the {info, data} shape. Visibility, citations, sentiment, and query-fanouts reports take category_id, start_date, end_date, and metrics, plus report-specific optional fields. Traffic reports use a different shape: bots and referrals are scoped by domain rather than category_id. V2 FactCheck reports and V2 prompt answers are category-and-date scoped, but do not take a metrics field.

/v1/reports/visibility

How often your asset appears in AI answers. Common recipes: Visibility Score (with delta), over time, leaderboard, compare competitors, segment by model/region/persona.

/v1/reports/citations

Which URLs and domains AI answers cite. Common recipes: Citation Share + delta, share + volume over time, rank by domain.
citation_share is per-AI-model averaged. count is the raw number. Sorting by one doesn’t track the other — pick the question you’re answering and sort on the matching metric.

/v1/reports/sentiment

How positively/negatively AI answers reference your asset.
Numbers from the current public sentiment endpoint will not match the Profound app’s headline value exactly. Sentiment v2 — which closes the gap — is releasing soon.

/v1/reports/query-fanouts

The query-fanout view (how prompts cascade across AI surfaces). Same {info, data} shape.

/v1/reports/referrals (and /v2/reports/referrals)

Human-referral traffic to your domains attributed back to AI answers.

/v1/reports/bots (and /v2/reports/bots)

AI crawler / bot traffic to your domains.

/v2/reports/factcheck and /v2/reports/factcheck/claims

FactCheck scores and inaccurate claims for a category. These endpoints take category_id, start_date, and end_date, but not metrics.

Answers (per-prompt data)

Agents

Prompts

Content Optimization


For the canonical parameter reference (every operator, every field, required vs optional), see the REST API tab.