The Microsoft Copilot scraper by cloro returns Copilot's Bing-grounded answers as structured JSON: answer text and markdown, every cited source, shopping cards and business entries.
- Get an API key at cloro.dev.
- POST a prompt to
https://api.cloro.dev/v1/monitor/copilot. - Read the parsed fields from the JSON response.
Copilot is the surface most often skipped by visibility tools, and it is grounded in Bing rather than Google, so its source list frequently disagrees with every other engine on the same question. That disagreement is the reason to track it separately rather than pooling it into an average.
import requests
payload = {
'prompt': 'best CRM for B2B sales teams',
'country': 'US',
'include': {'markdown': True},
}
response = requests.post(
'https://api.cloro.dev/v1/monitor/copilot',
headers={'Authorization': 'Bearer YOUR_API_KEY'},
json=payload,
)
print(response.json())curl -X POST https://api.cloro.dev/v1/monitor/copilot \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"prompt": "best CRM for B2B sales teams", "country": "US"}'Node.js and async/webhook examples are in the endpoint documentation.
| Parameter | Description | Default |
|---|---|---|
prompt* |
The query or question (1-10,000 characters) | – |
country |
Country code for localized results (US, GB, DE) |
US |
state |
US state code for finer localization | – |
include.markdown |
Return the answer as Markdown | false |
include.html |
Return a URL to the full HTML (expires after 24h) | false |
include.rawResponse |
Return the unparsed upstream payload | false |
* Required
{
"success": true,
"result": {
"text": "For B2B sales teams, the most commonly recommended options are...",
"sources": [
{ "position": 1, "url": "https://example.com/crm-guide", "label": "Example CRM Guide", "description": "Comparison of B2B CRM platforms..." }
],
"shoppingCards": [{ "title": "CRM Starter Plan", "price": { "value": 29.0, "currency": "$" }, "store": "Example" }],
"markdown": "For B2B sales teams, the most commonly recommended options are..."
}
}Alongside text and markdown:
sources— every cited URL with position, label and description, grounded in Bing's index.shoppingCards— product cards with price, store, rating and reviews.map— business and location entries with rating, reviews, address and operating status.citationPills— inline citation chips where present.rawResponse— the unparsed upstream payload.
Full field-level schemas are in the endpoint reference.
- Cross-engine coverage — the engine most visibility dashboards under-cover, so the cheapest place to find a gap.
- Enterprise and Microsoft-ecosystem queries — Copilot skews toward these, and answers there differ from consumer surfaces.
- Brand monitoring — whether Copilot names you on the prompts your buyers ask.
- Bing-index research — Copilot's grounding makes it a readable proxy for what Bing surfaces.
Different grounding. Copilot is Bing-backed, so on the same prompt it often cites a different set of domains. Pooling engines into one average hides being invisible on the one that matters to your category.
No. cloro covers Google Search, Google News, and the AI surfaces including Copilot. Bing's own search APIs were retired in August 2025.
cloro reads publicly visible responses. Check your own jurisdiction and terms.
60 seconds. Copilot streams its answer like the other AI surfaces.
- Endpoint reference: cloro.dev/docs
- Product page: cloro.dev/copilot
AI Mode · AI Overview · ChatGPT · Gemini · Google Search · Google News · Grok · Perplexity
Questions or support: r/cloroapi.
