01 · Records and state owned
Projects, Boolean queries and channels, mentions, authors and sources, sentiment/topics/categories, aggregate analyses, custom data sources, and uploaded documents.
Brandwatch
Brandwatch
Included because its Consumer Research API exposes project- and query-scoped mentions, source metadata, sentiment and workflow fields for brand-risk and insight interfaces, with controlled metadata correction through the same surface.
Social, PR & communitySystem of engagementExtensible SaaS
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Retrieve mentions and their source, author, location, query, engagement, sentiment, category, tag, workflow, and reach metadata for an authorized project and query or query group, with date filtering and historical pagination.
03 · Actions and write paths
Edit supported mention metadata, including sentiment, categories, tags, priority, workflow status, assignment, location, author, publication name, and classifications, for identified mentions in an authorized project.
04 · Authentication and permissions
API Users exchange credentials for a bearer access token and must hold a Regular or Admin role. Organization switching also requires the target platform client ID so authorization resolves to the intended Consumer Research client.
05 · Monitoring, approval, and recovery
Bind results and edits to one Consumer Research client, project, query, and date range; sanitize mention text before display, retain source restrictions, and show whether sentiment or workflow metadata is original or manually edited.
06 · Limits and caveats
No Brandwatch-published provider MCP is documented. Mention content is returned without added encoding or sanitization, some sources restrict full text or metadata, and ordinary page/pageSize pagination reaches only the first 10,000 mentions.
First-party access
Documented surfaces
Agent access
MCP support
No official MCP server located
Support: No official MCP server located
Read scope: No first-party MCP read surface verified.
Write scope: No first-party MCP write surface verified.
Authentication: Not applicable to a first-party MCP provider.
Approval boundary: Any customer-built adapter must define its own approval and confirmation controls.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access3
Event access1
Identity4
Governance4
Agent access1
UI extensibility4
Portability3
Observability3
Documentation4
Proposed customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Brandwatch ships them.
Single-platform patterns
- Consumer-insight and brand-risk radar
- Social publishing command center
- Brand-signal briefing
- Response and escalation queue
Multi-platform compositions
- Brandwatch + content-production platform: social publishing command center
- Brandwatch + CRM or support system + analytics or work-management system: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
3 recorded sources
APIRepresentative source
https://developers.brandwatch.com/docs/ ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Targeted first-party core-access review
Developer docsSource inventory
https://developers.brandwatch.com/ ↗First-party developer documentation or platform overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
HomepageSource inventory
https://www.brandwatch.com/ ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Verified fact
Tied to cited first-party evidence reviewed for this profile.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.