Mention · Rate Limits

Mention Rate Limits

Published rate limits for the Mention API. This artifact REPLACES a 2026-05-04 scaffold whose per-minute and per-month figures for Free / Professional / Enterprise tiers were invented — none of those tiers exist and none of those numbers are published. Mention publishes two concrete endpoint limits in its help center and one response header in its reference. Everything else is stated only as "limits vary based on resource types and methods".

Mention Rate Limits is the machine-readable rate-limit profile for Mention on the APIs.io network, in the API Commons Rate Limits shape.

It captures 2 rate-limit definitions, measuring requests.

Limit state is signalled in the reset response header, and an exhausted limit returns HTTP 429.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled and quotaExceeded.

Tagged areas include Alerts, Brand Monitoring, Media Monitoring, Social Listening, and Rate Limiting.

2 Limits Exhausted: HTTP 429 Quota: 402 reset
Transcribed from the provider's documentation on 2026-08-13 — dev.mention.com/current/src/appendix/Ratelimits.html, dev....
View Source
AlertsBrand MonitoringMedia MonitoringSocial ListeningRate LimitingQuotas

Limits

Create alert per-account
requests · 24 hours
Verbatim from the help center: "Create alert: max(20, alertsQuota*2) calls per 24 hours." The ceiling is derived from the account's own alert quota, so it is account-dependent and cannot be resolved to a constant without knowing the plan.
List mentions per-alert
requests · 24 hours
3600
Verbatim from the help center: "List mentions: 3600 calls per alert per 24 hours." Works out to an average of one call per alert every 24 seconds — which is why Mention points high-frequency consumers at the streaming endpoint instead.

Policies

Reset signalling
On 429, the response carries X-Rate-Limit-Reset holding the unix timestamp at which the limit resets. A client waits until that timestamp and retries.
No budget signalling
Mention returns no limit or remaining header, so a client cannot pace itself before exhaustion — the only way to learn a limit is to hit it. This is the main runtime gap for an autonomous consumer.
Prefer streaming over polling
The reference tells callers to follow _links.pull for new mentions and to "also consider using the streaming API" at https://stream.mention.net/api, which is the documented way to stay under the 3600/day listing limit.

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/mention-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.