2026-10-26, Copilot · GEO · Fundamentals

Best Microsoft Copilot scraper APIs for 2027: cited sources

Copilot grounds its answers in Bing results and cites the pages it used, which makes it the assistant where Bing visibility turns into answer visibility. Microsoft has no API that returns those consumer answers, so the options for 2027 are a scraper that sends prompts to copilot.microsoft.com, Microsoft’s grounding tools for your own agent, or your own collector. Scrapers differ in whether they send prompts at all, how they return citations, whether they target a country, and how they bill.

Vendor facts come from each vendor’s own pages, linked and checked on 2026-10-26; “not documented” means not found on those pages on that date. This is a buyer’s guide for 2027 budgets with facts as of October 2026; re-check prices before you commit.

Comparison

Two pages mention Copilot without answering new prompts on copilot.microsoft.com. ScrapingBee’s Copilot page covers public shared chats through its general scraper. DataForSEO parses Copilot Search on bing.com as ai_overview elements in its Bing SERP API, a different surface from the Copilot app.

Terms used below:

• Copilot answer: what a person gets at copilot.microsoft.com for a prompt, with the pages it cites.
• Inline citation: the chip in the answer text that points to one or more sources. Consecutive citations share one chip.
• Mode: the Copilot setting (such as smart, chat or reasoning) a vendor lets you choose. A different mode is a different series.

What to measure first

1. Mention rate: the answer names your brand. Any vendor’s answer text works.
2. Citation share: your domain among the cited pages, in order. Needs a sources list with positions.
3. Inline citation: which sentence cites you. Needs the chips mapped to sources.
4. Market variation: whether the answer changes by country. Needs country targeting, which SerpApi’s page does not document.
5. Bing to Copilot: whether ranking in Bing leads to a citation. Needs the searches Copilot ran, which no vendor page documents today.

The options

Bright Data Copilot Scraper

Bright Data’s Copilot Scraper takes url, prompt, country and index and returns answer_text, answer_text_markdown, sources, country and a timestamp. Jobs run synchronously or through an async trigger, with delivery by API, webhook or cloud storage (S3, GCS, Pub/Sub, Azure, Snowflake, SFTP).

Pricing (checked 2026-10-26): 5K records a month free, $1.50 per 1K pay as you go, Scale $499 a month for 384,000 records then $1.30 per 1K. Failed deliveries are not charged.

It has the lowest list price per answer. The field list names sources without positions or inline chips, so ask for a sample before you rely on order.

Fits bulk Copilot collection into a warehouse.

SearchApi Bing Copilot API

SearchApi’s Bing Copilot API uses engine=bing_copilot with q and market_code (such as en-US). It returns text_blocks, markdown and reference_links with index, title, link, displayed_link, snippet and source.

Pricing (checked 2026-10-26, pricing): 100 free requests; Developer $40 a month for 10,000 searches, Production $100 for 35,000, down to $1 per 1K at the 5M tier. It charges only for successful searches. Async delivery is not documented.

Market targeting by market_code and a flat per-search price, on the same key as its Google engines.

Fits teams already on SearchApi.

SerpApi Bing Copilot API

SerpApi’s Bing Copilot API uses engine=bing_copilot with q, no_cache, async and output (JSON, HTML or Markdown). It returns text_blocks, references with index, title, link, snippet and source, and a header; its launch post of June 16, 2026 adds header_video. No country parameter is documented. With async=true you collect results from the Searches Archive API; there is no webhook.

Pricing (checked 2026-10-26, pricing): 250 free searches a month; Starter $25 for 1,000, Developer $75 for 5,000, Production $150 for 15,000. Only successful searches count.

Without a country parameter, every answer comes from one market you do not choose. Confirm which with SerpApi before comparing markets.

Fits SerpApi customers who need Copilot text and references for one market.

Scrapeless Copilot scraper

Scrapeless documents a Copilot scraper, actor scraper.copilot, taking prompt, country, mode (search, smart, chat, reasoning or study) and should_fetch_share_link. It returns result_text as Markdown, links, citations with title and URL, and share_url.

No Copilot rate appears on its pricing page, which says it charges “only for successful data”. Ask for the rate in writing.

The mode choice lets you study how Copilot answers in reasoning or study mode. Keep one mode per series: a smart-mode answer and a chat-mode answer are different measurements.

Fits research on Copilot modes once you have a quoted price.

Apify Copilot actors

Apify’s own Microsoft Copilot Scraper takes queries, countryCode (default US) and copilotSearchMode (chat, reasoning, smart or study). It returns text, tables, sources with a section, and inlineCitations with textAnchor, the text each citation is attached to. It costs from $3.00 per 1,000 searches, pay per event. The page does not name copilot.microsoft.com and says the actor wraps a Google Search Scraper, so confirm which Copilot surface it collects.

A community actor, Copilot Answers Scraper, returns replyText, citations and citationCount from $157.14 per 1,000 completed answers, with no result charge for failures.

inlineCitations with text anchors are the most detailed citation mapping among the scrapers checked.

Fits prototypes and sentence-level citation studies.

ScrapeLLM

ScrapeLLM’s Copilot scraper is GET https://api.scrapellm.com/scrapers/copilot with an X-API-Key header, prompt and country. It returns result, result_markdown, links with URL and text, credits_used and elapsed_ms. A request costs 3 credits, and new accounts get 1,500 free trial credits. Plan prices and success-only billing are not documented on the page, which mentions async requests “with polling or webhook delivery” without details.

Fits a quick trial; get plan prices before you budget.

AnswerLine

POST /v1/monitor/copilot takes a prompt and a required country, any country. A US state is refused with a 400 and not billed.

curl -X POST https://api.answerline.dev/v1/monitor/copilot \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "prompt": "Which payroll software do small UK businesses use?",
    "country": "GB",
    "include": { "markdown": true }
  }'

Under result, per the API reference:

• text, and markdown when requested.
• sources[] with position, url and label. Copilot sources carry no description.
• citationPills[]: one entry per chip-and-source pair, grouped by a 1-based citationPillId; its position is the join key into sources. Omitted when the answer shows no chips.
• searchQueries, shoppingCards and map are coming and not returned yet.

result.provenance.searchMode reads forced: every answer searches the web. include.rawResponse returns the answer as normalized stream events; include.html is refused with a 400 on Copilot.

A Copilot request costs $0.00274 on every tier, and the include flags add nothing. A new account’s 100 free requests work on Copilot, and failed requests are not charged (credits).

Ordered sources, chip grouping and any country come in one response, with the same request contract as ChatGPT, Gemini, Perplexity, Grok, AI Mode, Google Search and Google News, and async batches of up to 500 tasks with webhooks and idempotency keys. There is no mode choice, and the searches Copilot ran are not returned yet.

Fits visibility products that compare Copilot citations with other assistants by country.

Microsoft’s grounding tools

Microsoft’s lifecycle notice says the Bing Search APIs retired on August 11, 2025 and points customers to Grounding with Bing Search. Its pricing is $14 per 1,000 transactions, up to 150 transactions a second and 1M a day, on top of your model. It grounds your own agent’s answer in Bing results; it does not return Copilot’s answer. The Microsoft 365 Copilot Chat API (preview) answers from the work product for users with a Microsoft 365 Copilot license.

Copilot APIs compared maps every Microsoft option and what it returns.

Building it yourself

A home-grown collector needs collection in every market you report on, a parser for answers, chips and sources, and upkeep when the app changes. Build vs buy itemizes the work.

How to choose

1. New prompts or shared chats. Tracking needs a scraper that sends your prompts.
2. Ordered sources. Citation share needs positions; inline citation work needs chips or text anchors.
3. Markets. If you report by country, rule out options without a documented country input.
4. Mode. Decide whether you measure the default experience or a chosen mode, and keep it fixed.
5. A published price. A 2027 budget needs a per-request rate in writing; Scrapeless and ScrapeLLM publish no dollar rate for Copilot.
6. Failure billing. Prefer success-only charges, idempotency and webhooks for scheduled jobs.
7. One contract or several. If ChatGPT, Gemini and AI Mode are on the plan, count the mapping work per extra vendor.

Cost example

200 prompts, one market, collected daily for 30 days: 6,000 Copilot answers a month. List prices checked 2026-10-26, before taxes and discounts. Recurring monthly free allowances (Bright Data’s 5K records) are netted; one-time trials (SearchApi’s 100 searches, ScrapeLLM’s 1,500 credits, AnswerLine’s 100 free requests) are not:

Scrapeless and ScrapeLLM are left out: neither ties a dollar price to a Copilot request on its page. AI monitoring cost planning covers budgeting across engines.

A weekly Copilot citation job on AnswerLine

Prompts in two markets as one batch, with a week-based idempotency key:

import os, datetime, requests

API = "https://api.answerline.dev"
HEADERS = {"Authorization": f"Bearer {os.environ['API_KEY']}"}
year, wk, _ = datetime.date.today().isocalendar()
week = f"{year}-W{wk:02d}"

prompts = ["best payroll software for small businesses", "Xero payroll vs Sage payroll"]
tasks = [
    {
        "taskType": "COPILOT",
        "payload": {"prompt": p, "country": c},
        "idempotencyKey": f"payroll-{i}-{c}-{week}",
        "webhook": {"url": "https://example.com/hooks/copilot"},
    }
    for i, p in enumerate(prompts)
    for c in ("GB", "US")
]

r = requests.post(f"{API}/v1/async/task/batch", json=tasks, headers=HEADERS, timeout=30)
r.raise_for_status()
print(r.json()["summary"])

In the webhook handler, find the chips that cite your domain:

def my_chips(result, domain="example.com"):
    return sorted({
        p["citationPillId"]
        for p in result.get("citationPills", [])
        if p["domain"] == domain or p["domain"].endswith("." + domain)
    })

An empty list with a non-empty sources means you were listed but not cited inline. Verify the webhook signature before trusting the body.

Pitfalls that skew Copilot data

• Mixing Copilot surfaces. copilot.microsoft.com, Copilot Search on bing.com and Microsoft 365 Copilot give different answers; keep them in separate series.
• Mixing modes. A reasoning-mode answer and a smart-mode answer are not one metric.
• Assuming sources are always there. sources can be empty and citationPills is omitted when no chips show; default both to empty lists.
• One run per prompt. Copilot answers vary between runs; sample several times and report rates, as in AI answer volatility.
• Counting links as citations. A link in the text is not a cited source; see mentions vs citations.

Every field is on the Copilot engine page, and monitoring Copilot walks through a first integration.

Keep reading