canonical: https://jentic.com/apis/mention.net/mention

# Mention API

The Mention API provides programmatic access to media monitoring data - alerts that scan the web and social platforms, mentions matched to those alerts, and the supporting account, tag, task, and statistics resources. Eleven endpoints let teams create and manage alerts, retrieve and curate mentions, attach tags and tasks for triage, and pull engagement and reach analytics. The API is bearer-authenticated and well suited to brand-monitoring dashboards, competitive-intelligence tooling, and PR-response workflows that need a structured stream of brand or keyword mentions.

## For AI agents

Read media monitoring alerts and mentions, manage tags and tasks, and pull mention statistics across web and social sources. Bearer-authenticated.

## Scope

Does not publish posts, manage social inboxes, or run paid ad campaigns - use for media-monitoring alerts, mention retrieval, and statistics only.

## Capabilities

- Create and manage alerts that scan web and social sources for keywords, brands, or competitors
- Retrieve mentions matched to an alert with source, sentiment, and reach metadata
- Tag mentions and assign tasks to teammates for PR-response triage
- Pull statistics for an alert including volume, sentiment breakdown, and reach over time
- Read account profile and authenticated identity through /accounts/me
- Curate the mentions feed by marking items read or flagging them for follow-up

## Use cases

### Brand Monitoring Dashboard

PR and communications teams build internal dashboards that surface incoming brand mentions in near real time. The /accounts/{account_id}/alerts/{alert_id}/mentions endpoint returns the matched mention stream with source, language, and reach, which the dashboard ranks and routes to the on-call comms lead. Integration takes a single afternoon because the alert and mention model is intentionally narrow.

Example prompt: Poll /accounts/{account_id}/alerts/{alert_id}/mentions every 5 minutes since the last seen mention ID, push new items into the dashboard, and highlight any with reach above 10,000.

### Competitive Intelligence

Marketing teams configure alerts for competitor keywords and product launches. The statistics endpoint exposes share-of-voice and sentiment over time, which powers a weekly briefing that compares own-brand mentions against direct competitors without manual scraping.

Example prompt: For each competitor alert, fetch /accounts/{account_id}/alerts/{alert_id}/statistics for the last 7 days and produce a CSV of mention count, sentiment ratio, and total reach per competitor.

### PR Crisis Triage

When sentiment skews negative, teams need to triage mentions quickly. The Mention API supports tagging mentions and assigning tasks to teammates, which a triage worker can call directly so each high-impact mention is logged, tagged, and routed to a responder without leaving the brand-response tool.

Example prompt: List mentions with sentiment=negative and reach>5000 from the last hour, tag each with 'crisis', and create a follow-up task assigned to the on-call PR lead.

### AI Agent Brand Briefing

An AI assistant can produce a daily brand briefing by chaining Mention's alert, mention, and statistics endpoints. Through Jentic, the agent loads the operations as discoverable tools and assembles the briefing - top mentions, sentiment trend, biggest reach - without writing custom HTTP code or maintaining auth refresh logic.

Example prompt: Search Jentic for 'list brand mentions', execute /accounts/{account_id}/alerts/{alert_id}/mentions and /statistics, and write a 5-bullet daily summary covering volume, top sources, and sentiment shift.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /accounts/me | Get authenticated account profile |
| GET | /accounts/{account_id}/alerts | List alerts for an account |
| POST | /accounts/{account_id}/alerts | Create a new alert |
| GET | /accounts/{account_id}/alerts/{alert_id} | Get alert details |
| GET | /accounts/{account_id}/alerts/{alert_id}/mentions | List mentions matched to an alert |
| GET | /accounts/{account_id}/alerts/{alert_id}/mentions/{mention_id} | Get a single mention |
| POST | /accounts/{account_id}/alerts/{alert_id}/mentions/{mention_id}/tags | Apply tags to a mention |
| GET | /accounts/{account_id}/alerts/{alert_id}/statistics | Get alert statistics |

## Key resources

- **Accounts** — Authenticated identity and account profile data.
- **Alerts** — Configured monitoring queries that scan web and social sources for matching content.
- **Mentions** — Items matched to an alert with source, sentiment, language, and reach metadata.
- **Tags** — Labels applied to mentions for triage and reporting.
- **Statistics** — Aggregate metrics for an alert over a time window - volume, sentiment, reach.

## Why Jentic

- **Setup:** Wiring Mention by hand means sending its HTTP bearer token and hand-coding each account, alert, mention, and statistics call against api.mention.net/api. Through Jentic you install once, import the Mention API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Mention puts the account and alert ids in the URL path (/accounts/{account_id}/alerts/{alert_id}/...), so a rule can pin your agent to one alert: it can read mentions and statistics there and nothing else. You choose the operations it may call, so creating an alert or tagging a mention is included only if you add it.
- **Credential handling:** Your Mention bearer token is stored once, encrypted, by your own Jentic One instance and injected on each /accounts and /alerts call at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list brand mentions' or 'create a media alert', and Jentic returns the matching operation under /accounts/{account_id}/alerts with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Sprout Social** — Broader social management suite with publishing, engagement, and listening combined
- **Buffer** — Scheduling and publishing rather than monitoring
- **Twitter API** — Direct platform access rather than aggregated cross-source monitoring

## FAQ

### What authentication does the Mention API use?

The API uses HTTP bearer authentication via the BearerAuth scheme. Tokens are issued from the Mention dashboard; through Jentic the token is held in the encrypted vault and injected on each request so it never enters agent context.

### Can I create an alert for a competitor keyword with the Mention API?

Yes. POST /accounts/{account_id}/alerts creates a new monitoring query, and the resulting mentions stream is available via GET /accounts/{account_id}/alerts/{alert_id}/mentions, which is the supported pattern for competitor and brand monitoring.

### What are the rate limits for the Mention API?

The OpenAPI spec does not publish numeric rate limits. In practice the API is paginated and time-bounded - request smaller windows and follow the cursor on the mentions endpoint for high-volume alerts to avoid throttling.

### How do I pull recent mentions through Jentic?

Run `pip install jentic`, search for `list brand mentions`, load /accounts/{account_id}/alerts/{alert_id}/mentions, and execute with the alert ID and a since-timestamp. Jentic handles bearer-token injection and pagination cursors.

### Does the Mention API expose sentiment and reach metrics?

Yes. /accounts/{account_id}/alerts/{alert_id}/statistics returns aggregated mention volume, sentiment breakdown, and reach for an alert over a time window, which lets reporting tools build share-of-voice and trend dashboards.

### Can I limit what my agent is allowed to do with the Mention API?

Yes. Because you self-host Jentic One, your own rules decide which Mention operations and credentials the agent may use. Mention puts the account and alert IDs in the URL path, so a rule can pin the agent to a single alert where it reads mentions from GET /accounts/{account_id}/alerts/{alert_id}/mentions and pulls statistics, and nothing else. You choose the operations it may call, so writes like POST /accounts/{account_id}/alerts to create an alert or tagging a mention are included only if you add them.