Skip to main content
GET
Get User Mentions
Get tweets that mention a given @handle, 20 per page. This is the only user-scoped X endpoint that supports a time window: pass sinceTime and/or untilTime as Unix timestamps in seconds to bound the range. Use this for monitoring — brand mentions, inbound replies, reputation tracking, or ‘what happened to this account in the last 24 hours’. Returns tweets with has_next_page and next_cursor. For the account’s own posts rather than mentions of it, use get_twitter_user_tweet_timeline.
First time? Point any MCP client at https://mcp.aisa.one/mcp — Claude Code, Codex, Cursor, VS Code and the rest. Authorization is OAuth: the client opens a browser, you click Allow once, and there is no key to paste. Your agent then reaches every endpoint through a few meta tools: search, list_categories, get_details and batch_quote are free, batch_use is billed per call. Setup per client is in Connect via MCP; the live tool list and what each call costs are on aisa.one/mcp.
Set this endpoint up in your agent →

Request contract

  • Method and path: GET /apis/v1/twitter/user/mentions
  • Availability: enabled
  • Request URL template: https://api.aisa.one/apis/v1/twitter/user/mentions
  • userName: query; optional
  • Runtime facts: 2c7f0e92fe7bc266f2f532478b278a83381f4b2e4885f901fc233de0bd00a698
Complete OpenAPI definition Effective request and pricing declaration (including authentication and referenced schemas):

Cost and request rules

Usage-based billing; Default request estimate: $0.003 USD (not a fixed price). Account-specific pricing and final settlement may differ. Published reference values are not an account-specific quote or a settled charge. For endpoints supporting X-AISA-Cost-Mode: quote, obtain a free quote for your exact request before execution; reconcile the settled cost with response metadata and Usage Logs. USD amounts use 1,000,000 integer micro-USD per dollar.
  • Default request reference estimate (USD): 0.003
  • Cost contract: response_count
  • Published reference multiplier: 1.0
  • Settlement evidence source: response_body

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Query Parameters

userName
string

Response

Successful response

code
integer
has_next_page
boolean
msg
string
next_cursor
string
status
enum<string>
Available options:
success,
error
tweets
object[]