Mention API

Name: Mention API
Brand: Mention API
Availability: InStock

✓ Official Vendor SpecSocial MediaSocial Listeningbearer11 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the Mention API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Mention API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Mention API.

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

GET STARTED

Start building with Mention API

Explore with Jentic

View OpenAPI Document

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.

Use Cases

Patterns agents use Mention API for, with concrete tasks.

★ 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.

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.

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.

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.

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

11 endpoints — 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.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using Mention API through Jentic.

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.

Mention API

Connect the Mention API to your agent

Capabilities

Start building with Mention API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs