- Brand
- First Answer
- Category
- Data & Analytics
- Primary Subcategory
- AI Search & LLM Visibility (AEO/GEO)
Integration details
Description
First Answer monitors how brands appear in answers from AI models such as ChatGPT, Perplexity, Gemini, Google AI Mode, Bing Copilot and Grok. Connect your First Answer account to ask questions about your monitored brands directly in the conversation. With this plugin you can: - See a brand's dashboard: mention rate, average sentiment, position and competitor ranking for a date range. - Review monitored prompts, the full AI responses collected for them and the search queries the models used. - Find which domains and URLs AI models cite, and which prompts cite them. - Compare your brand with the competitors you monitor. - List the prioritized recommendations First Answer suggests to improve your AI visibility. Intended for marketing, SEO, content and brand teams that already use First Answer. The plugin is read-only: it does not create, edit or delete brands, prompts, competitors or recommendations. It only accesses data from the workspaces your connected First Answer account can access, and it requires an existing First Answer account whose workspace includes MCP access.
- Integration type
- Plugin
- Verification status
- Not applicable
- Platform
- ChatGPT
- Primary Subcategory
- AI Search & LLM Visibility (AEO/GEO)
- Secondary Subcategories
- None listed
- Brand
- First Answer
- Access
- Account required
- First tracked
- 2026-11-14
- Tool count
- 21
- Market
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Not discoverable in ChatGPT yet
ChatGPT now suggests Plugins on its own when they match a user's request, but not every Plugin is being surfaced yet.We haven’t seen First Answer suggested yet. Sign up and we’ll track it, and your Discoverability Score will appear here once ChatGPT starts surfacing it.
What discovery looks like

Get alerts for First Answer
Get updates when First Answer’s Discoverability Score or category rank changes.
Competing in ChatGPT AI Search & LLM Visibility (AEO/GEO)
View Category21 tools agents can invoke
Get the brand's high-level dashboard with aggregated metrics across all monitored prompts. This is the best starting point for a quick brand health overview and competitive positioning assessment. Returns: - total_prompts: number of prompts being monitored - total_responses: total AI responses collected in the date range - total_brand_mentions: how many responses mentioned the brand - brand_mention_rate: percentage of responses mentioning the brand (0-100) - average_brand_sentiment: overall sentiment toward the brand (-1 to 1) - competitors_count: number of tracked competitors - brands_ranking: competitive leaderboard showing the brand and all competitors ranked by mention rate — this is the key competitive intelligence metric - top_ranked_prompts: prompts where the brand performs best - lowest_ranked_prompts: prompts where the brand performs worst (these are priority targets for optimization) Use group_id to filter metrics to a specific prompt category. Use ai_model to see performance on a single AI platform. Use category_ids to compare the brand only against some competitor categories: brands_ranking keeps the brand plus the matching competitors (competitors_count still counts every tracked competitor). This tool provides aggregated summary data. For deeper analysis: - Use list_monitored_prompts to see per-prompt breakdown - Use get_monitored_prompt on lowest_ranked_prompts to investigate issues - Use list_monitored_competitors to identify who the competitors are TIP: Call this tool with different ai_model values to compare brand performance across AI platforms (e.g. ChatGPT vs Perplexity vs Gemini). Competitor category filter (optional): - category_ids: comma-separated competitor category IDs (e.g. "3,7"). Category IDs (and names) come from the `categories` field of each competitor returned by list_monitored_competitors. - category_filter_mode: how category_ids is matched — "include" (default): competitors in ANY of the categories; "intersect": only competitors in EVERY category; "exclude": only competitors in NONE of them (uncategorized included). Your own brand is always kept; only competitors are filtered.
get_dashboard
Get full details about a specific brand including its description, key features, website, country, and language. Use this to understand what the brand is and what it offers before diving into visibility analysis. The description and key_features fields provide context that helps interpret mention rates and sentiment in other tools' output.
get_brand
List which monitored prompts have AI responses that cite a specific domain. This reveals the connection between a web source and the questions it influences. Requires domain_id obtained from list_cited_sources. Returns a paginated list of prompts that reference this domain, allowing you to understand: - Which types of questions lead AI models to cite this source - How broadly influential a domain is across different prompt categories - Whether a competitor's website is cited in prompts relevant to your brand Combine with get_monitored_prompt_responses to read the actual AI responses that cite this domain and understand the context of each citation.
get_cited_source_related_prompts
List which monitored prompts have AI responses that cite a specific URL. This is the most granular level of source-to-prompt mapping. Requires domain_id from list_cited_sources and url_id from get_cited_source_urls. Returns a paginated list of prompts where AI responses reference this exact URL. Use this to understand: - Exactly which questions lead AI models to cite a particular page - The scope of influence of a single piece of content on AI answers - Whether a specific competitor article is affecting multiple prompts This is the deepest drill-down in the cited sources hierarchy: list_cited_sources → get_cited_source_urls → get_cited_source_url_related_prompts
get_cited_source_url_related_prompts
List specific URLs (pages) from a cited domain, with detailed impact metrics. This drills down from domain-level to page-level citation analysis. Requires domain_id obtained from list_cited_sources. Returns a paginated list where each URL includes: - id: URL identifier (use as url_id in get_cited_source_url_related_prompts) - url: the full page URL - impact: impact score for this specific page - citation_count: how many times this URL was cited - prompts_count: how many different prompts reference this URL - first_seen_at: when this URL first appeared in AI citations - ai_models: which AI platforms have cited this URL Use 'search' to filter URLs by keyword (e.g. search='review' to find review pages). This tool is valuable for: - Identifying the most influential individual pages within a domain - Finding specific articles or pages that AI models rely on - Prioritizing content outreach targets (which pages to get mentioned on) - Tracking when new URLs start appearing in AI citations
get_cited_source_urls
Get a competitor category and the monitored competitors in it. Returns: - data: id, name, description, color, created_at, updated_at, and competitors — one page of the category's competitors, each with id, name, website, created_at and categories (all categories it belongs to, as [{id, name}]) - pagination: current_page, per_page, total_pages, total_records — refers to data.competitors (100 per page by default, max 100). Increase page to fetch the remaining competitors. Get competitor_category_id from list_competitor_categories.
get_competitor_category
Get full details about a specific monitored competitor: id, name, website, created_at and categories (the competitor categories it belongs to, as [{id, name}]). Use this when you need more context about a particular competitor that appears in dashboard rankings or prompt-level analysis.
get_monitored_competitor
Get domains and URLs that AI models cited in their responses to a specific monitored prompt. This reveals which web sources influence how AI models answer this particular question. Returns a paginated list of domains ranked by citation frequency, where each domain includes: - domain name and citation count - list of specific URLs cited from that domain Use this to understand: - Which websites are most influential for this specific query - Whether the brand's own website is being cited - Which competitor or third-party sites are shaping AI responses - Potential content optimization targets (sites to get listed on) For a broader cross-prompt view of cited sources, use list_cited_sources instead. For the brand-level source analysis, combine this tool's output across multiple prompts of interest.
get_monitored_prompt_citations
Get detailed statistics and daily time-series data for a specific monitored prompt. This is the go-to tool for deep-diving into a single prompt's performance over time, including competitor comparison. Returns: - Overall metrics: total_responses, brand_mentions, mention_rate, brand_average_position, average_sentiment - Daily time-series: for each day in the date range, shows mention rates and sentiment for the brand AND each of its competitors, enabling trend analysis and competitive benchmarking over time This tool is essential for: - Tracking how brand visibility changes day-by-day for a specific query - Comparing the brand vs competitors on a specific prompt - Identifying trends (improving or declining mention rates) - Spotting anomalies (sudden drops or spikes in visibility) To get the prompt text and summary stats first, use list_monitored_prompts. To read the actual AI-generated responses, follow up with get_monitored_prompt_responses. Use category_ids to limit the competitors in the time series to some competitor categories (e.g. only direct competitors). Competitor category filter (optional): - category_ids: comma-separated competitor category IDs (e.g. "3,7"). Category IDs (and names) come from the `categories` field of each competitor returned by list_monitored_competitors. - category_filter_mode: how category_ids is matched — "include" (default): competitors in ANY of the categories; "intersect": only competitors in EVERY category; "exclude": only competitors in NONE of them (uncategorized included). Your own brand is always kept; only competitors are filtered.
get_monitored_prompt
Get the actual full-text AI-generated responses for a monitored prompt. This is the only tool that provides the raw content of what AI models actually said, making it critical for qualitative analysis. Returns a paginated list where each response includes: - ai_model: which AI platform generated this response (e.g. chat_gpt, perplexity) - response_markdown: formatted response with markdown - response_text: plain text version of the response - brand_mentioned: whether the brand was mentioned (true/false) - brand_sentiment: sentiment toward the brand in this response (-1 to 1) - citations: list of URLs the AI model cited in its answer - search_queries: search queries the AI model executed to build its answer - created_at: when this response was captured Use this tool to: - Read exactly what AI models say about the brand - Understand the context in which the brand is (or isn't) mentioned - Analyze how different AI models frame the brand differently - Identify specific claims or inaccuracies in AI responses - See which sources are cited alongside brand mentions NOTE: Responses can be lengthy. For prompts with many responses, you may need multiple paginated calls. Filter by ai_model to focus on one platform.
get_monitored_prompt_responses
Get the search queries that AI models internally executed when building their response to a monitored prompt. Many AI models perform web searches before generating answers — this tool reveals what they searched for. Returns a paginated list where each entry includes: - query: the search query string - count: how many times this query was used across responses Results are sorted by frequency (most common queries first). Use this to understand: - What information AI models seek when answering this prompt - Whether AI models search for the brand by name - What related terms or competitor names AI models look up - SEO and content strategy insights (what queries to optimize for) This data is especially valuable for content optimization: if AI models consistently search for specific terms, ensuring your brand ranks well for those terms can improve AI visibility.
get_monitored_prompt_search_queries
Get one recommendation in full, including its payload — the actual instructions/content needed to execute it. Returns everything from list_recommendations plus: - payload: the body of the recommendation. IMPORTANT: the keys of this object DEPEND ON 'kind' — each kind has its own schema (an llms_txt recommendation carries a drafted file, a new_article one carries the article brief, a reddit_comment one carries the post and a suggested comment, and so on). Read the keys that are actually present; do not assume a fixed shape. - payload_schema_version: schema version of that payload - dismiss_reason / dismiss_reason_code / dismissed_at: why it was dismissed, when applicable See list_recommendations for what each 'status' value means — in particular, 'done' may have been resolved automatically by FirstAnswer rather than by the user, and 'dismissed' is a lasting user opt-out, not pending work. Use list_recommendations first to discover recommendation_id values.
get_recommendation
List all brands available in the user's workspaces. This is the ENTRY POINT for all analyses — call this first to obtain brand_id values needed by every other tool. Returns a paginated list where each brand includes: - id: unique brand identifier (use as brand_id in other tools) - workspace_id: workspace this brand belongs to (null if legacy / unassigned) - workspace_name: human-readable workspace name - name: internal brand name - display_name: human-friendly brand name for display - description: what the brand/company does - key_features: notable products or services - website: brand's primary URL - country / language: market context - created_at: when monitoring started If the user has multiple brands, you may need to iterate pages or ask which brand they want to analyze.
list_brands
List all domains (websites) cited by AI models in their responses across ALL monitored prompts for a brand. This provides a brand-wide view of which web sources are influencing AI-generated answers. Returns a paginated list where each domain includes: - id: domain identifier (use as domain_id in related tools) - domain: the domain name (e.g. 'wikipedia.org', 'forbes.com') - impact: impact score representing how influential this source is - prompts_count: how many different prompts cite this domain - responses_count: total responses that cite this domain - urls_count: number of distinct URLs cited from this domain - ai_models: list of AI platforms that cited this domain Use 'search' to filter by domain name (e.g. search='wikipedia'). Use group_id to narrow to citations from a specific prompt category. This is the starting point for source analysis. To drill deeper: 1. Call get_cited_source_urls with domain_id to see specific pages cited 2. Call get_cited_source_related_prompts to see which prompts reference this domain 3. Combine with get_monitored_prompt_citations for per-prompt source breakdown Identifying top cited sources helps understand what content AI models trust and where the brand should aim to be referenced.
list_cited_sources
List all individual URLs cited by AI models across all domains and prompts for a brand. Unlike get_cited_source_urls which drills into a single domain, this tool returns a flat, cross-domain ranking of every cited URL. Returns a paginated list where each URL includes: - url_id: URL identifier - url: the full page URL - domain_id: identifier of the parent domain - domain: the domain name (e.g. 'wikipedia.org') - ai_models: list of AI platforms that cited this URL - impact: percentage of total responses that cited this URL (0-100) - count: total number of times this URL was cited - prompts_count: how many different monitored prompts cite this URL - first_seen_at: when this URL first appeared in AI citations Use 'search' to filter by URL substring. Use monitored_prompt_id to narrow results to URLs cited in a specific prompt's responses. This tool is valuable for: - Getting a global view of the most influential pages across all domains - Finding which specific pages AI models rely on most - Discovering new URLs entering AI citations (sort by first_seen_at) - Comparing URL-level influence across AI platforms
list_cited_urls
List the competitor categories of a brand. Categories are user-defined labels that group monitored competitors (e.g. "Direct", "Regional", "Priority"); a competitor can belong to several categories. Returns a paginated list where each category includes: - id: category identifier (use as competitor_category_id in get_competitor_category, and in category_ids to filter get_dashboard, get_monitored_prompt and list_monitored_competitors) - name: category display name - description: what the category means for this brand (may be null) - color: color slug used in the app - competitors_count: number of monitored competitors in the category - created_at: when the category was created
list_competitor_categories
List all competitors being tracked alongside a brand. Competitors are other brands/companies whose mentions in AI responses are tracked for comparison with the main brand. Returns one page (see page/per_page) where each competitor includes: - id: competitor identifier - name: competitor brand name - website: competitor's URL (may be null) - created_at: when the competitor started being tracked - categories: competitor categories it belongs to, as [{id, name}]. These are user-defined labels (e.g. "Direct", "Regional"); use their id as category_ids in get_dashboard, get_monitored_prompt and this tool. Use this to understand the competitive landscape before analyzing per-prompt data. Competitor names will appear in the brands_ranking from get_dashboard and in per-prompt breakdowns from get_monitored_prompt. Call this tool to map competitor IDs to names, and to discover the competitor category IDs, before filtering those results. Competitor category filter (optional): - category_ids: comma-separated competitor category IDs (e.g. "3,7"). Category IDs (and names) come from the `categories` field of each competitor returned by list_monitored_competitors. - category_filter_mode: how category_ids is matched — "include" (default): competitors in ANY of the categories; "intersect": only competitors in EVERY category; "exclude": only competitors in NONE of them (uncategorized included). Your own brand is always kept; only competitors are filtered.
list_monitored_competitors
List all monitored prompts for a brand with aggregated performance statistics over the specified date range. This is the primary tool for understanding which questions/queries are being tracked and how the brand performs in each one. Returns a paginated list where each prompt includes: - id: prompt identifier (use as monitored_prompt_id in detail tools) - text: the actual prompt/question being monitored - group: which category the prompt belongs to - brand_mentions: total number of times the brand was mentioned - brand_average_position: average ranking position when mentioned (lower = better) - mention_rate: percentage of responses that mention the brand (0-100) - average_sentiment: sentiment score for brand mentions (-1 to 1) - response_count: total AI responses collected Use group_id to filter by prompt category. Use ai_model to see performance on a specific AI platform. IMPORTANT: This returns summary statistics only. For deeper analysis of any prompt, follow up with: - get_monitored_prompt: time-series data and competitor comparison - get_monitored_prompt_responses: actual AI response texts - get_monitored_prompt_citations: which sources AI models cited - get_monitored_prompt_search_queries: what search queries AI models performed Dates must be in YYYY-MM-DD format.
list_monitored_prompts
List prompt groups (categories) for a brand. Groups organize monitored prompts into thematic categories such as 'Product Comparisons', 'Industry Questions', or 'Purchase Intent'. Returns each group with: - id: group identifier (use as group_id filter in other tools) - name: group display name Use group_id to filter results in list_monitored_prompts, list_cited_sources, and get_dashboard to narrow analysis to a specific category of prompts. This is especially useful when the brand has many monitored prompts and you want to focus on a subset.
list_groups
List the brand's recommendations — the concrete, prioritized work FirstAnswer suggests to improve the brand's AI visibility (technical fixes, content gaps, setup steps, community engagement). This is the same list the user sees under "Recommendations" in the FirstAnswer app. Returns a paginated list where each recommendation includes: - id: recommendation identifier (pass it to get_recommendation for the full body) - category: on_site_technical | content_gap | setup | community - kind: the specific recommendation type. The full set is 'robots_txt_blocked_ai_crawler', 'llms_txt', 'new_article', 'analytics_script_setup', 'crawler_logs_setup', 'chatgpt_business_profile', 'reddit_comment' - title: human-readable summary of what to do - priority: low | medium | high - status: see the status meanings below - completed_at, created_at, updated_at STATUS MEANINGS (important — these are not generic workflow states): - 'suggested': FirstAnswer detected the opportunity and is proposing it. This is the state every recommendation starts in, and the state a previously completed one returns to if the problem comes BACK (a regression, e.g. a robots.txt rule that was fixed and later reappeared). The user has not decided on it yet. - 'approved': the user reviewed it and accepted it — they intend to do it, but it is NOT done yet. Still outstanding work. - 'done': completed. Either the user marked it done, or FirstAnswer detected on a later check that the problem no longer exists and resolved it automatically. Do not assume a human did the work. - 'dismissed': the user explicitly rejected it (dismiss_reason_code says why: not_relevant, not_priority, disagree, other). This is a lasting opt-out — FirstAnswer will not propose it again, and for setup recommendations it stops checking altogether. Never present a dismissed recommendation as pending work. 'suggested' and 'approved' are the OPEN states: work that still needs attention. 'done' and 'dismissed' are closed. Filtering: - status, category, kind and priority each accept a COMMA-SEPARATED list (e.g. status='suggested,approved', category='content_gap,setup'). - status also accepts the special value 'open', which expands to every open state (suggested + approved). Prefer status='open' over spelling those two out — it stays correct if FirstAnswer adds another open state. It combines freely, e.g. status='open,done'. - start_date / end_date (YYYY-MM-DD) filter on when it was created. - order_by: '-created_at' (default, newest first), 'created_at', '-priority' (high first), '-completed_at' (most recently completed first). This tool is valuable for: - Answering "what should I do to improve my AI visibility?" (status='open', order_by='-priority') - Reviewing the outstanding backlog by priority - Auditing what was already completed in a period (status='done', order_by='-completed_at') The list omits the recommendation body. Call get_recommendation with an id to read the full payload (the instructions, drafted files, URLs, etc.).
list_recommendations
List individual AI responses across ALL monitored prompts of a brand, one row per response, with the URLs each response cited. Unlike get_monitored_prompt_responses this does NOT require a monitored_prompt_id, so it is the general-purpose data tool for anything computed over the whole response population. The unit of analysis is the RESPONSE. That matters: aggregated tools (list_cited_sources, list_cited_urls) report a count per domain/URL, so summing them double-counts a response that cited two of them and their overlap is not recoverable. Here each response appears once, with its own cited_urls, so any set logic the caller needs is exact. ## Counting instead of paginating ``pagination.total_records`` is the number of DISTINCT responses matching the filters. When you only need a count, ask for one row and read the total instead of walking pages: list_responses(..., fields=["id"], per_page=1) -> pagination.total_records Any combination of filters works the same way, so a rate is two such calls (filtered over unfiltered). For example, responses citing at least one host from a list, out of all eligible responses: list_responses(..., cited_domain=["a.com", "b.com"], fields=["id"], per_page=1) list_responses(..., fields=["id"], per_page=1) Add brand_mentioned=true to either call to restrict to responses that mention the brand. Unfiltered, total_records reconciles with get_dashboard total_responses. ## Filters monitored_prompt_id, group_id, ai_model and cited_domain all accept multiple values. brand_mentioned restricts to responses that do/do not mention the brand. Unknown prompt or group ids return 404 instead of an empty list, so a mistyped filter is never mistaken for "no data". cited_domain is an EXACT hostname match, ORed across values: "example.com" does not match "www.example.com" or "uat.example.com", so a list of hosts stays literal and neighbouring subdomains are never swept in. List each host explicitly and confirm spelling with list_cited_sources — a host nobody cited simply matches nothing rather than erroring. ## Payload Use `fields` to control what comes back — responses are large: - Default (fields omitted): id, monitored_prompt_id, ai_model, created_at, brand_mentioned, brand_position, brand_sentiment, cited_urls - Opt-in: prompt_text, groups, cited_domains, search_queries, response_text, response_markdown fields=["cited_urls"] gives the minimal response id -> citations base. Only ask for response_text / response_markdown when you need to read the answers. Field notes: - cited_urls: distinct NORMALIZED URLs (lowercased host, no fragment, no trailing slash, utm_source/srsltid stripped) in citation order. - brand_position / brand_sentiment come back as strings (API-wide decimal convention); cast before doing arithmetic. Dates are YYYY-MM-DD and are compared against the analysis run date, the same window every other tool uses.
list_responses
First Answer ChatGPT Plugin FAQ
How the directory, categories and Discoverability Score work.
Read the methodologyHow do I improve First Answer's ChatGPT Plugin discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
What are First Answer alternatives on ChatGPT?
As of 2026-11-15, First Answer competes with 212medya Growth Check, 3RD, 8ight SEO & GEO, Actionbase, Adzviser Search Console, AEO/GEO by VibeSEO, Agent Ready, Agent Ready Checker and 111 more in ChatGPT AI Search & LLM Visibility (AEO/GEO), ranked by public Discoverability Score.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.


